Source: autopkgtest Version: 4.1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161021 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): > autopkgtest: DBG: no need to restore click AppArmor profiles > autopkgtest: DBG: needs_reset, previously=False, requested by run_tests() > line 169 > autopkgtest [01:20:21]: @@@@@@@@@@@@@@@@@@@@ summary > t FAIL non-zero exit status 1 > autopkgtest: DBG: testbed stop > autopkgtest: DBG: testbed close, scratch=/tmp/autopkgtest.2SwpBj > autopkgtest: DBG: sending command to testbed: close > autopkgtest: DBG: got reply from testbed: ok > autopkgtest: DBG: sending command to testbed: quit > > > ---------------------------------------------------------------------- > Ran 48 tests in 92.641s > > FAILED (failures=1, skipped=2) > debian/rules:38: recipe for target 'override_dh_auto_test' failed If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/21/autopkgtest_4.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.
