Source: tpb Version: 0.6.4-8 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160707 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): > fakeroot debian/rules clean > dh_testdir > dh_testroot > rm -f build-stamp > # Add here commands to clean up after the build process. > [ ! -f Makefile ] || /usr/bin/make distclean > rm -f config.log > test -r /usr/share/misc/config.sub && \ > cp -f /usr/share/misc/config.sub config.sub > test -r /usr/share/misc/config.guess && \ > cp -f /usr/share/misc/config.guess config.guess > debconf-updatepo > dh_clean > dpkg-source -b tpb-0.6.4 > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building tpb using existing ./tpb_0.6.4.orig.tar.gz > dpkg-source: warning: ignoring deletion of directory autom4te.cache > dpkg-source: warning: ignoring deletion of file autom4te.cache/output.0, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file autom4te.cache/requests, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.0, use > --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > tpb-0.6.4/config.guess > tpb-0.6.4/config.sub > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/tpb_0.6.4-8.diff.K0DV8g > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b tpb-0.6.4 gave error exit status 2 > ──────────────────────────────────────────────────────────────────────────────── > Build finished at 20160706-2122 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/07/tpb_0.6.4-8_unstable_reb.normal.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.
