Your message dated Wed, 29 Jan 2025 14:37:34 +0000
with message-id <[email protected]>
and subject line Bug#1094400: fixed in libtool 2.5.4-2.1
has caused the Debian Bug report #1094400,
regarding libltdl-dev: uninstallable in unstable: Depends: automake-1.16 but it 
is not installable
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.)


-- 
1094400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094400
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libltdl-dev
Version: 2.5.4-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: [email protected]
Control: block -1 by 1094361

Steps to reproduce:

$ podman run --rm -it debian:sid-slim
# apt update
# apt install libltdl-dev

(or use your favourite container, chroot or VM technology)

Expected result: can install libltdl-dev

Actual result:

> Unsatisfied dependencies:
> libltdl-dev : Depends: automake-1.16 but it is not installable

This appears to be because src:libtool writes the version of Automake
that it was built against into libltdl-dev's Depends, which was added
in 2018 to handle #905841, #906507 and similar bugs.

Note that due to #1094361, it does not seem to be possible to binNMU
libtool for this, because it build-depends on (an older version of)
libltdl-dev. This seems to have been added later in 2018, for:

>   * Add build-dep on libltdl-dev for test 102

It will probably be necessary to drop that dependency, either permanently
or temporarily, and skip the relevant test at build-time. If that test
assumes libtool is already installed, maybe it can still be run as
an autopkgtest? Or maybe the test suite can be told to use whatever part
of libltdl-dev it's using (headers? shared library? macros?) from the
built tree?

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: libtool
Source-Version: 2.5.4-2.1
Done: Helmut Grohne <[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.
Helmut Grohne <[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: Wed, 29 Jan 2025 14:07:27 +0100
Source: libtool
Architecture: source
Version: 2.5.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry <[email protected]>
Changed-By: Helmut Grohne <[email protected]>
Closes: 1094400
Changes:
 libtool (2.5.4-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix aclocal version matching to cope with minor-less versions. (Closes:
     #1094400)
Checksums-Sha1:
 52e118b9ab8ff450768f5ba3a58fccc325f0b070 2378 libtool_2.5.4-2.1.dsc
 b6e3993daef4c9cada71f05b29749d6cd2e610d7 37416 libtool_2.5.4-2.1.debian.tar.xz
Checksums-Sha256:
 bbc000d0cdc56dd95ce6258ee72e35fcda57337d8b35bfbfc22e58e78a97c1f5 2378 
libtool_2.5.4-2.1.dsc
 5afd6d08ce66f1b6d78a34b3f5e1fbe5ca8f5ad2b2944c1e4feb361407baed8a 37416 
libtool_2.5.4-2.1.debian.tar.xz
Files:
 22706b5ce4279b0023691b2cfb9bd39b 2378 devel optional libtool_2.5.4-2.1.dsc
 080b7be5dbfbb78fc5f81c4fb9eceb77 37416 devel optional 
libtool_2.5.4-2.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAmeaMIMACgkQLRqqzyRE
REJKTA/+NI2arEKkvV51OzTlkKhcG1g7TM60mkaAYB0/Q+zZuMCQy+Ie/lnzjMEb
35we0p3evzrYgK1l1iZGtkkw4rSLoS5is+TE9EzpP8maKsoLldmc0qsNfvy0sI4t
PFGUq+9iV8KmLAKlwBM4TpcUGfLA2QuYRVmQPnzZ12kWzuh8TdjLIpzEidlkSOGV
kxcIRR/T4gw6fc/P8HqwrWHWEaUi5oM/DDOiteqj341UNZ494i/BpALlF4U2YvR4
XqU5+N37lx0z+PU1oNrbvfyYyILtTTiXcEAYr1eLq17XsUpvmyTKPdY0yHLI2Biw
St1hXUEodkrbz9hnNeelk39fz+Nhqz5XAeGjQul1WEgrXBcVBidSadUgY4BinTbx
/Z4ava3jXAcN1QtfGeZdS+W6HvFBhS0xsGk+ELJgn2UKDrXITC/eiY3vjPTp35LD
4Romi0lu692rKGOZayMMEL4dZh4m/Tnh1kteUxMvbAGZnDvDupkIgkLLZeKG3si8
NR1CI/O5K5UXnax1JR3DRhIKe0bmKFSZw/gXVZslsmy3xl0LYqr0JBcnhvYSIAm5
ok/rXE6iCFSIY63neE/eqwg/RhsKb8boYyinLfCtrLzEtrKijAW6VMkpoZsK/ARR
tOFROPunRXzbUzKNKYsEe9KqJ/O+HoSlOMhjatQ5+4JJwkb5xmc=
=TXkO
-----END PGP SIGNATURE-----

Attachment: pgpN1zjU9lWvJ.pgp
Description: PGP signature


--- End Message ---

Reply via email to