Comment 2 for bug 478334

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package autoconf - 2.64-4ubuntu1

---------------
autoconf (2.64-4ubuntu1) lucid; urgency=low

  * Merge from debian testing, remaining changes: LP: #478334
    - bin/autoreconf.in: Check whether libtoolize supports --install, if it
      does, libtoolize is safe to run at all times since it will not install
      new files unless --install is passed to it as well.
  * Fixes autoconf requires m4 LP: #459422
  * Fixes autoconf suggests installing autobook LP: #372701

autoconf (2.64-4) unstable; urgency=low

  * Add back Suggests: autoconf-archive removed in 2.64-3. I did check
    whether that package still existed, but somehow I got it
    wrong--perhaps a typo. Thanks to Guillem Jover <email address hidden>
    for pointing out my mistake.

autoconf (2.64-3) unstable; urgency=low

  * Remove Suggests: autobook, autoconf-archive, because these packages
    are no longer in Debian. Thanks to Vincent Bernat <email address hidden>
    for pointing this out. Closes: #548025.

autoconf (2.64-2) unstable; urgency=low

  * Require m4 version 1.4.13 or later for both build and installation.
    GNU m4 1.4.13 adds a "--gnu" option that Autom4te uses at runtime if
    it was found to work at build time, so these dependencies ensure
    consistency. Thanks to Martin Casado <email address hidden> for
    reporting the problem.
 -- Bhavani Shankar <email address hidden> Sun, 08 Nov 2009 18:57:54 +0530