Bug#561837: grub not updatable to grub2

[Felix Zielcke]

Am Sonntag, den 20.12.2009, 19:16 +0100 schrieb Debian:
> reassign 561837 grub2
> 
> 
> Felix Zielcke schrieb:
> > Am Sonntag, den 20.12.2009, 17:01 +0100 schrieb Debian:
> >   
> >> Package: grub
> >> Version: 0.97-47lenny2
> >> Severity: normal
> >>     
> > Uhm what exactly is your problem and to what GRUB version does it
> apply?
> >   
> 
> Good question.
> Grub 0.97 is installable and working perfect on some other PC's.
> So i would say this bug should be better applied to package grub2
> 
> > You reported this bug against GRUB Legacy, i.e. 0.97.
> > This grub binary doestn't exist anymore with GRUB 2.
> >   
> 
> When it does not exist - why the installation is working?
> After the installation of grub2 failed i reinstalled grub with
> aptitude.
> You can see the output in my first eMail.

Your grub package is still GRUB Legacy. See the 0.97 at the end of that
line of dpkg -l output.
The only thing from grub2 used in GRUB Legacy is now grub-probe inside
grub-install and update-grub
But that's all.
If you want to boot your system with grub2 you need grub-pc (in case you
have a normal BIOS which I just assume if Legacy works.)

> It says that package grub-pc is broken and must be removed.
> After that the old grub was installed and can be called.
> You can see it:

But dpkg -l in your first mail said grub-pc was cleanly installed (ii at
the begin of line)
aptitude probable told this because grub and grub-pc conflict and so if
you install grub, grub-pc gets broken and has to be removed.


> > You have to use grub-install now just as you first did in this
> report,
> > before trying the grub command.
> >   
> 
> Yes - this works without errors but i could not call grub on the
> shell!
> Whatever i tried, the binary of grub2 was not installed.

There is no binary named either grub or grub2.
That thing from GRUB Legacy just doestn't exist any more.
Though we have now grub-emu but that's a seperate package now because
it's meant mainly for debugging.
grub-install now uses grub-setup to install GRUB to the MBR or
bootsector.

> > To generate grub.cfg it's still update-grub. But it's configured
> > differently now.
> >   
> 
> The configuration-file is generated.
> But not more.

update-grub never did anything else. That's why upstream names it now
grub-mkconfig and update-grub is now just a stub which calls that.

> Up to now i didn't try a reboot.
> I will check this now.
> My hope is that grub2 is still booted from the other partition.
> 
> 
> Regards
> Karsten Malcher
> 

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer