Bug#1044427: gtk-doc: Fails to build source after successful build

[Lucas Nussbaum]

Source: gtk-doc
Version: 1.33.2-1
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 gtk-doc
> dpkg-buildpackage: info: source version 1.33.2-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Simon McVittie <smcv at debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --with gnome,python3 --buildsystem=meson
>    dh_auto_clean -O--buildsystem=meson
>    dh_autoreconf_clean -O--buildsystem=meson
>    dh_gnome_clean -O--buildsystem=meson
>    dh_clean -O--buildsystem=meson
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building gtk-doc using existing ./gtk-doc_1.33.2.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/__init__.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/__init__.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/check.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/check.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/common.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/common.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/config.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/config.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/fixxref.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/fixxref.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/highlight.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/highlight.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/md_to_db.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/md_to_db.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/mkdb.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/mkdb.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/mkhtml.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/mkhtml.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/mkhtml2.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/mkhtml2.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/scan.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/scan.cpython-311.pyc in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to gtkdoc/__pycache__/scangobj.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add gtkdoc/__pycache__/scangobj.cpython-311.pyc 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/gtk-doc_1.33.2-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.