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 #241903, regarding grub: Should ignore PPP & friends' traffic over the serial line 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.) -- 241903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241903 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: grub Version: 0.91-2 Severity: normal Hi! I have pppd connected to the serial terminal line on the client side, and have to switch it off and fire up minicom by hand. When minicom is started, I find the grub in the menu or at the commandline (I presume this is because of the random bash pppd sends). I fear some valid PPP data might actually command grub to do something silly, like wiping out a MBR or the like. Maybe there is a similar issue with SLIP and/or other serial line protocols? Grub should recognize the other end is a pppd and should ignore any data such pppd sends. Cheers, Jan. -- System Information Debian Release: 3.0 Kernel Version: Linux kontryhel 2.4.25-jan #2 SMP Fri Feb 20 15:23:11 CET 2004 i686 unknown Versions of the packages grub depends on: ii libc6 2.2.5-11.5 GNU C Library: Shared libraries and Timezone ii libncurses5 5.2.20020112a- Shared libraries for terminal handling
pgpRmbhHbLApw.pgp
Description: PGP signature
--- 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 ---
