reopen 544377 severity 544377 critical thanks First off, this bug should *not* be closed. It's great that you think this is impossible, but I can assure you that it happened. Would you like to see my dpkg logs? I can also *guarantee* you that I did not do anything that would touch grub on the MBR. Perhaps another package (kernel? initramfs-tools?) managed to break something during the upgrade, but it's grub that has control of the MBR.
Here you can see on the 19th when I upgraded grub-legacy: 2009-08-19 09:38:14 upgrade grub-legacy 0.97-55 0.97-56 2009-08-19 09:38:14 status half-configured grub-legacy 0.97-55 2009-08-19 09:38:14 status unpacked grub-legacy 0.97-55 2009-08-19 09:38:14 status half-installed grub-legacy 0.97-55 2009-08-19 09:38:14 status half-installed grub-legacy 0.97-55 2009-08-19 09:38:14 status half-installed grub-legacy 0.97-55 2009-08-19 09:38:14 status unpacked grub-legacy 0.97-56 2009-08-19 09:38:14 status unpacked grub-legacy 0.97-56 Here's when I previously rebooted the machine: Aug 20 00:19:01 mycelium kernel: [ 3560.225453] fuse exit Aug 20 00:19:03 mycelium kernel: Kernel logging (proc) stopped. Aug 20 00:19:36 mycelium kernel: imklog 4.2.0, log source = /proc/kmsg started. Aug 20 00:19:36 mycelium kernel: [ 0.000000] Initializing cgroup subsys cpuset Aug 20 00:19:36 mycelium kernel: [ 0.000000] Initializing cgroup subsys cpu Aug 20 00:19:36 mycelium kernel: [ 0.000000] Linux version 2.6.31-rc6 (dilin...@dev) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #8 SMP Thu Aug 20 00:11:28 EDT 2009 Aug 20 00:19:36 mycelium kernel: [ 0.000000] KERNEL supported cpus: And here's the grub-common upgrade: 2009-08-30 19:27:24 upgrade grub-common 1.96+20090826-3 1.97~beta1-1 2009-08-30 19:27:24 status half-configured grub-common 1.96+20090826-3 2009-08-30 19:27:24 status unpacked grub-common 1.96+20090826-3 2009-08-30 19:27:24 status half-installed grub-common 1.96+20090826-3 2009-08-30 19:27:24 status half-installed grub-common 1.96+20090826-3 2009-08-30 19:27:24 status half-installed grub-common 1.96+20090826-3 2009-08-30 19:27:24 status unpacked grub-common 1.97~beta1-1 2009-08-30 19:27:24 status unpacked grub-common 1.97~beta1-1 Secondly, regardless of whether GRUB1 is legacy and not used any more, breaking user's machines is *not* acceptable. On Mon, 31 Aug 2009 08:18:20 +0000 [email protected] (Debian Bug Tracking System) wrote: > This is an automatic notification regarding your Bug report > which was filed against the grub-common package: > > #544377: grub-common: broke grub1 install? > > It has been closed by Felix Zielcke <[email protected]>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Felix Zielcke > <[email protected]> by replying to this email > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
