similar to: Processed: #473645 should be closed not #474509

Processing commands for control at bugs.debian.org: > reassign 474509 xen-3 Bug#474509: xen: Please enable support for loading bzImages with v2.08 of the x86 bootloader protocol Warning: Unknown package 'xen' Bug reassigned from package `xen' to `xen-3'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

Processing commands for control at bugs.debian.org: > found 599161 4.0.1-5.5 Bug #599161 {Done: Bastian Blank <waldi at debian.org>} [src:xen] xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart Bug #674907 {Done: Bastian Blank <waldi at debian.org>} [src:xen] shifts the clock by 50 minutes unexplicably under a Xen dom0 Marked as found

Processing commands for control at bugs.debian.org: > unarchive 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains Unarchived Bug 763102 > reopen 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common:

Processing commands for control at bugs.debian.org: > unarchive 753358 Bug #753358 {Done: Ian Campbell <ijc at hellion.org.uk>} [xen] pygrub not working when a disk script is in use Unarchived Bug 753358 > reopen 753358 Bug #753358 {Done: Ian Campbell <ijc at hellion.org.uk>} [xen] pygrub not working when a disk script is in use 'reopen' may be inappropriate when a bug

Processing commands for control at bugs.debian.org: > found 661231 1:3.22+dfsg1-2 Bug #661231 [isdnlog] isdnlog: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too Bug #331116 [isdnlog] isdnlog: fails to purge Marked as found in versions isdnutils/1:3.22+dfsg1-2. Marked as found in versions isdnutils/1:3.22+dfsg1-2. > found 527067 1.4.15+nmu2 Bug #527067

Processing commands for control at bugs.debian.org: > reopen 212146 Bug#212146: logcheck: please consider changing sort algorithm Bug reopened, originator not changed. > reopen 212149 Bug#212149: logcheck: please consider defining DATE and HOSTNAME macros for use in rule files Bug reopened, originator not changed. > merge 212149 174331 Bug#174331: logcheck: propose support for macros

Processing commands for control at bugs.debian.org: > reopen 678923 Bug #678923 {Done: George Shuklin <george.shuklin at gmail.com>} [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Bug reopened Ignoring request to alter fixed versions of bug #678923 to the same values previously set > End of message, stopping processing here. Please contact me if you need

Processing commands for control at bugs.debian.org: > reopen 412379 Bug#412379: logcheck-database: something for avahi? Bug reopened, originator not changed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Processing commands for control at bugs.debian.org: > unarchive 391606 Unarchived Bug 391606 > reopen 391606 Bug#391606: xen-utils-common: doesn't ship referenced man pages Bug reopened, originator not changed. > found 391606 3.1.0-1 Bug#391606: xen-utils-common: doesn't ship referenced man pages Bug marked as found in version 3.1.0-1. > thanks Stopping processing here.

Hi, There are a couple of open bugs against Xen-3 with patches which directly impact my efforts to have Debian Installer work in a Xen guest domain for Lenny. ?In both cases the relevant fixes are already committed in upstream Xen and I've been rebuilding and using the Debian packages with them without problems. First is #476366 which is a pygrub issue that prevents booting a guest using

Hi, I'm pleased to announce release 0.8 of efilinux, a reference implementation of a minimal UEFI bootloader. This bootloader has no bells or whistles, it is simply a prototype with the minimum amount of smarts required to load a linux kernel (though loaders for other formats could be added). Currently it only supports booting x86-64 bzImages but i386 support is planned for release 0.9, with

Processing commands for control at bugs.debian.org: > found 728266 2.0.91-2 Bug #728266 [blktap-dkms] Depends on obsolete packages Marked as found in versions blktap-dkms/2.0.91-2. > tags 728266 + jessie sid Bug #728266 [blktap-dkms] Depends on obsolete packages Added tag(s) sid and jessie. > severity 701278 important Bug #701278 [src:flush] flush: ftbfs with GCC-4.8 Severity set to

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

I object to the closing of these bugs on all of the following grounds: 1. They are wishlist items, and the wish has not been resolved, simply dismissed. 2. They are closed on the grounds that the messages are startup messages. Some are, but some are not. 3. The suggestion that startup messages should not be filtered out seems unwarranted. 4. I responded to earlier requests for exact log lines,

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: serious After noting that this version supposedly loads bzImage kernels: | xen-3 (3.2.1-2) unstable; urgency=low | | * Use e2fslibs based ext2 support for pygrub. (closes: #476366) | * Fix missing checks in pvfb code. | See CVE-2008-1952. (closes: #487095) | * Add support for loading bzImage files. (closes: #474509) | *

> > You are probably imitating / following some procedure used by > > Slackware to create EFI-compatible ISO images. The problem, as > > mentioned in a recent email this last week, is the particularities of > > the documents regarding, in this case, grub2 as EFI bootloader (as > > oppose to documents covering EFI bootloaders in general and clearly > >

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was debian at abeckmann.de). > usertags 669005 piuparts Bug#669005: uninstallable on sid (might just need require a rebuild) There were no usertags set. Usertags are now: piuparts. > affects 669005 + shogun-python-static shogun-python-modular

Hi William, Please could you provide some more details of the failure since this functionality works for me both with the Debian packages and upstream and I don't recall any additional patches upstream. Are there any messages in the logs? Particularly /var/log/xen/xend* and /var/log/xen/domain-builder-ng.log. Which kernel are you trying to load? The standard Lenny -686-bigmem kernel