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 #302276,
regarding update-grub does not use fallback
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.)
--
302276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302276
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub
Version: 0.95+cvs20040624-16
Tags: patch
Grub's fallback isn't supported by update-grub. If you want to use
update-grub and fallback, you need to edit menu.lst after each run of
update-grub.
I made a patch to update-grub that allows fallback. It creates a new
comment for grub's fallback option in the template configuration, and
creates a new update-grub option fallbackstanzas to use 'savedefault
fallback' to each automagic stanza.
With the patch, I'm running update-grub as usualy, and safely doing
remote reboots into new Debian and custom kernel packages.
303a304,306
> # should grub create automagic stanzas to use fallback
> fallbackstanzas="true"
>
324a328,336
> ## fallback num
> # Set the fallback entry to the entry number NUM. Numbering starts from 0.
> # Requires 'default saved' above and 'savedefault fallback' in each stanza
> that
> # will fall back on failure. Also requires a numbered boot stanza that will be
> # the fallback. It is suggested to add a known-good stanza before the
> AUTOMAGIC
> # KERNEL LIST. To have grub use fallback in all automagic stanzas, use the
> # 'fallbackstanzas' option below.
> # fallback 1
>
560a573
> fallbackstanzas=${10}
577c590,594
< echo "savedefault" >> $buffer
---
> if test x"$fallbackstanzas" = x"true" ; then
> echo "savedefault fallback" >> $buffer
> else
> echo "savedefault" >> $buffer
> fi
645a663,665
> # Extract the fallbackstanzas value
> fallbackstanzas=$(GetMenuOpt "fallbackstanzas" "$fallbackstanzas")
>
704d723
<
710a730,735
> echo "## should update-grub create automagic stanzas to use fallback" >>
> $buffer
> echo "## e.g. fallbackstanzas=true" >> $buffer
> echo "## fallbackstanzas=false" >> $buffer
> echo "# fallbackstanzas=$fallbackstanzas" >> $buffer
> echo >> $buffer
>
799c824
< "$currentOpt" "" "$initrd" "true"
---
> "$currentOpt" "" "$initrd" "true" "$fallbackstanzas"
810c835
< "true"
---
> "true" "$fallbackstanzas"
829c854
< "$kernel" "$currentOpt" "" "$initrd" "false"
---
> "$kernel" "$currentOpt" "" "$initrd" "false"
> "$fallbackstanzas"
--- 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 ---
