Hi Luke, On Sun, Sep 15, 2013 at 05:43:18PM -0400, Luke Faraone wrote: > On Wed, Sep 11, 2013 at 05:15:02PM +0200, Salvatore Bonaccorso wrote: > > As pointed out in prepration of the recent DSA, it looks I can > > reproducibly get build failure for python-django (however was not 100% > > reproducible on another machine): > > I have not been able to reproduce this issue on several build systems; I > suspect it would also be functional on the buildds. > > Can you provide more information about your local configuration to give > a better idea as to what is causing this bug for you?
Thanks for verifying. Yes sure, here is more details on configuration I used (It's similar to buildd's setup as far I can tell, thus the initial severity, but downgrading is perfect if not reproducible elsewere): Basically I followed [1]. [1] https://wiki.debian.org/sbuild This is how I created the sbuild chroot: sbuild-createchroot wheezy /srv/chroot/wheezy-amd64-sbuild http://http.debian.net/debian Install eatmydata in the chroot. The config for the sbuild chroot looks like: [wheezy-amd64-sbuild] type=directory description=Debian wheezy/amd64 autobuilder directory=/srv/chroot/wheezy-amd64-sbuild groups=root,sbuild root-groups=root,sbuild profile=sbuild command-prefix=eatmydata and the sbuild profile (/etc/schroot/sbuild) is unmodified from the sbuild installation. It might be also some timing issue on the teardown raising this, as I'm also not able to reproduce the failure on a very similar setup. Please simply let me know if I should test something. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
