Bug#390023: Maintenance of multipath-tools

[Steve Langasek]

John,

On Tue, Nov 21, 2006 at 09:17:05AM -0600, John Goerzen wrote:
> > there's an open RC bug on multipath-tools for more than 50 days and nobody
> > from the team (Bastian? Andres?) has commented on it:
> > http://bugs.debian.org/390023
> > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=multipath-tools

> > The last upload is an NMU of John Goerzen. John, maybe you should join the
> > team and help out with the maintenance of this package ?

> Thanks for bringing this up.  I do believe that it is important for that
> NMU to reach etch.  For the record, I pulled in a number of patches from
> upstream's git tree.  They addressed some pretty significant bugs, which
> are listed at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382214
> The NMU also fixed some missing dependencies, the PID issue, etc.


> This bug #390023 may not actually be RC.  It complains about the upgrade
> from an earlier version in testing (0.4.7-1), not an upgrade from the
> version in stable (0.4.2.4-2).  I don't know if the upgrade from stable
> is broken also; #294066 which discusses the PID file handling issue
> doesn't include a version number.

Hmm, this is the first I've noticed that Bastian is a co-maintainer of
multipath-tools.  The other issue holding multipath-tools out of testing,
besides bug #390023, is that the package has not been uploaded for s390
despite several builds on the autobuilder, and Bastian is the maintainer of
the s390 buildd.  Bastian, is there a reason this binary has not been
uploaded, or is the build getting lost by accident?

> I would argue that:

>  * If upgrades from stable are fine, this bug is non-RC and the
>    corrected version should enter etch.

>  * If upgrades from stable are broken, then this bug is also found in
>    the version in etch presently and is no worse.

Yes, I agree with both of these points; we're better off having one new
potentially-RC bug to deal with than leaving the two fixed RC bugs in
testing.  If there is no explanation for the stalled s390 binaries, I will
probably go ahead and push -1.1 into testing for the other architectures
while we're waiting for that to be resolved.

Can anyone else test whether this upgrade problem affects sarge->etch?

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/