Bug#464302: libmodule-load-conditional-perl: FTBFS: perl-modules: non-matching version installed (5.8.8-12 ! >> 5.10)
Niko Tyni
ntyni at debian.org
Tue Feb 12 21:34:52 UTC 2008
On Wed, Feb 06, 2008 at 09:42:53PM +0100, gregor herrmann wrote:
> On Wed, 06 Feb 2008 21:31:55 +0100, Lucas Nussbaum wrote:
> > sbuild doesn't
> > do that, unfortunately. Couldn't you write libversion-perl |
> > perl-modules, so that it works with sbuild?
>
> Thinking a bit more I think we could just write libversion-perl,
> because perl-modules 5.10 (since -3) provides libversion-perl.
> Dropping the version on the dependecy would mean that we have a
> problem in stable ...
I don't think there's a problem even with stable.
The distribution specifies version.pm >= 0.69, but judging by
t/02_Parse_Version.t and
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2007-01/msg00805.html
the problem is only with pureperl installations of version.pm, while we
have an XS one.
Indeed, both the test suite and the apparently problematic
$ perl -Mversion -le'qv(1)+0'
invocation work on Etch libversion-perl 0.6701-1.
Conclusion: as perl-modules Build-Essential:yes, an unversioned
*build*-dependency on just libversion-perl should work "everywhere".
I'm not quite as sure about the runtime dependency, but it seems that
Depends: perl (>= 5.6.0-16), libversion-perl
works at least in 'apt-get install libsmart-comments-perl',
as it drags perl-modules with it in the 5.10 case.
Cheers,
--
Niko Tyni ntyni at debian.org
More information about the pkg-perl-maintainers
mailing list