Source: nototools Version: 0.2.13-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > dh_auto_clean > I: pybuild base:217: python3.9 setup.py clean > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_nototools/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:217: python3.8 setup.py clean > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_nototools/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.8' does not exist -- can't clean it > rm -rf nototools.egg-info > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_autoreconf_clean -O--buildsystem=pybuild > dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building nototools using existing > ./nototools_0.2.13.orig.tar.xz > dpkg-source: info: local changes detected, the modified files are: > nototools-0.2.13/nototools/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/nototools_0.2.13-1.diff.EHwupO > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > -------------------------------------------------------------------------------- > Build finished at 2020-10-27T12:29:37Z The full build log is available from: http://qa-logs.debian.net/2020/10/27/nototools_0.2.13-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.