On 04/20/2014 03:42 AM, Gonéri Le Bouder wrote: > Hi Thomas and Ivo, > >> The build still fails on all architectures. There is probably something that >> happens in the local build in your environment that doesn't work on the >> buildds. > I'm afraid that's the problem. > > I managed to rebuild the package on fresh i386 and amd64 cowbuild env > with no problem. > > Best regards,
Hi Goneri, Yes, I did rebuild it also in a fresh amd64 cowbuilder env as well. In fact, that's what does Jenkins each time I push (it even rebuilds for Wheezy, Precise and Trusty), but out of options, I did try to setup a completely new Sid environment using Cowbuilder. And it did work as well, which is weird. So now, I really don't get what is happening with the buildds, and why they don't have binaries in $(CURDIR)/debian/subunit/usr/bin/* just right after dh_python3 happens (eg: see the log, this is what this bug is about, and IMO it has very little to do with my system being up-to-date or not). Yes, I could try to get myself setup with sbuild, but I'm not sure it would help to understand what's going on. :( Does anyone have a clue? Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org