Bug#557359: Can't detect multipath devices

[Felix Zielcke]

forcemerge 483971 557359
thanks

Am Samstag, den 21.11.2009, 20:53 +0100 schrieb Guido Günther:
> Hi Felix,
> Thanks for the quick response.
> 
> On Sat, Nov 21, 2009 at 07:04:42PM +0100, Felix Zielcke wrote:
> > Looks like you forgot about 483971 and 442382.
> > and maybe even others. Haven't looked this multipath issue now all
> up.
> > But i remembered it was you who has interest in multipath support
> inside
> > debian-installer and so grub2 too.
> Nope, I didn't. This one is different as it breaks upgrades from
> existing and supported installations.

It is not different. The older ones were reassigned to grub-common and
you filed this against grub-common (actually even grub-probe).
If it's more important then wishlist then the severity of that bug needs
to be changed and not a new one filed which exactly says the same: to
implement multipath support inside grub-probe.

> > I'm a bit unsure if I should just merge this with 483971 or reassign
> at
> > GRUB Legacy, where the dummy grub package still is, and add a
> debconf
> > note that gets shown when multipath is detected and tells people to
> keep
> > Legacy for now.
> That would at least be a workaround.
> 
> > But it still looks like that you're the only one for whom multipath
> is
> > important. (Well and Frans who considers this as a blocker, but it
> > didn't block the switch to grub2 as default for d-i alpha1)
> Don't think so. Multipath is run in "enterprise" environments where
> people are much more conservative regarding upgrades. I'm starting to
> get reports from etch->lenny upgrades so don't expect many others to
> notice within the next year. 
> Cheers,
>  -- Guido

Seems like I have to take it literarily that you get the reports.
The debian-testing mailing list were all upgrade-reports end doestn't
say anything about multipath back to 2008/12.

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer