[buildd-tools-devel] Bug#569629: buildd: Don't go to next suite if --take fails.

Kurt Roeckx kurt at roeckx.be
Fri Feb 12 22:26:19 UTC 2010


Package: buildd
Version: 0.59.1-1~buildd20100201.2

I've just find this in the log:
Feb 12 08:47:37 buildd[20978]: unstable: total 7 packages to build.
Feb 12 08:47:40 buildd[20978]: Can't take alsa-tools: already taken by buildd_alpha-goedel
Feb 12 08:47:44 buildd[20978]: lenny-volatile: total 0 packages to build.
Feb 12 08:47:48 buildd[20978]: etch-volatile: total 0 packages to build.
Feb 12 08:47:52 buildd[20978]: lenny-backports: total 24 packages to build.
Feb 12 08:47:55 buildd[20978]: Starting build (dist=lenny-backports) of gcc-4.3_4.3.4-6~bpo50+1

I've seen it do the same kind of behaviour before.  It really
shouldn't go to the next suite when --take fails, it should
just try the next package in the list of packages it got.


Kurt






More information about the Buildd-tools-devel mailing list