On 02/23/2016 07:31 PM, Daniel Reichelt wrote: > Interesting. On a current jessie (plain + git/master-testsuite-enabled's > build-deps from bpo) I get an error about python3.4's unittest not > recognizing arguments from PYBUILD_TEST_ARGS - see attached build.log. > > Which version of libpython3.4-stdlib ends up being used within your > chroot? (mine is 3.4.2-1)
In my jessie-backports chroot, both jessie and jessie-backports are available in sources.list. But the main issue is this: Quoting build log: > usage: python3.4 -m unittest discover (...) This should say python3.4 -m **pytest**, not unittest. That's what the 'export PYBUILD_TEST_PYTEST=1' in d/rules is supposed to trigger. The corresponding line in the pybuild source code: (git-blame says it's there since 2013, so should™ be in jessie, without needing backports) http://anonscm.debian.org/cgit/dh-python/dh-python.git/tree/pybuild#n396 Can you reproduce the build failure in a freshly created pbuilder? I created mine with: DIST=jessie-backports git-pbuilder create and I checked my build with: git add -u && \ gbp buildpackage --git-pbuilder --git-dist=jessie-backports \ --git-export=INDEX --git-ignore-new Its quite possible there is something™ different with the way you set up your chroot, but debomatic and git-pbuilder seem to agree with me so far. Checking the debomatic log, the only dependency it actually pulled from backports is the msgpack, and it used the rest from jessie(-updates), so it doesn't seem to be using other backported versions. I'd love to fix this, but I can't reproduce it here. Cheers, - Danny ps: debomatic log link from Gianfranco http://debomatic-i386.debian.net/distribution#jessie-backports/borgbackup/1.0.0~rc1-3~bpo8+1/buildlog
