Source: rpmlint Version: 1.9-4 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): > ./FilesCheck.py:1003:1: E305 expected 2 blank lines after class or function > definition, found 1 > ./Config.py:84:1: E305 expected 2 blank lines after class or function > definition, found 1 > ./Config.py:98:1: E305 expected 2 blank lines after class or function > definition, found 1 > ./Config.py:112:1: E305 expected 2 blank lines after class or function > definition, found 1 > ./Config.py:133:1: E305 expected 2 blank lines after class or function > definition, found 1 > ./Config.py:143:1: E305 expected 2 blank lines after class or function > definition, found 1 > ./AbstractCheck.py:108:1: E305 expected 2 blank lines after class or function > definition, found 1 > ./test/test.Pkg.py:33:1: E305 expected 2 blank lines after class or function > definition, found 1 > ./test/test.SpecCheck.py:34:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./test/test.SpecCheck2.py:20:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./test/test.SpecCheck3.py:20:1: E305 expected 2 blank lines after class or > function definition, found 1 > ./test/test.PamCheck.py:25:1: E305 expected 2 blank lines after class or > function definition, found 1 > Makefile:60: recipe for target 'check' failed > make[2]: *** [check] Error 1 > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > debian/rules:18: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/18/rpmlint_1.9-4_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.