Bug#546822: apt-get update of grub-pc daisychained from -legacy boots into -pc

[Robert Millan]

On Wed, Sep 16, 2009 at 10:25:34AM +0200, Felix Zielcke wrote:
> Am Mittwoch, den 16.09.2009, 00:28 +0200 schrieb Steffen Moeller:
> > Package: grub-pc
> > Version: 1.97~beta3-1
> > Severity: serious
> > 
> > Hello,
> > 
> > I obeyed the request to test grub2 and install grub-pc. This ended up in the daisychained invocation of first the legacy grub with the first entry being the grub2.
> > 
> > Then there was a new grub2 package which was installed together with others via apt-get -u dist-upgrade. 
> > 
> > Since then, the system boots into grub-pc, no longer into grub-legacy. This will be of some serious dissatisfaction to those whose daisychained grub-pc install was not functional and the user hoped to have better success with the new version.
> > 
> > Cheers,
> > 
> > Steffen
> 
> We never install grub2 into MBR without asking the user first.
> There's a debconf prompt for it, where you have to choose the device
> where it should get installed.
> If you choose a device there, then it's clear that your grub-legacy gets
> replaced in the MBR
> 
> -- debconf information:
> * grub-pc/install_devices: /dev/sda
> 
> And you did.
> So I fail to see where the bug is.

I don't understand the problem either.

Steffen, was the "GRUB install devices" dialog presented to you, or was
/dev/sda silently selected?

If it was presented to you, was there something misleading about it?  In
theory, you shouldn't see that dialog untill either you run
"upgrade-from-grub-legacy", or when you upgrade the grub-pc package.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."