I did what Edward and Jason suggested, and now portage looks ready to do its job again. Now, I only have to wait for the 99 packages I need updated to download, compile, and install. A month + with no updates, leaves lots of time at a terminal in my hands. Thanks for all the help everybody!

On 4/25/05, Edward Catmur <[EMAIL PROTECTED]> wrote:
On Mon, 2005-04-25 at 19:21 +0000, Calvin Spealman wrote:
> See, thats part of the problem: there is no package called 'mad'.
> There is gnomad and madplay, but no package just called 'mad'. I had
> the same trouble with portage trying to install motif, instead of
> openmotif, which actually does exist. I don't know why, but portage
> just started trying to update packages that aren't there. Might it
> have to do with any changes in naming of packages, or some of the
> package splits over the last month or two? (My computer has been
> packed up since early March)

Check your overlays. I get this occasionally from bugfix ebuilds that
aren't updated when Portage-tree ebuilds are.

Also clean out your cache:
rm -r /usr/portage/metadata /var/cache/edb/dep

But I'd bet it's your overlays.

--
[email protected] mailing list


Reply via email to