Your message dated Sun, 07 Dec 2025 12:49:20 +0000
with message-id <[email protected]>
and subject line Bug#1122013: fixed in libtool 2.5.4-8
has caused the Debian Bug report #1122013,
regarding libtool: d/rules "clean" target does not fully restore the build
environment
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.)
--
1122013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122013
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:libtool
Version: 2.5.4-7
Severity: minor
Tags: patch
Dear libtool maintainer,
this package does not currently leave the build environment in a way
that is compatible with re-running the build in place. For example,
running inside sbuild with the extra commands described at
<https://wiki.debian.org/sbuild#Validate_package_cleanup> shows that
many files have been deleted (OK, they will regenerated by ./bootstrap)
or are left modified.
Leaving the package in a clean state is something that not many package
maintainers care about but given the amount of code present in d/rules
in 2.5.4-7 to deal with various removals, I assume it is of value to you.
You can find a commit to fix all these issues and fully restore the
package to a clean state at the end of this MR
https://salsa.debian.org/mckinstry/libtool/-/merge_requests/2
(The commit builds on top of the standard dh sequence commit mentioned
in #1122012.)
Kind regards,
--
Gioele Barabucci
--- End Message ---
--- Begin Message ---
Source: libtool
Source-Version: 2.5.4-8
Done: Alastair McKinstry <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libtool, 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.
Alastair McKinstry <[email protected]> (supplier of updated libtool 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: Sun, 07 Dec 2025 12:19:28 +0000
Source: libtool
Architecture: source
Version: 2.5.4-8
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry <[email protected]>
Changed-By: Alastair McKinstry <[email protected]>
Closes: 286341 733935 1122012 1122013
Changes:
libtool (2.5.4-8) unstable; urgency=medium
.
[ Cyril Brulebois ]
* Fix sanitation of libtool vs. libtoolize; the former is shipped in
libtool-bin (arch:any, so binary-arch target), the latter in libtool
(arch:all, so binary-indep target).
* Use a single sed call (no pipefail in dash).
* Make sure failures are noticed inside for loops.
* Unhardcode upstream version from sanitation loops.
.
[ Gioele Barabucci ]
* d/rules: Use standard `dh` sequence to d/rules (Closes: #1122012, #1122013)
.
[ Alastair McKinstry ]
* Close previously fixed bugs. Closes: #286341, #733935
Checksums-Sha1:
65055f2cf6d050804d57097c7ba57319a711454e 2240 libtool_2.5.4-8.dsc
96daaee038bc1f7810d5b5a09457cc9d01c190af 41712 libtool_2.5.4-8.debian.tar.xz
Checksums-Sha256:
c6e076153fa6e39ce0c608cf0d1ef67ca162805d5b7e274b6a556bc4eadd1734 2240
libtool_2.5.4-8.dsc
e1e90dd340c2949c301f11a32a1eb46d08e96ef947427aa2d4cd3293f671a200 41712
libtool_2.5.4-8.debian.tar.xz
Files:
9a638b8cb01f95053dda6b45f9b0973a 2240 devel optional libtool_2.5.4-8.dsc
23463f5b3dd0c55295c29e3633d08274 41712 devel optional
libtool_2.5.4-8.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmk1dFcACgkQy+a7Tl2a
06XNwA//Q3ykllk753u2dtcdpjtxsywkM8JQkFRI2+j1y0weiY1P0W+dSONkLsvF
HXIZdttgWb9wcT7IKNYitD82wupaa7+OvdwO/J4N8P4OgxV7qGb4P7EMcrcqnk5w
48k2rTzCgLzO06SzBC4hu/YFsLf0qjLYMezXTz3rni6XO9mZLNVO3hgksJq9Fcd4
4ZEvC469q+Dm2k/1tYafwMZy0+x5kQ9hGH9uSGpcMYhxUoR7yf/dRAF5138Kb6E/
bPytVxIthvCmv8hzRFGGog3QMCJeL/FwBUAFCW6JQdk1hlwvGcRMeyoV83X22vIk
o2EVHktI5d/zJepme/eqrjNgvtAa9Rym+lkqCS5wTMl372JTCbmxZzTylxCal34h
/6xTuJoeTd/1ITFlyJHFZGTNL19yzkIdtIi8RQnXi6cE9Sz4qNwlM0REYxq7BXLx
oXa1Czq9ZR4212BCNCA5lbjzfXCHIs8AGltYXkjjyvl5N3Ie70opXAVwCaEprQPU
MI/8ZguypYVt8nHo/fs6WXLhbZD0nF7jZM3tLXN4Z5soUCvSq2eBS0erh7gyZpDF
41F+2ey1xIdXZ4e9m64ZVdrOpy3iDJbAz8fypfz8sTJTrRcliZIu89qwEospjooT
e76wHdWcmgVvtMMyr47NrzJf/sPE27uQRnTYfwbmn27uU2IoR7s=
=4/bm
-----END PGP SIGNATURE-----
pgp_p80iKf5Gh.pgp
Description: PGP signature
--- End Message ---
