On Sun, Jan 22, 2012 at 04:16:22PM +0100, Eduard Bloch wrote:
> Package: dh-autoreconf
> Version: 5
> Severity: important
> File: /usr/bin/dh_autoreconf
>
> Today I failed to build a package:
>
> /var/tmp/libmediainfo-0.7.52 $ dh_autoreconf
> autoconf-wrapper: invalid number of arguments
> dh_autoreconf: autoreconf -f -i Project/GNU/Library returned exit code 255
> ed@zombie: /var/tmp/libmediainfo-0.7.52 $ dh_autoreconf -v
> find Project/GNU/Library ! -ipath "./debian/*" -a ! \( -path '*/.git/*'
> -o -path '*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*'
> \) -a -type f -exec md5sum {} \; > debian/autoreconf.before
> autoreconf -f -i Project/GNU/Library
> autoconf-wrapper: invalid number of arguments
>
> Solution: remove autoconf2.13 (which puts a diversion upon autoreconf
> binary).
It would work with autoconf2.13 if the wrapper was patched to forward
all non-option arguments (pathes in this case) to autoreconf. I'd
prefer that solution over a conflict with autoconf2.13, as developers
may have that installed or packages may want to use it for whatever
reasons.
[I could also call autoreconf with --install instead of -i by default,
which should cause the wrapper to run the new autoreconf and forward
the other arguments. But this seems a bit ugly.]
I CCed the autoconf2.13 maintainer for further input on this
topic.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
