Re: upgrading in sid
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/31/07 11:42, Daniel Burrows wrote:
> On Sun, Dec 30, 2007 at 08:01:32PM -0500, charlie derr <cderr@simons-rock.edu> was heard to say:
>>>> The following packages will be upgraded:
>>>> gnome-session libgnome2-common libgnomevfs2-common shared-mime-info
>>>> 4 packages upgraded, 0 newly installed, 0 to remove and 795 not upgraded.
>>>> Need to get 0B/2706kB of archives. After unpacking 1461kB will be used.
>>>> Do you want to continue? [Y/n/?] y
>>>> Writing extended state information... Error!
>>>> E: I wasn't able to locate file for the desktop-base package. This might mean you need to manually fix this package.
>>>> E: Couldn't lock list directory..are you root?
>>> You used apt-get to break the desktop-base package behind aptitude's
>>> back and that seems to have confused aptitude. I would hope that this
>>> problem goes away once you have fixed the desktop-base package.
>>>
>> Thanks again for letting me know that it was my mixing apt-get and aptitude that probably screwed me up.
>
> I don't know any reason that mixing apt-get and aptitude should cause
> problems, particularly this problem.
Don't apt-{get,cache} and aptitude track dependencies in different
manners, using different data stores?
> This is usually a symptom of your
> package lists being out of sync in a weird way: it means that apt
> thought it could download this package, but when it went to actually
> download it no source was providing it. I expect you would get the same
> error with apt-get as with aptitude.
- --
Ron Johnson, Jr.
Jefferson LA USA
"Your mistletoe is no match for my TOW missile." Santa-bot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHeS5KS9HxQb37XmcRAuc1AKDANaBqJ+WliveeawOD38LyLTjKfgCeIN7Y
4C39SnLc8kuETyvsdk9euFE=
=TXyq
-----END PGP SIGNATURE-----
Reply to: