[Pkg-telepathy-maintainers] Bug#1047529: telepathy-spec: Fails to build source after successful build

[Lucas Nussbaum]

Source: telepathy-spec
Version: 0.27.4-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 telepathy-spec
> dpkg-buildpackage: info: source version 0.27.4-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Laurent Bigonville <bigon at debian.org>
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean
>    dh_auto_clean
> 	make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -f doc/spec/index.html FIXME.out 
> rm -rf test/output
> rm -rf tmp
> rm -rf doc/spec
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: verifying ./telepathy-spec_0.27.4.orig.tar.gz.asc
> gpgv: Signature made Sat Nov 16 12:43:08 2019 UTC
> gpgv:                using RSA key AA33B0D27868E36C151780F0FE0B6D736B1195ED
> gpgv: Note: signatures using the SHA1 algorithm are rejected
> gpgv: Can't check signature: Bad public key
> dpkg-source: warning: cannot verify upstream tarball signature for ./telepathy-spec_0.27.4.orig.tar.gz: no acceptable signature found
> dpkg-source: info: building telepathy-spec using existing ./telepathy-spec_0.27.4.orig.tar.gz
> dpkg-source: info: building telepathy-spec using existing ./telepathy-spec_0.27.4.orig.tar.gz.asc
> dpkg-source: error: cannot represent change to tools/__pycache__/specparser.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add tools/__pycache__/specparser.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 tools/__pycache__/xincludator.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add tools/__pycache__/xincludator.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/telepathy-spec_0.27.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.