On 02/23/2016 08:15 PM, Danny Edel wrote: > 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.
After it didn't work with gbp on my jessie64 VM either, I tested gbp on stretch64 and it worked?! > 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. Then I noticed this line missing in my d/rules. Turns out I messed up the git fetch on the jessie machine. Shame on me! → Green lights from my end, git/master-testing-enabled builds went through just fine. Sorry for the confusion and thanks for your patience and your work on this :) Daniel
