Your message dated Sat, 16 Aug 2025 15:55:37 -0400 (EDT)
with message-id <[email protected]>
and subject line Bug#1110934: Removed package(s) from unstable
has caused the Debian Bug report #549165,
regarding grub-legacy: update-grub no longer works on my system
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.)
--
549165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549165
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-legacy
Version: 0.97-58
Severity: important
update-grub no longer works on my system; it prints no errors, but returns an
exit code of 1. From the dpkg output, when trying to install a stock debian
kernel:
-----
~# dpkg -i /var/cache/apt/archives/linux-image-2.6.30-2-686_2.6.30-8_i386.deb
(Reading database ... 69738 files and directories currently installed.)
Preparing to replace linux-image-2.6.30-2-686 2.6.30-8 (using
.../linux-image-2.6.30-2-686_2.6.30-8_i386.deb) ...
Updating directory /lib/modules/2.6.30-2-686.
Examining /etc/kernel/preinst.d/
Unpacking replacement linux-image-2.6.30-2-686 ...
Running postrm hook script /usr/sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
User postrm hook script [/usr/sbin/update-grub] exited with value 1
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs 2.6.30-2-686
/boot/vmlinuz-2.6.30-2-686
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 2.6.30-2-686
/boot/vmlinuz-2.6.30-2-686
Setting up linux-image-2.6.30-2-686 (2.6.30-8) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.30-2-686
cryptsetup: WARNING: found more than one resume device candidate:
/dev/lizzie/swap
UUID=4b33b853-b245-4ec1-b649-c14f9a9b9907
cryptsetup: WARNING: found more than one resume device candidate:
/dev/lizzie/swap
UUID=4b33b853-b245-4ec1-b649-c14f9a9b9907
ln: creating symbolic link `/tmp/mkinitramfs_wRwI3y/sbin/vgchange': File exists
initrd.img(/boot/initrd.img-2.6.30-2-686
) points to /boot/initrd.img-2.6.30-2-686
(/boot/initrd.img-2.6.30-2-686) -- doing nothing at
/var/lib/dpkg/info/linux-image-2.6.30-2-686.postinst line 569.
vmlinuz(/boot/vmlinuz-2.6.30-2-686
) points to /boot/vmlinuz-2.6.30-2-686
(/boot/vmlinuz-2.6.30-2-686) -- doing nothing at
/var/lib/dpkg/info/linux-image-2.6.30-2-686.postinst line 569.
Running update-grub.
Searching for GRUB installation directory ... found: /boot/grub
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.30-2-686 (--install):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-2.6.30-2-686
-----
The System.map, config, vmlinuz and initrd.img files are all created in /boot,
but the menu entries aren't added into /boot/grub. My grub config is a bog
standard one, created by the installer, and has been working until now. I have
the same problem when trying to install a custom compiled kernel.
Running update-grub manually:
-----
~# update-grub
Searching for GRUB installation directory ... found: /boot/grub
-----
Nothing happens to /boot/grub/menu.lst
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-legacy depends on:
ii grub-common 1.97~beta3-1 GRand Unified Bootloader, version
ii libc6 2.9-26 GNU C Library: Shared libraries
ii libncurses5 5.7+20090803-2 shared libraries for terminal hand
grub-legacy recommends no packages.
Versions of packages grub-legacy suggests:
pn grub-legacy-doc <none> (no description available)
pn mdadm <none> (no description available)
pn multiboot-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Apologies; this wasn't sent as part of the dak rm action. I'm doing
this by hand. Since this was manual, this opens the chance for me taking
action by mistake.
I got the list of bugs via UDD, and am closing via -close on BCC. I spot
checked about 10 of the bugs, and they're all src:grub. The COUNT
matches the tracker page, so I'm sending this.
If I have closed a bug that's not about bin:grub or src:grub, please do
re-open the bug.
paultag
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
grub | 0.97-84 | source
grub-legacy | 0.97-84 | amd64, i386
------------------- Reason -------------------
ROM; dead upstream, replaced by grub2
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected].
The full log for this bug can be viewed at https://bugs.debian.org/1110934
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
