[Pkg-privacy-maintainers] Bug#1046975: txtorcon: Fails to build source after successful build

[Lucas Nussbaum]

Source: txtorcon
Version: 22.0.0-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 txtorcon
> dpkg-buildpackage: info: source version 22.0.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Antoine Beaupré <anarcat at debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --with=python3,sphinxdoc --buildsystem=pybuild
>    dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:275: python3.11 setup.py clean 
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_txtorcon/build' (and everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
>    dh_autoreconf_clean -O--buildsystem=pybuild
>    dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: verifying ./txtorcon_22.0.0.orig.tar.gz.asc
> gpgv: Signature made Wed Mar 16 21:28:53 2022 UTC
> gpgv:                using RSA key 9D5A2BD5688ECB889DEBCD3FC2602803128069A7
> gpgv:                issuer "meejah at meejah.ca"
> gpgv: [don't know]: invalid packet (ctb=2d)
> gpgv: keydb_search failed: Invalid packet
> gpgv: [don't know]: invalid packet (ctb=2d)
> gpgv: keydb_search failed: Invalid packet
> gpgv: Can't check signature: No public key
> dpkg-source: warning: cannot verify upstream tarball signature for ./txtorcon_22.0.0.orig.tar.gz: no acceptable signature found
> dpkg-source: info: building txtorcon using existing ./txtorcon_22.0.0.orig.tar.gz
> dpkg-source: info: building txtorcon using existing ./txtorcon_22.0.0.orig.tar.gz.asc
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: newly created empty file '_trial_temp/_trial_marker' will not be represented in diff
> dpkg-source: warning: file txtorcon-22.0.0/_trial_temp/authcookie has no final newline (either original or modified version)
> dpkg-source: warning: file txtorcon-22.0.0/_trial_temp/test.test_controller/FilesystemOnionFactoryTests/test_happy_path/ggttwk0b/temp/hs_ed25519_secret_key has no final newline (either original or modified version)
> diff: txtorcon-22.0.0/_trial_temp/test.test_endpoints/EndpointTests/test_explit_dir_not_readable_ver/7aq5jxd2/temp/hostname: Permission denied
> dpkg-source: error: diff on txtorcon-22.0.0/_trial_temp/test.test_endpoints/EndpointTests/test_explit_dir_not_readable_ver/7aq5jxd2/temp/hostname subprocess returned exit status 2
> 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/txtorcon_22.0.0-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.