reassign 477304 grub
fixed 477304 0.97-37
thanks
Hello,
From: Nick Hastings [mailto:[EMAIL PROTECTED]
Interesting but not related to this bug.
Yes, I just tried to reproduce it and as you can see on a fresh install with
sid version of grub-legacy
there's no problem.
This is *not* what the bug is about. The bug is about what happens in
the case where grub *is* using /boot/boot/grub/. Please read the bug
report again.
Well I can't remember ever having a /boot/boot, the time I used grub-legacy.
But ok that's long ago and I think I didn't use a seperate /boot at that time.
This bug probable belongs more to grub-legacy then grub-common which only
contains grub-probe and grub-mkimage
I don't think the problem is grub-probe, it's more how it's called from
grub-legacy scripts
I don't bother to read grub-legacy's bug reports, if this wasn't reassigned to
grub-common I would have never saw it :)
If you really want to reporoduce the bug the same way I did, you need
to
start by installing woody...
Ah thanks for telling.
So the problem only happens if your system started with woody or maybe before
that?
But everyone who started with sarge doestn't have this problem?
Anyway it seems that the bug is indeed reproducable and better news it
is fixed in grub 0.97-41.
Ok I just checked the changelogs between -36 (you reported against) and -41
In -37
* update-grub/grub-install: Pass --device-map to grub-probe. Thanks
[EMAIL PROTECTED] (Closes: #476833)
Now I now why I didn't found anything useful in 0.97-41 why this /boot/boot
could be a problem for grub-probe :)
So clearly this bug belongs to package grub and not grub-common and more
important
it's already fixed.
Hurray why all this trouble if it's fixed :)
I hope that reassign and fixed 0.97-37 is really correct now.
I leave it up to you and Robert if this bug report still isn't correctly
handled by me :)
Thanks for replying
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
