Source: ogmtools Version: 1:1.5-4.1 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 ogmtools > dpkg-buildpackage: info: source version 1:1.5-4.1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Adrian Bunk <[email protected]> > dpkg-source --before-build . > fakeroot debian/rules clean > test -x debian/rules > rm -f debian/stamp-makefile-build debian/stamp-makefile-install > /usr/bin/make -C . -k distclean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > Making distclean in avilib > make[2]: Entering directory '/<<PKGBUILDDIR>>/avilib' > test -z "libavi.a" || rm -f libavi.a > rm -f *.o core *.core > rm -f *.tab.c > rm -rf ./.deps > rm -f Makefile > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH > make[2]: Leaving directory '/<<PKGBUILDDIR>>/avilib' > Making distclean in . > make[2]: Entering directory '/<<PKGBUILDDIR>>' > test -z "ogmmerge ogmdemux ogminfo ogmsplit ogmcat dvdxchap" || rm -f > ogmmerge ogmdemux ogminfo ogmsplit ogmcat dvdxchap > rm -f *.o core *.core > rm -f *.tab.c > rm -rf ./.deps > rm -f Makefile > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > rm -f config.status config.cache config.log configure.lineno > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > rm -f debian/stamp-autotools > rmdir --ignore-fail-on-non-empty . > rmdir: failed to remove '.': Invalid argument > make: [/usr/share/cdbs/1/class/autotools.mk:64: makefile-clean] Error 1 > (ignored) > set -e; mv ./config.guess.cdbs-orig ./config.guess; mv > ./config.sub.cdbs-orig ./config.sub; > dh_clean > dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in > use) > rm -f debian/stamp-autotools-files > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building ogmtools using existing ./ogmtools_1.5.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of directory autom4te.cache > dpkg-source: warning: ignoring deletion of file autom4te.cache/requests, use > --include-removal to override > 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/traces.0, use > --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > ogmtools-1.5/configure > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/ogmtools_1.5-4.1.diff.gXMJyv > 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/ogmtools_1.5-4.1_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.
