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 #175348,
regarding grub: no non-interactive boot with multiple terminals
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.)
--
175348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=175348
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub
Version: 0.92+cvs20021128-1
Severity: normal
builtins.c:line 4049, in terminal_func()
/* If multiple terminals are specified, wait until the user pushes any
key on one of the terminals. */
This is a problem.
I like that I can access GRUB through either a serial interface or the
console, but when I have it configured that way, it won't boot on its own.
It waits for a keypress before it goes to the boot menu, regardless of
what any of the timeout settings are.
the global section of my grub/menu.lst:
timeout 12
default 0
fallback 1
serial --unit=1 --speed=19200
terminal --dumb console serial
root (hd1,0)
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux charon.funhouse 2.4.19charon #1 Fri Aug 30 19:44:56 PDT 2002 i586
Locale: LANG=C, LC_CTYPE=C
Versions of packages grub depends on:
ii libc6 2.3.1-5 GNU C Library: Shared libraries an
ii libncurses5 5.3.20021109-2 Shared libraries for terminal hand
-- 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 ---
