That said, I can't really speak for the Debian Autoconf package. If it
derives from an upstream tarball, it should not need autoconf at build
time at all. If it wishes to use an installed autoconf, it should do
fine with 2.59.
Hope this helps a bit. (And please report back problems!)
Yeah, i
* Michael Moss wrote on Fri, Jul 07, 2006 at 11:39:50PM CEST:
> Package: autoconf
> Version: 2.59.cvs.2006.06.05-1
> Severity: important
> Justification: fails to build from source
> dpkg-checkbuilddeps: Unmet build dependencies: autoconf (>=
> 2.59.cvs.2006.05.13)
>
> Is it normal to depend on
Package: autoconf
Version: 2.59.cvs.2006.06.05-1
Severity: important
Justification: fails to build from source
Trying to backport this version of autoconf fails because it depends on
a prior testing (etch) version, but that version is no longer available
because it was replaced by subsequent vers
3 matches
Mail list logo
