Source: sqlcipher Version: 3.4.1-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 sqlcipher > dpkg-buildpackage: info: source version 3.4.1-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Hans-Christoph Steiner > <[email protected]> > dpkg-source --before-build . > debian/rules clean > dh clean > dh_auto_clean > make -j8 distclean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > rm -f *.lo *.la *.o sqlcipher libsqlcipher.la > rm -f sqlite3.h opcodes.* > rm -rf .libs .deps > rm -f lemon lempar.c parse.* sqlite*.tar.gz > rm -f mkkeywordhash keywordhash.h > rm -f *.da *.bb *.bbg gmon.out > rm -rf tsrc .target_source > rm -f tclsqlcipher > rm -f testfixture test.db > rm -f LogEst fts3view rollback-test showdb > rm -f showjournal showstat4 showwal speedtest1 > rm -f wordcount changeset > rm -f sqlite3.dll sqlite3.lib sqlite3.exp sqlite3.def > rm -f sqlite3.c > rm -f sqlite3rc.h > rm -f shell.c sqlite3ext.h > rm -f sqlite3_analyzer sqlite3_analyzer.c > rm -f sqlite-*-output.vsix > rm -f mptester mptester.exe > rm -f rbu rbu.exe > rm -f srcck1 srcck1.exe > rm -f fuzzershell fuzzershell.exe > rm -f fuzzcheck fuzzcheck.exe > rm -f sqldiff sqldiff.exe > rm -f dbhash dbhash.exe > rm -f fts5.* fts5parse.* > rm -f config.h config.log config.status libtool Makefile sqlcipher.pc > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_autoreconf_clean > dh_clean > dpkg-source -b . > dpkg-source: warning: upstream signing key but no upstream tarball signature > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building sqlcipher using existing > ./sqlcipher_3.4.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of file install-sh, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file aclocal.m4, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file ltmain.sh, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file configure, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file config.h.in, use > --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > sqlcipher-3.4.1/sqlite3session.h > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/sqlcipher_3.4.1-2.diff.Y9Q5U1 > 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/sqlcipher_3.4.1-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.
