Source: pam-shield Version: 0.9.6-1.3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org 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 pam-shield > dpkg-buildpackage: info: source version 0.9.6-1.3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Andreas Henriksson > <andr...@fatal.se> > dpkg-source --before-build . > fakeroot debian/rules clean > dh_testdir > dh_testroot > # Add here commands to clean up after the build process. > /usr/bin/make distclean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > rm -rf .libs _libs > test -z "pam_shield.la" || rm -f pam_shield.la > rm -f ./so_locations > rm -f shield-purge > rm -f *.o > rm -f *.lo > rm -f *.tab.c > test -z "" || rm -f > test . = "." || test -z "" || rm -f > rm -f config.h stamp-h1 > rm -f libtool config.lt > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > rm -f cscope.out cscope.in.out cscope.po.out cscope.files > rm -f config.status config.cache config.log configure.lineno > config.status.lineno > rm -f ./.deps/pam_shield.Plo > rm -f ./.deps/pam_shield_lib.Plo > rm -f ./.deps/shield_purge-pam_shield_lib.Po > rm -f ./.deps/shield_purge-shield_purge.Po > rm -f Makefile > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_clean > dh_clean: warning: Compatibility levels before 10 are deprecated (level 8 in > use) > rm -fr build-stamp config.h config.status missing \ > Makefile stamp* .depend .deps/ .pc/ ltmain.sh libtool \ > depcomp install-sh > rm -fr /<<PKGBUILDDIR>>/debian/libpam-shield > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pam-shield using existing > ./pam-shield_0.9.6.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: executable mode 0755 of 'build-aux/compile' will not be > represented in diff > dpkg-source: warning: executable mode 0755 of 'config.guess' will not be > represented in diff > dpkg-source: warning: executable mode 0755 of 'config.sub' will not be > represented in diff > dpkg-source: info: local changes detected, the modified files are: > pam-shield-0.9.6/Makefile.in > pam-shield-0.9.6/aclocal.m4 > pam-shield-0.9.6/build-aux/compile > pam-shield-0.9.6/build-aux/config.guess > pam-shield-0.9.6/build-aux/config.sub > pam-shield-0.9.6/build-aux/depcomp > pam-shield-0.9.6/build-aux/install-sh > pam-shield-0.9.6/build-aux/ltmain.sh > pam-shield-0.9.6/build-aux/missing > pam-shield-0.9.6/config.guess > pam-shield-0.9.6/config.h.in > pam-shield-0.9.6/config.sub > pam-shield-0.9.6/configure > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pam-shield_0.9.6-1.3.diff.k2jb85 > 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/pam-shield_0.9.6-1.3_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.
