Bug#544157: [grub-pc] shouldn't try to upgrade from GRUB 1 to GRUB 2 again if it did it before

[Felix Zielcke]

Am Samstag, den 29.08.2009, 12:51 +0200 schrieb Martin Steigerwald:
> Am Samstag 29 August 2009 schrieben Sie:
> 
> > The grub-pc.config script only extracts once the kopt parameter from it
> > and saves it in /etc/default/grub.
> 
> And thats the only parameter that was messed up after downgrading grub-pc 
> from sid to squeeze. /etc/default/grub then contained kopt from menu.lst 
> again.

Hm grub-pc.config before I changed it checked if grub-pc/linux_cmdline
returns "fillme" and only then extracts the kopt value.
So that should only happen if you have purged the package and then
reinstalled it but not if you just downgraded with apt/dpkg.

> > And if you choose to chainload grub2 then the update-grub from
> > grub-legacy is run with a special variable set, so that it generates a
> > menu entry for GRUB 2.
> 
> No, I let it replace GRUB 1 completely. I was surprised that it even asked 
> me that again, since I have been using GRUB 2 exclusively before. I have / 
> on a ext4 since about a week or two so I wouldn't want to switch back to 
> GRUB 1 anyway.

The chainload question is (at least in the sid version) only asked if
stage2 and menu.lst exists and core.img not.

> > In the sid version I changed the handling of the Linux kernel
> > parameters, it could be that this doestn't work cleanly with a
> > downgrade but this isn't fixable.
> 
> Well when its just a problem with an interim testing/unstable version that 
> stable users won't see that might not be a big problem. But if someone 
> experiences a problem on upgrading grub-pc from lenny to squeeze when its 
> stable and gets that problem own downgrade that wouldn't be that 
> convenient. OTOH AFAIR package downgrades aren't supported officially.
> 

Yes they aren't. You can't upgrade from oldstable to stable and then
downgrade again to oldstable.

-- 
Felix Zielcke
Proud Debian Maintainer