Source: dropwatch Version: 1.5.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200225 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules). Relevant part (hopefully): > make[2]: Nothing to be done for 'check'. > make[2]: Leaving directory '/<<PKGBUILDDIR>>/src' > Making check in doc > make[2]: Entering directory '/<<PKGBUILDDIR>>/doc' > make[2]: Nothing to be done for 'check'. > make[2]: Leaving directory '/<<PKGBUILDDIR>>/doc' > Making check in tests > make[2]: Entering directory '/<<PKGBUILDDIR>>/tests' > make rundropwatch.sh > make[3]: Entering directory '/<<PKGBUILDDIR>>/tests' > make[3]: Nothing to be done for 'rundropwatch.sh'. > make[3]: Leaving directory '/<<PKGBUILDDIR>>/tests' > make check-TESTS > make[3]: Entering directory '/<<PKGBUILDDIR>>/tests' > make[4]: Entering directory '/<<PKGBUILDDIR>>/tests' > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2020/02/25/dropwatch_1.5.1-2_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.
