Bug#443838: po4a: missing/wrong (indirect) versioned dependency on perl-base
Package: po4a Severity: serious Hi, hex-a-hop fails to build from source on m68k: http://buildd.debian.org/fetch.cgi?pkg=hex-a-hopver=0.0.20070315-6arch=m68kstamp=1190551250file=log The affected output line is: Building bg translation Can't locate unicore/PVA.pl in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/share/perl/5.8/utf8_heavy.pl line 80. That's clearly a po4a call which fails. The file unicore/PVA.pl is provided in version 5.8.8-8 and newer (check also the perl changelog entry 5.8.8-9: Fix perl-base replaces after move of PVA.pl etc.) of perl-base. m68k has 5.8.8-7 or older installed. Please adapt the dependencies. Thanks. Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443838: po4a: missing/wrong (indirect) versioned dependency on perl-base
On Mon, Sep 24, 2007 at 03:20:06PM +0200, Jens Seidel wrote: Package: po4a Severity: serious Please adapt the dependencies. Thanks. I see that perl-base has the following line: Replaces: perl ( 5.8.8-5), perl-modules ( 5.8.8-8), ... Should it be safe to directly depend on perl-base instead of perl-modules? Please note that I'm not sure whether unicore/PVA.pl is required for only some parts of po4a which may justify to not depend on it. But should it not at least suggest a recent version of perl-base in this case? Or is Depends: perl-base Suggests: perl-base ( 5.8.8-8) (or something similar) invalid? PS: I now see in http://buildd.debian.org/pkg.cgi?pkg=hex-a-hop that the state of m68k is: Dep-Wait: perl (= 5.8.8-11). Does this mean that the dependencies of hex-a-hop are not yet fullfilled but a build attempt happened nevertheless? Sorry for many stupid questions but I want hex-a-hop in testing as soon as possible ... Thanks, Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443838: po4a: missing/wrong (indirect) versioned dependency on perl-base
Jens Seidel wrote: On Mon, Sep 24, 2007 at 03:20:06PM +0200, Jens Seidel wrote: PS: I now see in http://buildd.debian.org/pkg.cgi?pkg=hex-a-hop that the state of m68k is: Dep-Wait: perl (= 5.8.8-11). Does this mean that the dependencies of hex-a-hop are not yet fullfilled but a build attempt happened nevertheless? This means that the next try for a build will only happen when perl version 5.8.8-11 or later is available on m68k... Sorry for many stupid questions but I want hex-a-hop in testing as soon as possible ... hex-a-hop is ready for testing migration if it's mipsel build is installed in the archive and it's staging period is over [1] ... m68k is not taken into account for testing migration... Cheers Luk [1] http://bjorn.haxx.se/debian/testing.pl?package=hex-a-hop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443838: po4a: missing/wrong (indirect) versioned dependency on perl-base
On Mon, Sep 24, 2007 at 05:22:21PM +0200, Luk Claes wrote: Jens Seidel wrote: On Mon, Sep 24, 2007 at 03:20:06PM +0200, Jens Seidel wrote: PS: I now see in http://buildd.debian.org/pkg.cgi?pkg=hex-a-hop that the state of m68k is: Dep-Wait: perl (= 5.8.8-11). Does this mean that the dependencies of hex-a-hop are not yet fullfilled but a build attempt happened nevertheless? This means that the next try for a build will only happen when perl version 5.8.8-11 or later is available on m68k... OK, but why happened an initial build if build deps are not fulfilled? I also do not know where = 5.8.8-11 comes from, at least not from po4a so the bug remains open. Sorry for many stupid questions but I want hex-a-hop in testing as soon as possible ... hex-a-hop is ready for testing migration if it's mipsel build is installed in the archive and it's staging period is over [1] ... m68k is not taken into account for testing migration... Ah, m68k is not considered!? Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443838: po4a: missing/wrong (indirect) versioned dependency on perl-base
On Mon, Sep 24, 2007 at 05:46:44PM +0200, Jens Seidel wrote: On Mon, Sep 24, 2007 at 05:22:21PM +0200, Luk Claes wrote: Jens Seidel wrote: On Mon, Sep 24, 2007 at 03:20:06PM +0200, Jens Seidel wrote: PS: I now see in http://buildd.debian.org/pkg.cgi?pkg=hex-a-hop that the state of m68k is: Dep-Wait: perl (= 5.8.8-11). Does this mean that the dependencies of hex-a-hop are not yet fullfilled but a build attempt happened nevertheless? This means that the next try for a build will only happen when perl version 5.8.8-11 or later is available on m68k... OK, but why happened an initial build if build deps are not fulfilled? It's just the way it's implemented... I also do not know where = 5.8.8-11 comes from, at least not from po4a so the bug remains open. Probably the buildd maintainer saw that a recent version of perl was needed which only happens when the most recent version gets built... Which is also an implementation detail... Sorry for many stupid questions but I want hex-a-hop in testing as soon as possible ... hex-a-hop is ready for testing migration if it's mipsel build is installed in the archive and it's staging period is over [1] ... m68k is not taken into account for testing migration... Ah, m68k is not considered!? Indeed, m68k is not considered for migration to testing. There is currently not a single m68k package in testing... Will you please close this bogus bug now? Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443838: po4a: missing/wrong (indirect) versioned dependency on perl-base
On Mon, Sep 24, 2007 at 06:54:01PM +0200, Luk Claes wrote: On Mon, Sep 24, 2007 at 05:46:44PM +0200, Jens Seidel wrote: On Mon, Sep 24, 2007 at 05:22:21PM +0200, Luk Claes wrote: This means that the next try for a build will only happen when perl version 5.8.8-11 or later is available on m68k... OK, but why happened an initial build if build deps are not fulfilled? It's just the way it's implemented... Aha ... I also do not know where = 5.8.8-11 comes from, at least not from po4a so the bug remains open. Probably the buildd maintainer saw that a recent version of perl was needed which only happens when the most recent version gets built... Will you please close this bogus bug now? Please explain why you consider this bug is a bogus one? Po4a doesn't has a versioned package dependency on perl but needs one. This breaks other packages. If you really think I'm wrong or if it just does not matter that a snapshot in Debian does not work feel free to close it yourself. Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
