Hello, list.

Last emerge-sync brought following change:
net-zope/zopeinterface became net-zope/zope-interface, and, as far as I
can tell, all the ebuild files were updated to use a new package name.

Only problem is that portage doesn't seem to know about this and I
can't seem force it to update it's cache.

I have portage-2.2 with FEATURES="metadata-transfer", the latter
probably being the cause of the problem, but seem to be necessarry for
some overlays I'm using.

Error:
  emerge: there are no ebuilds to satisfy "net-zope/zopeinterface".

What I've tried so far:
  emerge --regen
  egencache --update
  emerge -C <pkg> && emerge -1 <pkg>

What works:
  ebuild /path/to/<pkg>.ebuild merge

Any ideas how to fix emerge in this case?
Thanks.

-- 
Mike Kazantsev // fraggod.net

Attachment: signature.asc
Description: PGP signature

Reply via email to