Am Montag, den 31.08.2009, 11:39 -0400 schrieb Andres Salomon: > 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.
But it's impossible that grub-common breaks it. Just look at the maintainer scripts if you don't believe me. and also look in the filelist. The package itself doestn't contain anything in /boot/grub. grub-legacy's grub-install just uses grub-mkdevicemap and grub-probe but nothing else from the package. Everything else is grub2 specific. So if you believe that grub-common breaks your grub-legacy then please explain how it should do this if the package itself doestn't do anything at all with your MBR or your /boot/grub. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
