* 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 a non-stable prior version? It seems that > would have a tendency to break for people who haven't kept up with > every update (even when running the testing distribution, and not > just when trying to backport like I am). Note: in this case I cannot speak for the Debian Autoconf package, only about the upstream Autoconf tarball (and CVS sources): Autoconf tarballs are usually generated bootstrapped with the same autoconf version. (This is done also to test it, of course.) Often, there is however no need to use that new Autoconf version. In fact, I believe Autoconf-2.60 (which has been released some days ago) can be bootstrapped with 2.59 (and the AC_PREREQ line in configure.ac reflects this). 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!) Cheers, Ralf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
