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]
