Source: cloud-init Version: 0.7.8-1 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): > Running: pep8 cloudinit/ tests/ tools/ > cloudinit/safeyaml.py:26:1: E305 expected 2 blank lines after class or > function definition, found 1 > cloudinit/util.py:2029:9: E741 ambiguous variable name 'l' > cloudinit/sources/DataSourceAltCloud.py:279:1: E305 expected 2 blank lines > after class or function definition, found 1 > cloudinit/sources/DataSourceBigstep.py:50:1: E305 expected 2 blank lines > after class or function definition, found 1 > cloudinit/sources/DataSourceEc2.py:204:1: E305 expected 2 blank lines after > class or function definition, found 1 > cloudinit/sources/DataSourceGCE.py:160:1: E305 expected 2 blank lines after > class or function definition, found 1 > cloudinit/config/cc_ca_certs.py:54:34: E741 ambiguous variable name 'l' > cloudinit/config/cc_growpart.py:300:1: E305 expected 2 blank lines after > class or function definition, found 1 > cloudinit/config/cc_resizefs.py:49:1: E305 expected 2 blank lines after class > or function definition, found 1 > cloudinit/handlers/upstart_job.py:119:1: E305 expected 2 blank lines after > class or function definition, found 1 > tools/hacking.py:159:1: E305 expected 2 blank lines after class or function > definition, found 1 > Makefile:39: recipe for target 'pep8' failed > make[2]: *** [pep8] Error 1 > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/18/cloud-init_0.7.8-1_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.
