On Mon, 27 Jan 2025 at 19:58:04 +0000, Simon McVittie wrote:
> $ 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.
automake-1.17/1:1.17-1 added a Provides: automake-1.16 in an attempt to
address this (which I suspect might reintroduce #905841, #906507 and
similar bugs in libtool, but perhaps automake and/or libtool has changed
upstream in such a way as to avoid that), and some relevant team has
scheduled binNMUs of libtool.
Unfortunately binNMUs of libtool/2.5.4-2+b1 are now failing, because
the machinery in libtool that parses the automake Provides to find its
major/minor version number doesn't seem to work with 1.17, either because
of the new Provides or for some other reason:
> rm -f debian/libltdl-dev.substvars
> echo 'automake=automake-aclocal (GNU automake) 1.17' >
> debian/libltdl-dev.substvars
> dh_gencontrol -a
> dpkg-gencontrol: warning: can't parse dependency automake-aclocal (GNU
> automake) 1.17
> dpkg-gencontrol: error: parsing package 'libltdl-dev' Depends field: libltdl7
> (= 2.5.4-2+b1), , automake-aclocal (GNU automake) 1.17
Perhaps the output of `aclocal-1.17 --version` has changed from "1.17" to
"aclocal (GNU automake) 1.17" and the libtool packaging isn't expecting that?
smcv
