Re: what happened to libapt-pkg-libc6.2-3-2-3.2?
On Wed, May 22, 2002 at 05:38:44PM +0200, Tomas Pospisek's Mailing Lists <email@example.com> was heard to say:
> tpo2:/home/tpo# apt-get install hello-debhelper
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Sorry, hello-debhelper is already the newest version.
> You might want to run `apt-get -f install' to correct these:
> Sorry, but the following packages have unmet dependencies:
> deity: Depends: libapt-pkg-libc6.2-3-2-3.2
> python-apt: Depends: libapt-pkg-libc6.2-3-2-3.2
> synaptic: Depends: libapt-pkg-libc6.2-3-2-3.2
> E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
> specify a solution).
> Has it been pulled from testing/unstable? And why haven't
> deity, python-apt and synaptic been pulled from testing at the same time?
> Testing is broken this way.
Are you sure? libapt-pkg is always provided by apt, and the version
of apt in testing provides that particular libapt-pkg.
I got a bug report against aptitude for this problem some time back, and
it turned out the user was running an unreleased CVS snapshot of apt.
Could that be happening here?
/-------------------- Daniel Burrows <firstname.lastname@example.org> -------------------\
| Wisdom is one of the few things |
| that looks bigger the farther away it is. |
| -- Terry Pratchett |
\----------------- The Turtle Moves! -- http://www.lspace.org ----------------/
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org