unarchive 1118317
notfixed 1118317 2.5.4-6
reassign 1147934 libltdl-dev 2.6.2-2
reassign 1147935 libltdl-dev 2.6.2-2
reassign 1147936 libltdl-dev 2.6.2-2
reassign 1147937 libltdl-dev 2.6.2-2
reassign 1147938 libltdl-dev 2.6.2-2
forcemerge 1118317 1147934 1147935 1147936 1147937 1147938
affects 1118317 + src:redland src:squid
clone 1147935 -1
reassign -1 automake 1:1.19-2
retitle -1 Consider dropping alternatives handling as there are no alternatives
to set
severity -1 minor
thanks
Santiago Vila wrote:
> Package: src:parser
> Version: 3.5.1-3
> Severity: serious
> Tags: ftbfs forky sid
> [...]
> make[5]: Leaving directory '/<<PKGBUILDDIR>>/src/lib/cord'
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/lib/cord'
> Making all in ltdl
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src/lib/ltdl'
> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash '/<<PKGBUILDDIR>>/missing'
> aclocal-1.18 -I m4
> /<<PKGBUILDDIR>>/missing: line 85: aclocal-1.18: command not found
> WARNING: 'aclocal-1.18' is missing on your system.
> You should only need it if you modified 'acinclude.m4' or
> 'configure.ac' or m4 files included by 'configure.ac'.
> make[4]: *** [Makefile:566: aclocal.m4] Error 127
Every time there is a new major Automake release, this problem
resurfaces. Ideally, it should be addressed in src:libtool by either
1) Ensure that as soon as a new major Automake release is uploaded
to unstable, a libtool sourceful upload is being made before
Santiago (or Lucas) discovers that some packages FTBFS.
2) Patch the libtool files (/usr/share/libtool/aclocal.m4, etc.) so
that they don't require a specific Automake version or do some
tricks like AUTOMAKE=automake and ACLOCAL=aclocal (these are
versionless symlinks currently handled by dpkg-alternatives which I
believe is a remnant from the old automake packaging when every new
major release was a separate source package).
