Re: what happened to libapt-pkg-libc6.2-3-2-3.2?
On Wed, 22 May 2002, Matt Zimmerman wrote:
> On Wed, May 22, 2002 at 05:38:44PM +0200, Tomas Pospisek's Mailing Lists wrote:
>
> > 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.
>
> apt is telling you that those dependencies are unmet on your system, not in
> the package database. Try 'apt-get -f install' as it suggests, and check
> your installed version of apt. woody contains 0.5.4.
To expand on what Matt said:
When you tell apt to install a package, it attempts to only do what you have
requested. It also does a sanity check on the packages currently installed.
At some point, you used apt to install deity, python-apt, and synaptic. Then,
what appears to have happened, is that you used dpkg directly to install some
special version of apt. dpkg doesn't take care of keeping reverse
dependencies in check, in all cases.
So, when you next asked apt to do something, it complained about your broken
system.
Simply running apt-get -f install would allow it to fix it. Unless of course
the special apt you had installed was newer than the one available from
debian.
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: