Source: gdb Version: 7.11.1-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160930 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): > debian/rules build > test -x debian/rules > mkdir -p "/<<PKGBUILDDIR>>/build/objdir" > CDBS WARNING: DEB_DH_STRIP_ARGS is deprecated since 0.4.85 > set -e; mv ./readline/support/config.guess > ./readline/support/config.guess.cdbs-orig; cp --remove-destination > /usr/share/misc/config.guess ./readline/support/config.guess; mv > ./config.guess ./config.guess.cdbs-orig; cp --remove-destination > /usr/share/misc/config.guess ./config.guess; > set -e; mv ./readline/support/config.sub > ./readline/support/config.sub.cdbs-orig; cp --remove-destination > /usr/share/misc/config.sub ./readline/support/config.sub; mv ./config.sub > ./config.sub.cdbs-orig; cp --remove-destination /usr/share/misc/config.sub > ./config.sub; > touch debian/stamp-autotools-files > /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation > resolved from binary package "stamp-autotools". Stop. > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > -------------------------------------------------------------------------------- > Build finished at 2016-10-01T00:20:03Z 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 The full build log is available from: http://aws-logs.debian.net/2016/09/30/gdb_7.11.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.
