Your message dated Mon, 23 Dec 2024 21:50:03 +0000
with message-id <e1tpqjp-003z8h...@fasolo.debian.org>
and subject line Bug#1046485: fixed in libbitarray 2.0-3
has caused the Debian Bug report #1046485,
regarding libbitarray: 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.)
--
1046485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbitarray
Version: 2.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 libbitarray
> dpkg-buildpackage: info: source version 2.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille <ti...@debian.org>
> dpkg-source --before-build .
> debian/rules clean
> dh clean
> dh_auto_clean
> make -j8 clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -rf libbitarr.a *.o *.dSYM *.greg
> cd dev && make clean
> make[2]: Entering directory '/<<PKGBUILDDIR>>/dev'
> rm -rf bit_array_test bitlock_test bit_array_generate
> rm -rf bitarr_example.dump *.o *.dSYM *.greg
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/dev'
> cd examples && make clean
> make[2]: Entering directory '/<<PKGBUILDDIR>>/examples'
> rm -rf example_cpp example_c *.o *.dSYM *.greg
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/examples'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building libbitarray using existing
> ./libbitarray_2.0.orig.tar.gz
> dpkg-source: error: cannot represent change to dev/bitlock_try_test: binary
> file contents changed
> dpkg-source: error: add dev/bitlock_try_test in
> debian/source/include-binaries if you want to store the modified binary in
> the debian tarball
> dpkg-source: warning: executable mode 0755 of 'dev/bitlock_try_test' will not
> be represented in diff
> 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/libbitarray_2.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: libbitarray
Source-Version: 2.0-3
Done: Andreas Tille <ti...@debian.org>
We believe that the bug you reported is fixed in the latest version of
libbitarray, 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 1046...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated libbitarray 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: SHA256
Format: 1.8
Date: Mon, 23 Dec 2024 21:35:39 +0100
Source: libbitarray
Architecture: source
Version: 2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
<debian-med-packag...@lists.alioth.debian.org>
Changed-By: Andreas Tille <ti...@debian.org>
Closes: 1046485
Changes:
libbitarray (2.0-3) unstable; urgency=medium
.
* Fix clean target
Closes: #1046485
* Standards-Version: 4.7.0 (routine-update)
Checksums-Sha1:
03463a21fc9504733fe67a70997017e04c59c952 2033 libbitarray_2.0-3.dsc
e372ea5664e3e7e1365f4f74e1933ae3260842f2 4956 libbitarray_2.0-3.debian.tar.xz
6759ddfc1ad5e4201247ffca2601227eda958d96 6061 libbitarray_2.0-3_amd64.buildinfo
Checksums-Sha256:
802248e28c2c7e37a1d866345f34a48b024ec9428ca0837b6d810f7b0f6fae6f 2033
libbitarray_2.0-3.dsc
6061b0d8c9a425a48248c55f34a98e343b419285b415b80f54ff43dcc9386739 4956
libbitarray_2.0-3.debian.tar.xz
d0841fdc6d146624e1ce35f172583d7f1d67f22f7ed925a4429babb6b012b6b3 6061
libbitarray_2.0-3_amd64.buildinfo
Files:
66b719f1e17416d2631322d0163c191a 2033 science optional libbitarray_2.0-3.dsc
e24329bca291d1d0fea44658524b75bc 4956 science optional
libbitarray_2.0-3.debian.tar.xz
844af320c08edb7673ad23818ab82bce 6061 science optional
libbitarray_2.0-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmdp11IRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFhwxAAiHvApV4d6zr2QdiaO/e0cU6ItYd8O4zx
H+n2IDqDK/oiwsCxH35hqKta4NPJvWQaSNhTOzac9Wppog6ZnmuffRIpJab03jME
fnBqe0NDOmLgZejTPeiRUm+Fby8q/6KCd9GgnfGhsVdHtW4dh3ylKiMTD6Y289Wg
Co7lvcHQEB0lY/0GN49NNSK93vycaP0t8BFLEwXXOuJRhaLuXuBhVC1yGkzP3Z8R
S7bmgdHeqyrMru+0bhsEfNZO6emKjqlKqETfkxHjJ+ffwAHYL4Z5USehVYVRItj+
Ny3dJAngVfiCyKT9QBOLpN2Tv1MY2/PbiN8lv/e7OnRTt+YFzoh5032oRPIN/5AF
QgOIal3nj7aPyR5ujHOxSZ6mC9bdZtsk6o3NLIe0EZGkwdel1/sio38R8fcHZCho
Z8zd227hQNmukWwuQ+LNPAgoTlz1yiyDo36uGdiH1CoEUmvjdGMmFYwOhLYQy4md
yinhhyJd6VAPCpfc1DnL5cL3EP92wusQtcpigVm4pTmCUnNrFxRrB+Y2GQgmSigV
EQNrOYpF8XeUgdBEHfMJEtS8c7RzmhZpdIuIN6+GfHY9bbVvt2KJLEW9Q19YzoXq
Ez6vt09ztPe1IBq01HJ9TGp71ASoF/VAJiwYov8vwZOndHkDACF5QiDb4jo1ybJY
rKkWqVvXg74=
=/SZs
-----END PGP SIGNATURE-----
pgpHT91sPhGzB.pgp
Description: PGP signature
--- End Message ---
