Your message dated Fri, 16 Jun 2006 14:32:57 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#372783: fixed in kernel-package 10.049
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-image-2.6.16-2-amd64-k8
Version: 2.6.16-14
Severity: grave
Hello,
today my machine failed to boot. What was the real reason? Something is
completely fscked up with initrd management. The chronics:
some weeks ago: install of linux-image-2.6.16-1-amd64
dist-upgrading
manual install of self-compiled linux-image-2.6.17-rc6 (without initrd)
reinstall of linux-image-2.6.16-1-amd64
deinstall of linux-image-2.6.17-rc6
today: install of linux-image-2.6.16-2-amd64
reboot
Machine does not reboot. -1-amd64 is broken because initrd.img.old
points to the _new_ initrd for -2-amd64 and initrd.img symlink is missing.
So, how could this happen? I don't know. The only suspicious thing that
I remember is that grub-install seemed to be run twice, I don't know
why. But such problems must not appear, thus the severity.
Eduard.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-rc5
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.16-2-amd64-k8 depends on:
ii e2fsprogs 1.39-1 ext2 file system utilities and lib
ii initramfs-tools [linux-initra 0.60 tools for generating an initramfs
ii module-init-tools 3.2.2-3 tools for managing Linux kernel mo
linux-image-2.6.16-2-amd64-k8 recommends no packages.
-- debconf information:
linux-image-2.6.16-2-amd64-k8/preinst/already-running-this-2.6.16-2-amd64-k8:
linux-image-2.6.16-2-amd64-k8/postinst/depmod-error-2.6.16-2-amd64-k8: false
linux-image-2.6.16-2-amd64-k8/preinst/abort-overwrite-2.6.16-2-amd64-k8:
linux-image-2.6.16-2-amd64-k8/postinst/create-kimage-link-2.6.16-2-amd64-k8:
true
linux-image-2.6.16-2-amd64-k8/postinst/bootloader-error-2.6.16-2-amd64-k8:
linux-image-2.6.16-2-amd64-k8/postinst/bootloader-test-error-2.6.16-2-amd64-k8:
linux-image-2.6.16-2-amd64-k8/postinst/depmod-error-initrd-2.6.16-2-amd64-k8:
false
linux-image-2.6.16-2-amd64-k8/postinst/kimage-is-a-directory:
linux-image-2.6.16-2-amd64-k8/preinst/lilo-initrd-2.6.16-2-amd64-k8: true
linux-image-2.6.16-2-amd64-k8/preinst/lilo-has-ramdisk:
linux-image-2.6.16-2-amd64-k8/postinst/old-dir-initrd-link-2.6.16-2-amd64-k8:
true
linux-image-2.6.16-2-amd64-k8/preinst/overwriting-modules-2.6.16-2-amd64-k8:
true
linux-image-2.6.16-2-amd64-k8/postinst/old-initrd-link-2.6.16-2-amd64-k8: true
linux-image-2.6.16-2-amd64-k8/prerm/removing-running-kernel-2.6.16-2-amd64-k8:
true
linux-image-2.6.16-2-amd64-k8/preinst/failed-to-move-modules-2.6.16-2-amd64-k8:
linux-image-2.6.16-2-amd64-k8/preinst/initrd-2.6.16-2-amd64-k8:
linux-image-2.6.16-2-amd64-k8/postinst/old-system-map-link-2.6.16-2-amd64-k8:
true
linux-image-2.6.16-2-amd64-k8/prerm/would-invalidate-boot-loader-2.6.16-2-amd64-k8:
true
linux-image-2.6.16-2-amd64-k8/preinst/abort-install-2.6.16-2-amd64-k8:
linux-image-2.6.16-2-amd64-k8/preinst/bootloader-initrd-2.6.16-2-amd64-k8:
true
linux-image-2.6.16-2-amd64-k8/preinst/elilo-initrd-2.6.16-2-amd64-k8: true
--
--- End Message ---
--- Begin Message ---
Source: kernel-package
Source-Version: 10.049
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_10.049.dsc
to pool/main/k/kernel-package/kernel-package_10.049.dsc
kernel-package_10.049.tar.gz
to pool/main/k/kernel-package/kernel-package_10.049.tar.gz
kernel-package_10.049_all.deb
to pool/main/k/kernel-package/kernel-package_10.049_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: SHA1
Format: 1.7
Date: Fri, 16 Jun 2006 15:51:53 -0500
Source: kernel-package
Binary: kernel-package
Architecture: source all
Version: 10.049
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: 368539 372233 372783 373774
Changes:
kernel-package (10.049) unstable; urgency=low
.
* Bug fix: "kernel-package: localversion* files not supported?", thanks
to Mattia Dongili. It is not that localversion files are not
supported, it is that patches that try to change the version numbering
are not, You see, patches are applied _after_ there is a ./debian
directory, and that means ./debian/changelog is already in place. Re
doing this would require a drastic change in make-kpkg, so now we
document that patches that change package names are not supported.
(Closes: #368539).
* Bug fix: "linux-image-2.6.16-2-amd64-k8: initrd symlink management
sucks", thanks to Eduard Bloch. Well, the bug topic sucks too. And,
looking at the logs posted, it did seem to work in the test (the link
was indeed created). I did spot a typo in the postinst, so I think
this corner case should not arise again. (Closes: #372783).
* Bug fix: "no longer supports images with the same name on 2 arches",
thanks to Martin Michlmayr. Well, no longer is a misnomer, we never
did support multiple architectures for images in the control file.
This should now be fixed; we accept a space separated list of
architectures now. (Closes: #373774).
* kernel-package: arch/powerpc/include/asm symlink is not included in
the *-headers package, thanks to Eddy Petrisor. now we ship all of
arch/$KERNEL_ARCH/include. (Closes: #372233).
* Added documentation to the man page that just adding --cross-compile
does not in any way set the compiler used by the build system. That
still has to be done explicitly.
Files:
4f86f9395a066b3ccd125d0d2de265d1 485 misc optional kernel-package_10.049.dsc
dc7db9a3d5b80d5b701e4678a61c172b 844176 misc optional
kernel-package_10.049.tar.gz
c514de469f8000f669e5a2b01dd5c730 539588 misc optional
kernel-package_10.049_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEkxqGIbrau78kQkwRAmEvAKDApaUzYeNA+NTqYsn119Anm8nLCQCfezMX
gUJqHUyCws7htU1hPKk5yfc=
=d9Np
-----END PGP SIGNATURE-----
--- End Message ---
