Source: git-buildpackage Version: 0.8.6 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > ./gbp/scripts/import_orig.py:650:1: E305 expected 2 blank lines after class > or function definition, found 1 > ./gbp/scripts/import_dscs.py:176:1: E305 expected 2 blank lines after class > or function definition, found 1 > ./gbp/scripts/config.py:139:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./gbp/scripts/clone.py:149:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./gbp/scripts/create_remote_repo.py:365:1: E305 expected 2 blank lines after > class or function definition, found 1 > ./gbp/scripts/buildpackage.py:798:1: E305 expected 2 blank lines after class > or function definition, found 1 > ./gbp/scripts/pull.py:174:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./gbp/scripts/import_dsc.py:435:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./gbp/scripts/dch.py:572:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./gbp/scripts/pq.py:487:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./gbp/scripts/supercommand.py:149:1: E305 expected 2 blank lines after class > or function definition, found 1 > ./gbp/deb/format.py:116:1: E305 expected 2 blank lines after class or > function definition, found 1 > Makefile:12: recipe for target 'syntax-check' failed > make[2]: *** [syntax-check] Error 1 > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > debian/rules:21: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/18/git-buildpackage_0.8.6_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
