Source: cpdb-libs Version: 1.2.0-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 cpdb-libs > dpkg-buildpackage: info: source version 1.2.0-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Thorsten Alteholz > <deb...@alteholz.de> > dpkg-source --before-build . > debian/rules clean > dh clean > debian/rules override_dh_auto_clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > [ ! -r Makefile ] || make distclean > make[2]: Entering directory '/<<PKGBUILDDIR>>' > Making distclean in lib > make[3]: Entering directory '/<<PKGBUILDDIR>>/lib' > test -z "libcpdb-libs-frontend.la libcpdb-libs-common.la" || rm -f > libcpdb-libs-frontend.la libcpdb-libs-common.la > rm -f ./so_locations > rm -rf .libs _libs > rm -f *_interface.* > rm -f *.o > rm -f *.lo > rm -f *.tab.c > test -z "" || rm -f > test . = "." || test -z "" || rm -f > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > rm -f ./.deps/libcpdb_libs_common_la-backend_interface.Plo > rm -f ./.deps/libcpdb_libs_common_la-common_helper.Plo > rm -f ./.deps/libcpdb_libs_common_la-frontend_interface.Plo > rm -f ./.deps/libcpdb_libs_frontend_la-frontend_helper.Plo > rm -f Makefile > make[3]: Leaving directory '/<<PKGBUILDDIR>>/lib' > make[3]: Entering directory '/<<PKGBUILDDIR>>' > rm -rf .libs _libs > rm -f *.lo > test -z "cpdb-libs-backend.pc cpdb-libs-frontend.pc cpdb-libs-common.pc" || > rm -f cpdb-libs-backend.pc cpdb-libs-frontend.pc cpdb-libs-common.pc > test . = "." || test -z "" || rm -f > 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 > make[3]: Leaving directory '/<<PKGBUILDDIR>>' > rm -f config.status config.cache config.log configure.lineno > config.status.lineno > rm -f Makefile > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > rm -f lib/cpd-interface-headers > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_autoreconf_clean > dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building cpdb-libs using existing > ./cpdb-libs_1.2.0.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: error: cannot represent change to demo/print_frontend: binary > file contents changed > dpkg-source: error: add demo/print_frontend in debian/source/include-binaries > if you want to store the modified binary in the debian tarball > dpkg-source: warning: executable mode 0755 of 'demo/print_frontend' will not > be represented in diff > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1 > > 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/cpdb-libs_1.2.0-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.
