[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Total confusion with aptitude. Help, please!



Hi, Eduardo!

On Fri, Jun 20, 2008 at 01:40:55PM -0300, Eduardo M KALINOWSKI wrote:
> Alan Mackenzie escreveu:


> >My /etc/apt/source.list now looks like this:
> >#########################################################################
> >#deb ftp://ftp.de.debian.org/debian/ stable main contrib
> >deb ftp://ftp.de.debian.org/debian/ oldstable main contrib

> >#deb-src ftp://ftp.de.debian.org/debian/ stable main contrib
> >deb-src ftp://ftp.de.debian.org/debian/ oldstable main contrib

> >deb http://security.debian.org/ oldstable/updates main contrib
> >#########################################################################

> >When I now start aptitude, I get a plethora of errors with the following
> >form:

> >W: Couldn't stat source package list ftp://ftp.de.debian.org 
> >oldstable/main Packages
> >   (/var/lib/apt/lists/ftp.de.debian.org_debian_dists_oldstable_main_binary-i386_Packages) - stat (2 No such file or
> >   directory)

> >[...]
> >Here, "stable -> etch" and "oldstable -> sarge" seem to be of equal
> >status.  This is making me feel stupid; what stupid mistake have I made
> >in my source.list?

> None, I'd say. Have you run aptitude update?

I have now!

I think I understand the error message now - it parses as "couldn't stat
[the] source package list [for] ftp://ftp.de.debian.org oldstable/main
['s] Packages [, which should be on your Debian system at]
(/var/lib/....._Packages)."

I'd read the message as meaning that /var/lib/apt/.......-i386-Packages
couldn't be found on ftp.de.debian.org - the first part of the message
creates that mental context.

And the last bit of the message (which I didn't quote above) which said
something like "You may want to update the package lists." was not
referring to the contents of the file /etc/apt/source.list (which I
thought at first), is certainly not talking about a package called
"lists", but actually means "You may want to run the `update' command in
aptitude.".

Phew!

After running the update command, I now have a sanely working aptitude
again.  Thanks!

-- 
Alan Mackenzie (Nuremberg, Germany).


Reply to: