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 #393079, regarding grub: "default saved" is broken by the new patch 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.) -- 393079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393079 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: grub Version: 0.97-1ubuntu9 Severity: normal (CC'ing Debian BTS, because I would have had the same problem with Sarge instead of Dapper. Ubuntu's reportbug doesn't handle this very well...) I have a system using dmraid and booting grub from the Windows boot loader. Using savedefault prevents grub from booting Linux. Selecting the menu entry for the Ubuntu kernel, the "kernel" and "initrd" lines show, but then I see: .... savedefault Error 15: File not found and I have to press return to go back to the main grub menu. If I hit 'e' and take out the savedefault, it boots normally. The menu.lst entry wass generated by update-grub: title Ubuntu, kernel 2.6.15-27-k7 root (hd0,6) kernel /boot/vmlinuz-2.6.15-27-k7 root=/dev/mapper/via_hibggiii7 ro quiet splash initrd /boot/initrd.img-2.6.15-27-k7 savedefault boot As I said, this machine doesn't boot grub the normal way. The machine is an Athlon XP on an Asus A7V600, with 2 160GB SATA hard drives using BIOS-driven RAID1. It runs win2k, but I left 5GB at the end of the drives to play around with; hence Ubuntu. I installed mostly using http://www.ubuntu-in.org/wiki/SATA_RAID_Howto. (which, incidentally, is a real pain compared to setting up /target and using the normal ubiquity installer...) I put GRUB on the boot sector of my ext3 partition, not the MBR, using grub device (hd0) /dev/mapper/via_hibggiii root (hd0,6) setup (hd0,6) And then, instead of somehow chainloading that partition, I did dd if=/dev/mapper/via_hibggiii of=grub.img bs=512 count=1 and after booting into win2k I copied that file to c:\grub.img, and told the windows bootloader about it with boot.ini: .... c:\grub.img="GRUB" So I don't know where grub could save defaults to, and I'm not shocked that savedefault doesn't work. I've always been suspicious about by default writing to the hard drive while booting, but this is the first time savedefault has ever actually caused a problem. My opinion is that it's not such a great default. The standard grub menu.lst doesn't use the saved default anyway. I would suggest making savedefault another automagic-comment configurable item, defaulting to off. Thanks, Peter Cordes -- System Information: Debian Release: testing/unstable APT prefers dapper-security APT policy: (500, 'dapper-security'), (500, 'dapper') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-27-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages grub depends on: ii libc6 2.3.6-0ubuntu20 GNU C Library: Shared libraries an ii libncurses5 5.5-1ubuntu3 Shared libraries for terminal hand grub recommends no packages. -- 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 ---
