I just did an emerge sync, and the best I can tell, there is no sys-libs/libcap-1.10-r5 (it's not in /usr/portage/sys-libs/libcap/ and not in the manifest), but there is this error on emerge -uDva world: ------------------------------------------------- Quote: These are the packages that I would merge, in order: Calculating world dependencies /!!! aux_get(): ebuild path for 'sys-libs/libcap-1.10-r5' not specified: !!! None emerge: create(): aux_get() error on sys-libs/libcap-1.10-r5; aborting... ----------------------------------------------------- What I did to get a good emerge is this: 1. put =sys-libs/libcap-1.10-r5 in /etc/portage/package.mask 2. touch /usr/portage/sys-libs/libcap/libcap-1.10-r5.ebuild 3. run the emerge (emerge -uDva world) This will create the ebuild file and mask it ... making (at least) my emerge work. Reproducible: Always Steps to Reproduce:
There's a stale metadata cache file which has no ebuild associated with it. I'm currently trying to reach infra to remove the file.
Infra comes through in its chariot blazing to fix another issue. -Jeffrey
This isn't fixed here, same problem, and I still need to touch the ebuild to do an emerge -UvDp world. BTW, its been 2-3 days now and I just synced, so its not because I didn't sync recently. Just resynced on hawk.gentoo.org.
Seems to still be happening.
bah. closing this, the mirrors are fine... something local is occuring with the users system which needs to be sorted out.
Just for the record ... this is still happening on my machine. I synced twice, from two different gentoo servers. I don't know what the cause is, but it is not fixed ... I am using the ~x86 arch
Well, err no.. its not that there is a problem on the mirrors or on the local machines.. its the fact that emerge -U is causing it..
My problem has been resolved ... somehow, libcap-1.10-r5 was released as ~x86 ... and then removed. While it was released, it was installed by an emerge. It was then removed totally from portage, not just masked ... thus a emerge -U tried failed because the ebuild no longer exists in portage. The fix was to downgrade to libcap-1.10-r4 So the real question is, why was libcap-1.10-r5 removed and not just masked after being released in portage...
