Re: What is keeping new autoconf out of testing?
On Fri, 21 Sep 2001, Andreas Metzler wrote:
> I do not understand this:
> autoconf2.13 2.13-38 (new) (optional) (low)
> Maintainer: Ben Pfaff <pfaffben@msu.edu>
> autoconf2.13 uploaded 15 days ago, out of date by 5 days!
> autoconf2.13/alpha: Unsatisfiable Depends: autoconf (>= 2.50)
> autoconf2.13/arm: Unsatisfiable Depends: autoconf (>= 2.50)
> [etc, for all architectures]
> valid candidate (will be installed unless it's dependent upon other
> buggy pkgs)
>
> autoconf 2.52-2 (currently 2.13-27) (optional) (low)
> Maintainer: Ben Pfaff <pfaffben@msu.edu>
> autoconf uploaded 21 days ago, out of date by 11 days!
> autoconf/alpha: Unsatisfiable Depends: autoconf2.13 (>= 2.13-34)
> autoconf/arm: Unsatisfiable Depends: autoconf2.13 (>= 2.13-34)
> [etc, for all architectures]
> valid candidate (will be installed unless it's dependent upon
> other buggy pkgs)
They depend on eachother. testing scripts don't handle that situation
automatically, IIRC
--
wouter dot verhelst at advalvas dot be
"Human knowledge belongs to the world"
-- From the movie "Antitrust"
rm -rf /bin/laden
Reply to: