Your message dated Tue, 9 Oct 2007 13:32:05 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#445825: multipath-tools-boot should run after
libdevmapper1.02
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: multipath-tools
Version: 0.4.7-1.1
Severity: grave
Tags: patch
Justification: renders package unusable
The script /etc/rcS.d/S03multipath-tools-boot creates devices in
/dev/mapper/ (per udev rule), but /dev/mapper/ does not exist at that
time. The directory is created by /etc/rcS.d/S25libdevmapper1.02, so
multipath-tools-boot should run after that. (Or perhaps the directory
should be created earlier by some other means.) I could successfully
fix the problem by moving it to S25multipath-tools-boot. (The numbers
are a bit tight because I need it before S26lvm.)
This applies to etch; it might be possible that the new packaging
structure in unstable works better.
--- End Message ---
--- Begin Message ---
Version: 0.4.7-3
On Tue, Oct 09, 2007 at 01:02:33PM +0200, Peter Eisentraut wrote:
> I have to revise my analysis of the problem. It is indeed independent of
> libdevmapper. The problem is that multipath-tools-boot starts before udev,
> so whatever devices it may have created will be shadowed by udev. I could
> fix it by moving multipath-tools-boot to S04.
Which is what the lenny package has (fixed in 0.4.7-3). I wonder if we
should do an update for the next point release?
Cheers and thanks for having a look at the problem again,
-- Guido
--- End Message ---
