Re: Buildd info lag?

[Colin Watson <cjwatson@debian.org>]

On Mon, Mar 22, 2004 at 11:21:00AM +0100, Björn Stenberg wrote:
> Are the testing scripts using old buildd information?
> 
> Example: curl
> 
> Today's update_excuses.html claims it's out of date on arm, s390 and sparc:
>   http://http://ftp-master.debian.org/testing/update_excuses.html#curl
> 
> However judging from the buildd logs, curl was successfully built for all these architectures already friday night:
>   http://buildd.debian.org/build.php?arch=arm&pkg=curl
>   http://buildd.debian.org/build.php?arch=s390&pkg=curl
>   http://buildd.debian.org/build.php?arch=sparc&pkg=curl
> 
> Are the buildd logs perhaps not the end of the story? Has the package
> been built but not yet signed and uploaded, maybe?

Correct.

      curl |   7.11.0-4 |      unstable | arm, s390, sparc
      curl |   7.11.1-1 |      unstable | source, alpha, hppa, i386, ia64, m68k, mips, mipsel, powerpc

arm and sparc are in incoming.

> Is there someplace a curious person can find out more about this?

I think that's about it, really. The buildds are operated by humans, and
all the signatures are manual although the builds themselves aren't. The
build logs deliberately say "maybe-successful" or "maybe-failed" instead
of "successful" or "failed".

Cheers,

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]