Your message dated Wed, 11 Feb 2026 10:35:14 +0000
with message-id <[email protected]>
and subject line Bug#1048850: fixed in python-hacking 4.1.0-5
has caused the Debian Bug report #1048850,
regarding python-hacking: Fails to build source after successful build
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1048850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048850
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-hacking
Version: 4.1.0-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 python-hacking
> dpkg-buildpackage: info: source version 4.1.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Thomas Goirand <[email protected]>
> dpkg-source --before-build .
> dpkg-source: info: using options from
> python-hacking-4.1.0/debian/source/options:
> --extend-diff-ignore=^[.]gitreview$
> fakeroot debian/rules clean
> make: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> dh clean --buildsystem=python_distutils --with python3,sphinxdoc
> debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> rm -rf .testrepository
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_autoreconf_clean -O--buildsystem=python_distutils
> dh_clean -O--buildsystem=python_distutils
> dpkg-source -b .
> dpkg-source: info: using options from
> python-hacking-4.1.0/debian/source/options:
> --extend-diff-ignore=^[.]gitreview$
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-hacking using existing
> ./python-hacking_4.1.0.orig.tar.xz
> dpkg-source: warning: newly created empty file
> 'build/lib/hacking/__init__.py' will not be represented in diff
> dpkg-source: warning: newly created empty file
> 'build/lib/hacking/checks/__init__.py' will not be represented in diff
> dpkg-source: warning: newly created empty file
> 'build/lib/hacking/tests/checks/__init__.py' will not be represented in diff
> dpkg-source: warning: file python-hacking-4.1.0/hacking.egg-info/SOURCES.txt
> has no final newline (either original or modified version)
> dpkg-source: error: cannot represent change to
> hacking/__pycache__/__init__.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add hacking/__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
> hacking/__pycache__/config.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add hacking/__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
> hacking/__pycache__/core.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add hacking/__pycache__/core.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
> hacking/checks/__pycache__/__init__.cpython-311.pyc: binary file contents
> changed
> dpkg-source: error: add hacking/checks/__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
> hacking/checks/__pycache__/comments.cpython-311.pyc: binary file contents
> changed
> dpkg-source: error: add hacking/checks/__pycache__/comments.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
> hacking/checks/__pycache__/except_checks.cpython-311.pyc: binary file
> contents changed
> dpkg-source: error: add
> hacking/checks/__pycache__/except_checks.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
> hacking/checks/__pycache__/mock_checks.cpython-311.pyc: binary file contents
> changed
> dpkg-source: error: add
> hacking/checks/__pycache__/mock_checks.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
> hacking/checks/__pycache__/other.cpython-311.pyc: binary file contents changed
> dpkg-source: error: add hacking/checks/__pycache__/other.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
> hacking/tests/__pycache__/__init__.cpython-311.pyc: binary file contents
> changed
> dpkg-source: error: add hacking/tests/__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
> hacking/tests/__pycache__/test_config.cpython-311.pyc: binary file contents
> changed
> dpkg-source: error: add hacking/tests/__pycache__/test_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
> hacking/tests/__pycache__/test_doctest.cpython-311.pyc: binary file contents
> changed
> dpkg-source: error: add
> hacking/tests/__pycache__/test_doctest.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
> hacking/tests/__pycache__/test_import_exceptions.cpython-311.pyc: binary file
> contents changed
> dpkg-source: error: add
> hacking/tests/__pycache__/test_import_exceptions.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
> hacking/tests/checks/__pycache__/__init__.cpython-311.pyc: binary file
> contents changed
> dpkg-source: error: add
> hacking/tests/checks/__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
> hacking/tests/checks/__pycache__/test_comments.cpython-311.pyc: binary file
> contents changed
> dpkg-source: error: add
> hacking/tests/checks/__pycache__/test_comments.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
> hacking/tests/checks/__pycache__/test_except_checks.cpython-311.pyc: binary
> file contents changed
> dpkg-source: error: add
> hacking/tests/checks/__pycache__/test_except_checks.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
> hacking/tests/checks/__pycache__/test_mock.cpython-311.pyc: binary file
> contents changed
> dpkg-source: error: add
> hacking/tests/checks/__pycache__/test_mock.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
> hacking/tests/checks/__pycache__/test_other.cpython-311.pyc: binary file
> contents changed
> dpkg-source: error: add
> hacking/tests/checks/__pycache__/test_other.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/python-hacking_4.1.0-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.
--- End Message ---
--- Begin Message ---
Source: python-hacking
Source-Version: 4.1.0-5
Done: Thomas Goirand <[email protected]>
We believe that the bug you reported is fixed in the latest version of
python-hacking, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand <[email protected]> (supplier of updated python-hacking package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 11 Feb 2026 11:20:42 +0100
Source: python-hacking
Architecture: source
Version: 4.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack <[email protected]>
Changed-By: Thomas Goirand <[email protected]>
Closes: 1048850
Changes:
python-hacking (4.1.0-5) unstable; urgency=medium
.
* Cleans better (Closes: #1048850).
Checksums-Sha1:
e7d2534dc27e2ac9832397ce4676853ef5c35e0a 2542 python-hacking_4.1.0-5.dsc
cad7cbcb56395aadb0ddb53e8d8f8265c1567fec 3980
python-hacking_4.1.0-5.debian.tar.xz
55d80d1e6294c483decce30f80de0bbd5c4462a1 10253
python-hacking_4.1.0-5_amd64.buildinfo
Checksums-Sha256:
903b51c1b856178917d8e0a900065fd0e49a68398cca450d67ebfe11bd871409 2542
python-hacking_4.1.0-5.dsc
b6b7ea5587c49afab3a105bc884829f729f040de4fb95bd1ae19d14a45e44a81 3980
python-hacking_4.1.0-5.debian.tar.xz
277df63ff2387b60715dae594686a365d68d776ad2adb403c50b034adb2fec90 10253
python-hacking_4.1.0-5_amd64.buildinfo
Files:
ebc87e175299665c1cc2ed50af80b733 2542 python optional
python-hacking_4.1.0-5.dsc
fa64629624d858107e01b7e1084d8390 3980 python optional
python-hacking_4.1.0-5.debian.tar.xz
087533c57a033efe70652bf9fc5932d6 10253 python optional
python-hacking_4.1.0-5_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmmMWGwACgkQ1BatFaxr
Q/67Pw/8CAzd8Gg47Z0BzuDT/r4Oe4IsiXKqkZ0h7IIFqVpzXA0ORSI01Yt6toeH
RDzqIqPQM3iHqtpqwUWV+NzdTyTQHzpY7q4R2YuKSlrRvrzBhPUoVqJIeZKKDf2O
Mr93JRcnB0y1lUwJx24FVWoVFZX0fP8VPbDtSuK3k4NMNXvmbJasqrVQKxwvHPvP
OE4awZrakqA9kNWSn/tvc/XSuai+B8NttpXBE6JpzipjizNxbvT/55NJ6f3fn8Hy
gG6HnL2xk4XMbbENrTpwKUUdLCNYo2GX3od0ozkWPM6+qTPsH9ywNTLuJi/WMlzS
scsJQT/kcow/eLvRarrKXD6zgu97jaznxdlHX5Gp+s95bpSM42gM6aSArInbWpVQ
OzvXYmKrpgkVthXwrzXfZ60Au3yugAbmxSkEnNX5pm0c2A4tsnwlY8z6FemlgH/X
A3igFk8aEmLbunGpmyQJzf4hClrkI9m09wnw9G8gVggujMTLhw0YaVr8cvEUDhUq
GyaWxS94huixw+ToSLUV73EVakxXqzmUsNQUV2Hzey+m8d6JznEUxLcIHFzxw7Sy
BBST/+Cgwu9KKoX7/YIvNUJNJG3eraUlJ7XiivXgUpSBaqWinygWPFN5nsrFgRhR
02GUUfv1uBRkzqVhG5Dmt5nF8ObHgyV57CbkBIFkSPpxiFYrEtk=
=eUtJ
-----END PGP SIGNATURE-----
pgp050ny_X7WX.pgp
Description: PGP signature
--- End Message ---
