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 #403435,
regarding Questionable behavior of update-grub when root device does not exist
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.)


-- 
403435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403435
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub
Version: 0.97-20
Severity: wishlist

Hi,

I recently needed to use update-grub while recovering a system. I've 
booted from a live CD and started LVM, which hosts the root filesystem 
on a logical volume, then mounted root on /mnt and chrooted into it. 
Running update-grub in a chroot resulted in a broken menu.lst file for 
the following reason: the root device, extracted by update-grub from 
/etc/fstab (/dev/mapper/rootvg-rootlv) was not present inside the 
chroot, so even though the root device name was correctly determined 
in the find_device() function, it was later discarded due to

device=`readlink -f "$device"`

line, since readlink returns an empty string for a non-existent file. 
As a result I ended up with fallback root=/dev/hda1 entries in my 
kernel lines, which is really suboptimal.

I see at least two different ways to resolve the problem. One is to 
run readlink only on devices which are symbolic links (maybe even a 
check that it exists is sufficient). Another is to prompt user whether 
it is ok to use a non-existent device as root=. Either way, if there 
is information about the root device available in fstab, there is no 
good reason to toss it out in favour of most-probably-wrong /dev/hda1 
fallback.

Best regards,
-- 
Jurij Smakov                                           [email protected]
Key: http://www.wooyd.org/pgpkey/                      KeyID: C99E03CC


--- 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 ---

Reply via email to