Hi, On Sun, Apr 20, 2014 at 09:48:47AM +0800, Thomas Goirand wrote: > 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?
I just tried the rebuild myself (with pbuilder), and it seems the problem happens when building only the architecture-specific package (which is what happens on the buildds). When building both architecture specific and architecture independent packages, the build works fine. Cheers, Ivo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
