Source: mailfront Version: 2.12-2 Severity: minor Tags: trixie sid ftbfs User: [email protected] Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: [email protected] Usertags: qa-doublebuild
Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > ------------------------------------------------------------------------------------------------------------------------ > > dpkg-buildpackage: info: source package mailfront > dpkg-buildpackage: info: source version 2.12-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Vagrant Cascadian > <[email protected]> > dpkg-source --before-build . > debian/rules clean > dh clean > dh_auto_clean > make -j8 clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > rm -f `cat TARGETS` > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: verifying ./mailfront_2.12.orig.tar.gz.asc > gpgv: Signature made Thu Feb 12 14:10:37 2015 UTC > gpgv: using RSA key 5151BDC9C14D3C67 > gpgv: Note: signatures using the SHA1 algorithm are rejected > gpgv: Can't check signature: Bad public key > dpkg-source: warning: cannot verify upstream tarball signature for > ./mailfront_2.12.orig.tar.gz: no acceptable signature found > dpkg-source: info: building mailfront using existing > ./mailfront_2.12.orig.tar.gz > dpkg-source: info: building mailfront using existing > ./mailfront_2.12.orig.tar.gz.asc > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > mailfront-2.12/conf-bgincs > mailfront-2.12/conf-bglibs > mailfront-2.12/conf-bin > mailfront-2.12/conf-bin{orig} > mailfront-2.12/conf-cc > mailfront-2.12/conf-ccso > mailfront-2.12/conf-ccso{orig} > mailfront-2.12/conf-cc{orig} > mailfront-2.12/conf-include > mailfront-2.12/conf-include{orig} > mailfront-2.12/conf-ld > mailfront-2.12/conf-ld{orig} > mailfront-2.12/conf-modules > mailfront-2.12/conf-modules{orig} > mailfront-2.12/conf-qmail > mailfront-2.12/conf-qmail{orig} > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/mailfront_2.12-2.diff.YhxZfb > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/mailfront_2.12-2_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
