Your message dated Thu, 19 Nov 2009 07:18:43 +0000
with message-id <[email protected]>
and subject line Bug#556929: fixed in kernel-package 12.028
has caused the Debian Bug report #556929,
regarding kernel-package: postinstallation script uses wrong name for xen0
kernel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
556929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556929
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kernel-package
Version: 12.027
Severity: important
installing a xen0 kernel:
# dpkg -i linux-image-2.6.31.5-xen0_jh1_amd64.deb
Selecting previously deselected package linux-image-2.6.31.5-xen0.
(Reading database ... 33202 files and directories currently installed.)
Unpacking linux-image-2.6.31.5-xen0 (from
linux-image-2.6.31.5-xen0_jh1_amd64.deb) ...
Done.
Setting up linux-image-2.6.31.5-xen0 (jh1) ...
Internal Error: Could not find image (/boot/xen0-linux-2.6.31.5)
dpkg: error processing linux-image-2.6.31.5-xen0 (--install):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
linux-image-2.6.31.5-xen0
Looking in /boot we find:
# ls /boot/*xen0*
/boot/vmlinux-2.6.31.5-xen0 /boot/vmlinuz-2.6.31.5-xen0
Looks like the postinstall script is getting the wrong name
In /var/lib/dpkg/info/linux-image-2.6.31.5-xen0.postinst we see:
....
# Predefined values:
my $version = "2.6.31.5";
my $move_image = ''; # target machine defined
my $kimage = "xen0-linux"; # Should be empty, mostly
....
die "Internal Error: Could not find image (" . $realimageloc
. "$kimage-$version)\n" unless -e $realimageloc
. "$kimage-$version";
What is "xen0"? A bit of the version? An architechure? A
subarchiture? A submarine architect?
-- System Information:
Debian Release: 5.0.3
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-rc6 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages kernel-package depends on:
ii binutils 2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii build-essential 11.4 Informational list of build-essent
ii debianutils 2.30 Miscellaneous utilities specific t
ii file 4.26-1 Determines file type using "magic"
ii gettext 0.17-4 GNU Internationalization utilities
ii make 3.81-5 The GNU version of the "make" util
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
ii po-debconf 1.0.15 manage translated Debconf template
ii util-linux 2.13.1.1-1 Miscellaneous system utilities
Versions of packages kernel-package recommends:
ii cpio 2.9-13 GNU cpio -- a program to manage ar
Versions of packages kernel-package suggests:
ii bzip2 1.0.5-1 high-quality block-sorting file co
pn docbook-utils <none> (no description available)
ii e2fsprogs 1.41.3-1 ext2/ext3/ext4 file system utiliti
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
pn libdb3-dev <none> (no description available)
pn libncurses-dev <none> (no description available)
pn linux-source | kernel-source <none> (no description available)
ii xmlto 0.0.20-5 XML-to-any converter
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kernel-package
Source-Version: 12.028
We believe that the bug you reported is fixed in the latest version of
kernel-package, which is due to be installed in the Debian FTP archive:
kernel-package_12.028.dsc
to main/k/kernel-package/kernel-package_12.028.dsc
kernel-package_12.028.tar.gz
to main/k/kernel-package/kernel-package_12.028.tar.gz
kernel-package_12.028_all.deb
to main/k/kernel-package/kernel-package_12.028_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Manoj Srivastava <[email protected]> (supplier of updated kernel-package
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Format: 1.8
Date: Thu, 19 Nov 2009 00:38:06 -0600
Source: kernel-package
Binary: kernel-package
Architecture: source all
Version: 12.028
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava <[email protected]>
Changed-By: Manoj Srivastava <[email protected]>
Description:
kernel-package - A utility for building Linux kernel related Debian packages.
Closes: 556929
Changes:
kernel-package (12.028) unstable; urgency=low
.
* More bug fixes with the XEN images.
* [3ec0509]: Brown Paper bag spelling fix: iamge -> image
* [34fa772]: Rework handling of XEN packages
.
So far, kernel-package would pay special attention to the
configuration files that enabled XEN hypervisor/guest images, mangling
the package name, and changing the file paths where the images were
dumped. This caused no end of confusion to third party tools, and also
surprised people when packages with different names had unexpected
file conflicts. With dpkg defaulting to --force-overwrite that could
be catastrophic. This is because a normal kernel image, a XenU or a
Xen0 image, all looked for modules in /lib/modules/$version, and would
conflict.
.
With this commit, kernel-package stops paying attention to the XEN
configuration hints in the config, producing a normal kernel image.
If users want to have a DomU or a Dom0 image from the same kernel
version, they will have to do what people wanting to run kernels witht
he same version with differing configurations have always had to do:
use --append-to-version to make the kernel images packages not
conflict.
Bug fix: "postinstallation script uses wrong name for xen0 kernel",
thanks to John Hughes (Closes: #556929).
Checksums-Sha1:
e84b3f07826c39b44fb9441440284c25607691e0 911 kernel-package_12.028.dsc
ec8ec0632f4ef0192616674cb9f3c20684a50d4d 553562 kernel-package_12.028.tar.gz
f9447d5e599828278be49212b42857885e4a5d6e 500746 kernel-package_12.028_all.deb
Checksums-Sha256:
b1c60b5563e14c39afd7a179cc49b5cbb66210aee9596803692dae385db158cd 911
kernel-package_12.028.dsc
b4972c16032f30c5372e18eb8ff1531378e6bdb69364c9a70559b1da00ba21ca 553562
kernel-package_12.028.tar.gz
a264ce4bef89077f387b106c1eef2346f736c2f8ef58699e79445ba08e075c53 500746
kernel-package_12.028_all.deb
Files:
55235ce01dba9a61b782baf8a7ec1e90 911 kernel optional kernel-package_12.028.dsc
0e6888d180a281445f234c5c6abac566 553562 kernel optional
kernel-package_12.028.tar.gz
efa9179ea5ae6bf918cb0cafb4138682 500746 kernel optional
kernel-package_12.028_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14-svn0 (GNU/Linux)
iEYEAREDAAYFAksE7jAACgkQIbrau78kQkzUXgCfXDnfLgBi1qF6vHtfEavtJWj5
SgYAn1oUmrT2HwHzXlO3v3md/vzanCut
=t+J9
-----END PGP SIGNATURE-----
--- End Message ---
