Re: buildd failure
On Tue, Jun 03, 2003 at 05:03:09PM +0200, Marcelo E. Magallon wrote:
> On Tue, Jun 03, 2003 at 10:35:51AM -0400, Matt Zimmerman wrote:
> > On Tue, Jun 03, 2003 at 12:31:42PM +0200, Attila SZALAY wrote:
> > > What can I do with this (from packages.qa.debian.org):
> > >
> > > # 42 days old (needed 10 days)
> > > # out of date on hppa: libzorpll, libzorpll-dev (from 220.127.116.11-1)
> > >
> > > This is with package libzorpll.
> > Go to buildd.debian.org, read the log and find out what happened.
> For hppa:
> * 1.5.55-1 (latest build at Nov 18 15:01: maybe-failed)
> * 18.104.22.168-1 (latest build at Mar 23 17:18: maybe-successful)
> For alpha:
> * 1.5.55-1 (latest build at Nov 19 02:02: maybe-failed)
> * 1.5.57-1 (latest build at Nov 19 19:00: maybe-failed)
> * 22.214.171.124-1 (latest build at Nov 25 08:33: maybe-successful)
> * 126.96.36.199-1 (latest build at Nov 27 03:31: maybe-successful)
> * 188.8.131.52-1 (latest build at Apr 21 15:11: maybe-successful)
> Now, what does that mean?
It could mean that the autobuilder never attempted the build, in which case
it is my understanding that a buildd admin could prod it into doing so.
It could also mean that a build was attempted, but something went wrong, the
log was lost, etc.
In any case, debian-devel in general is not likely to know, but the buildd