The package built fine on the buildds just a couple of days ago. Do you have an idea how the aws build environment differs?
Am 28. Januar 2017 09:28:00 MEZ schrieb Lucas Nussbaum <lu...@debian.org>: >Source: systemd >Version: 232-14 >Severity: serious >Tags: stretch sid >User: debian...@lists.debian.org >Usertags: qa-ftbfs-20170128 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): >> Pinging... >> Failed to ping watchdog: No such file or directory >> Pinging... >> Failed to ping watchdog: No such file or directory >> Pinging... >> Failed to ping watchdog: No such file or directory >> Pinging... >> Failed to ping watchdog: No such file or directory >> PASS test-watchdog (exit status: 0) >> ==== test-web-util.log ==== >> PASS test-web-util (exit status: 0) >> ==== test-xattr-util.log ==== >> PASS test-xattr-util (exit status: 0) >> ==== test-xml.log ==== >> PASS test-xml (exit status: 0) >> debian/rules:355: recipe for target 'override_dh_auto_test' failed > >The full build log is available from: > http://aws-logs.debian.net/2017/01/28/systemd_232-14_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. > >_______________________________________________ >Pkg-systemd-maintainers mailing list >pkg-systemd-maintain...@lists.alioth.debian.org >http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
