Your message dated Wed, 14 Aug 2024 01:49:04 +0000 with message-id <e1se38k-00b8rs...@fasolo.debian.org> and subject line Bug#1045019: fixed in dex 0.10.1-1 has caused the Debian Bug report #1045019, regarding dex: 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 ow...@bugs.debian.org immediately.) -- 1045019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: dex Version: 0.9.0-2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@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 dex > dpkg-buildpackage: info: source version 0.9.0-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by James McCoy <james...@debian.org> > dpkg-source --before-build . > debian/rules clean > dh clean --with python3 > dh_auto_clean > make -j8 clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > /bin/sh: 1: git: not found > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building dex using existing ./dex_0.9.0.orig.tar.gz > dpkg-source: error: cannot represent change to .doctrees/dex.doctree: binary > file contents changed > dpkg-source: error: add .doctrees/dex.doctree in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: cannot represent change to .doctrees/environment.pickle: > binary file contents changed > dpkg-source: error: add .doctrees/environment.pickle 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/dex_0.9.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: dex Source-Version: 0.10.1-1 Done: James McCoy <james...@debian.org> We believe that the bug you reported is fixed in the latest version of dex, 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 1045...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy <james...@debian.org> (supplier of updated dex 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 13 Aug 2024 21:35:50 -0400 Source: dex Architecture: source Version: 0.10.1-1 Distribution: unstable Urgency: medium Maintainer: James McCoy <james...@debian.org> Changed-By: James McCoy <james...@debian.org> Closes: 1045019 Changes: dex (0.10.1-1) unstable; urgency=medium . * New upstream release + Remove sphinx-generated during clean (Closes: #1045019) * Bump copyright years in debian/copyright * Declare compliance with Policy 4.7.0, no changes needed * Update watch file to version 4 and mode=git Checksums-Sha1: 6b002cbe491a8949c316813b611f6c3a6fbfd253 2071 dex_0.10.1-1.dsc 2178d46f1ca7e27fa1965b83830317044695e8ae 11732 dex_0.10.1.orig.tar.xz c68ebdf04ff0d3f0bb02049e2d3aaa85baadc721 2800 dex_0.10.1-1.debian.tar.xz Checksums-Sha256: 6b86e16ff0aab6fb3cdcb2d405702d7c8d16de4b99b0396c97474194faaff157 2071 dex_0.10.1-1.dsc 05efce2a41fc98e775247e35607da2cb82fd96284b1da1c62060628865f25fee 11732 dex_0.10.1.orig.tar.xz c549f825a8125b1f852863d68fd121160230b05cbfbb9eacd8084f46d0356dc6 2800 dex_0.10.1-1.debian.tar.xz Files: ae1068645ccd0df23aa6d9b4db3a0ffe 2071 x11 optional dex_0.10.1-1.dsc 7811adac2cf4a1590047382f6876f131 11732 x11 optional dex_0.10.1.orig.tar.xz 69e914466db4e8c62641b2f3b137b835 2800 x11 optional dex_0.10.1-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAma8CnNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9sHxw/6AtmcdDfqEsqgI+wYFG/jb097jxtl rSoe9Z+eSnG96u7VdE0Ddj4eS7TNwcXDzof796hnPSJPB3NbAOO/legFR/eaHCCN E/Pvnjz1uWVCyflyhxq1jcybw+xbGhgHwNtnWbOY8dI015D6Q1PelKty6P6NEJw1 0QHyghyoH8W1CIUC78wriKMFj95uiSsc7tNm6nRImdJ6Djay9MhRUE/KIHxdDRbZ 14JiMn6XpuTE+qbUu9OwlLa+2ODpcS+j9sjN8bUY4pJbqDI6cFnec0o/AJbbdZCt zpaoF7ML2PErQ8Tfh3woC1sZvToEeBAQxWwIR5p/vUJidrHI6Sj0CzO6MerJVEJ+ r936xtibgcFer5Wd0fybctkjS1MAsdS9Mkt+roGqDc7ZkO/pmZBQKmlvP6SbvKUH XfNC7y1HttYfGKrSunxBsV4Ca4cfAZJ9CBbrPNr+2SdhlOwIVmo1dqdZscH+W9WC yJ/0R3ZNnkdXBG28AqU6spPRWcfWWUgy6UgvDhPomWw/cflaKopwZ610TVoIQQ34 zfTLhA+hGDTkJaTgHixBLNJGQ5G2ChZaiC+uADWr5k9OV4fdWbIq66Kga1SFjd39 AJCmeUffKaO+43N2VUpAHKKGyefPcYDo7BfuOtv+DGvJcR9v3zhX0IYqVG/9R6IQ QGvzf81YKY9i9+o= =QUMm -----END PGP SIGNATURE-----pgpH4ZwZZ9TOL.pgp
Description: PGP signature
--- End Message ---