Re: upgrading just one "stable" package to "testing" version
Your sources.list must not be correct then, or something is fubared
rm -rf /var/lib/apt/lists/*
then make SURE /etc/apt/sources.list is correct.
Then update the package list, and try and get dpkg first, then apt.
That should work. Let us all know the result.
----- Original Message -----
From: "Toby Thain" <email@example.com>
To: "Jason Lim" <firstname.lastname@example.org>
Sent: Tuesday, March 19, 2002 7:59 PM
Subject: Re: upgrading just one "stable" package to "testing" version
> On Tuesday, March 19, 2002, at 05:17 AM, Jason Lim wrote:
> >> On Mon, Mar 18, 2002 at 21:11:20 +1100, Toby Thain wrote:
> >>> spaz:~# apt-get update
> >>> spaz:~# apt-get install apt
> >>> Reading Package Lists... Done
> >>> Building Dependency Tree... Done
> >>> Sorry, apt is already the newest version
> >>> 0 packages upgraded, 0 newly installed, 0 to remove and 5 not
> > upgraded.
> >> That's strange. Stable has apt 0.3.19; testing has apt 0.5.4. This
> > should
> >> have worked. Perhaps apt is among the "5 not upgrade" packages, for
> >> some
> >> reason? You could work around this by installing the new apt (and its
> >> dependencies) through "dpkg".
> > There is a simple way... do apt-get -v
> > What is the output? What version does it report?
> spaz:~# apt-get -v
> apt 0.3.19 for i386 compiled on May 12 2000 21:17:27
> > Then we'll know all.
> > --
> > To UNSUBSCRIBE, email to email@example.com
> > with a subject of "unsubscribe". Trouble? Contact
> > firstname.lastname@example.org
> To UNSUBSCRIBE, email to email@example.com
> with a subject of "unsubscribe". Trouble? Contact