Package: rebuildd Version: 0.4 Severity: wishlist post_build_cmd currently only gets executed after a successful build.
This means it's never possible to cleanup what source_cmd or build_cmd did after a failure of one of those commands. Either always call post_build_cmd but with different environment variables so that we know whether the build has been successful or not. Or add a new hook post_build_failed_cmd or cleanup_cmd. Note that it would be even better if the design of rebuildd involved creating a temporary directory in $work_dir and dropping that directory once the build is finished. Because right now if you build the same source package for two architectures and/or for two different distros at the same time, you end up sharing the downloaded source package and you don't really know when it's safe to remove it. It would also be nice to have comments explaining all the entries in the configuration file because many things are not obvious (the substitution available, the meaning of "any" in "more_arches" I still don't know... I had to put "i386" explicitly to get it to accept i386 builds on a amd64 machine). -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (150, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rebuildd depends on: ii lsb-base 3.2+Debian29 ii python 2.7.2-10 ii python-apt 0.8.3+nmu1 ii python-sqlobject 0.12.4-2.1 ii python-support 1.0.14 Versions of packages rebuildd recommends: ii pbuilder 0.206 ii python-gdchart2 0.beta1-3.4+b4 ii python-webpy 1:0.34-2 Versions of packages rebuildd suggests: ii cowdancer 0.67 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
