On Sat, Jan 30, 2010 at 01:42:20PM +0100, Kurt Roeckx wrote: > On Fri, Jan 29, 2010 at 11:13:41PM +0000, Roger Leigh wrote: > > On Fri, Jan 29, 2010 at 11:16:38PM +0100, Kurt Roeckx wrote: > > > I noticed that I had 2 empty dirs in the build directory. The log > > > file for both show something like: > > > W: Failed to fetch http://incoming.debian.org/buildd-unstable/Sources.bz2 > > > Hash Sum mismatch > > > > > > E: Some index files failed to download, they have been ignored, or old > > > ones used instead. > > > apt-get update failed > > > Giving back package jcc_2.5-2 after failure in apt-get-update stage. > > > > What were the empty directories called? > > > > > > If they were normal package build directories, they may have failed to > > be removed after the apt failure. However, this should be fixed for > > a month or so with the new sbuild. Are you using the latest sbuild? > > I also noticed that the same packages where not given back. > > The transaction log on the wanna-build side shows: > package | distribution | version | action | prevstate | > state | real_user | set_user | time > -------------+--------------+---------+------------------+------------------+------------------+-------------+-------------------+---------------------------- > python-fuse | unstable | 2:0.2-2 | --binNMU | Installed | > BD-Uninstallable | aba | aba | 2010-01-25 > 16:02:52.221485 > python-fuse | unstable | 2:0.2-2 | --merge-all | BD-Uninstallable | > Needs-Build | wbadm | wbadm | 2010-01-25 > 16:03:35.457945 > python-fuse | unstable | 2:0.2-2 | --take | Needs-Build | > Building | buildd_i386 | buildd_i386-biber | 2010-01-26 > 01:20:03.324181 > > In the daemon.log file it shows: > Jan 26 01:20:03 buildd[28284]: Starting build (dist=unstable) of: > Jan 26 01:20:03 buildd[28284]: !1!python-fuse_2:0.2-2 > Jan 26 01:20:03 buildd[28284]: command line: nice -n 0 sbuild --apt-update > --batch --stats-dir=/home/buildd/stats --dist=unstable > --auto-give-back=buildd.debian.org....@buildd_i386-biber@buildd_i...@buildd.debian.org > --mail-log-to=k...@roeckx.be,l...@buildd.debian.org --arch=i386 --binNMU=1 > --make-binNMU=Build extension for python2.6 python-fuse_2:0.2-2 > Jan 26 01:21:14 buildd[28284]: Build finished. > > The logs says it gave it back, but I can't find a trace of that. > > I wonder if this has to do with it being a binNMU, both cases are > a binNMU.
Possibly, but the give-back should be triggered whether or not it's a binNMU. The auto-give-back code in sbuild is triggered on all package status changes. If you see a line "Giving back package $package after failure..." in the package build log, then it definitely ran wanna-build --give-back since it's logged after the give-back completed. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
