[Pkg-freeipa-devel] Bug#1044048: certmonger: Fails to build source after successful build

[Lucas Nussbaum]

Source: certmonger
Version: 0.79.17-2
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa at 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 certmonger
> dpkg-buildpackage: info: source version 0.79.17-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Timo Aaltonen <tjaalton at debian.org>
>  dpkg-source --before-build .
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: applying cross.patch
> dpkg-source: info: applying fix-keythi-h-path.diff
> dpkg-source: info: applying fix-service-environment.diff
> dpkg-source: info: applying use-dbus-run-session.diff
> dpkg-source: info: applying dont-require-an-nss-database.diff
>  fakeroot debian/rules clean
> dh clean --with quilt --builddirectory=build/
>    dh_auto_clean -O--builddirectory=build/
>    dh_autoreconf_clean -O--builddirectory=build/
>    dh_quilt_unpatch -O--builddirectory=build/
> Removing patch dont-require-an-nss-database.diff
> Restoring src/keygen-n.c
> Restoring src/scepgen-n.c
> Restoring src/submit-n.c
> Restoring src/keyiread-n.c
> Restoring src/certsave-n.c
> Restoring src/certread-n.c
> 
> Removing patch use-dbus-run-session.diff
> Restoring tests/run-tests.sh
> Restoring tests/Makefile.am
> 
> Removing patch fix-service-environment.diff
> Restoring systemd/certmonger.service.in
> 
> Removing patch fix-keythi-h-path.diff
> Restoring configure.ac
> 
> Removing patch cross.patch
> Restoring configure.ac
> 
> No patches applied
>    debian/rules override_dh_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_clean
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: applying cross.patch
> dpkg-source: info: applying fix-keythi-h-path.diff
> dpkg-source: info: applying fix-service-environment.diff
> dpkg-source: info: applying use-dbus-run-session.diff
> dpkg-source: info: applying dont-require-an-nss-database.diff
> dpkg-source: info: building certmonger using existing ./certmonger_0.79.17.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: error: cannot represent change to po/bg.gmo: binary file contents changed
> dpkg-source: error: add po/bg.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ca.gmo: binary file contents changed
> dpkg-source: error: add po/ca.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/cs_CZ.gmo: binary file contents changed
> dpkg-source: error: add po/cs_CZ.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/da.gmo: binary file contents changed
> dpkg-source: error: add po/da.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/de.gmo: binary file contents changed
> dpkg-source: error: add po/de.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/es.gmo: binary file contents changed
> dpkg-source: error: add po/es.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/eu.gmo: binary file contents changed
> dpkg-source: error: add po/eu.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/fr.gmo: binary file contents changed
> dpkg-source: error: add po/fr.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/gu.gmo: binary file contents changed
> dpkg-source: error: add po/gu.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/hu.gmo: binary file contents changed
> dpkg-source: error: add po/hu.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/id.gmo: binary file contents changed
> dpkg-source: error: add po/id.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/it.gmo: binary file contents changed
> dpkg-source: error: add po/it.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ja.gmo: binary file contents changed
> dpkg-source: error: add po/ja.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ka.gmo: binary file contents changed
> dpkg-source: error: add po/ka.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ko.gmo: binary file contents changed
> dpkg-source: error: add po/ko.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/lt.gmo: binary file contents changed
> dpkg-source: error: add po/lt.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/nb.gmo: binary file contents changed
> dpkg-source: error: add po/nb.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/nl.gmo: binary file contents changed
> dpkg-source: error: add po/nl.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/pl.gmo: binary file contents changed
> dpkg-source: error: add po/pl.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/pt.gmo: binary file contents changed
> dpkg-source: error: add po/pt.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/pt_BR.gmo: binary file contents changed
> dpkg-source: error: add po/pt_BR.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ru.gmo: binary file contents changed
> dpkg-source: error: add po/ru.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/si.gmo: binary file contents changed
> dpkg-source: error: add po/si.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/sv.gmo: binary file contents changed
> dpkg-source: error: add po/sv.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ta.gmo: binary file contents changed
> dpkg-source: error: add po/ta.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/tr.gmo: binary file contents changed
> dpkg-source: error: add po/tr.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/uk.gmo: binary file contents changed
> dpkg-source: error: add po/uk.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/zh_CN.gmo: binary file contents changed
> dpkg-source: error: add po/zh_CN.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/zh_TW.gmo: binary file contents changed
> dpkg-source: error: add po/zh_TW.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> 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/certmonger_0.79.17-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.