Re: [gentoo-user] How to update dependency cache for emerge?
Mike Kazantsev wrote: 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. Hi that's a problem of the ebuilds in the overlays. Inthe ebuild there is a hardcoded string for the dependency. So in case of a renaming you have to change the ebuilds in the overlays manually. jusitn signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] How to update dependency cache for emerge?
On Sat, 10 Oct 2009 09:10:24 +0200 Justin jus...@j-schmitz.net wrote: Mike Kazantsev wrote: 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. Hi that's a problem of the ebuilds in the overlays. Inthe ebuild there is a hardcoded string for the dependency. So in case of a renaming you have to change the ebuilds in the overlays manually. No, the ebuilds in question are (among others) dev-python/nevow and dev-python/ipython, from main portage tree. Furthermore, as I've stated in the original post, the dependencies there are _correct_, it's just that emerge doesn't even trying to check them, while direct ebuild X merge command works just fine. -- Mike Kazantsev // fraggod.net signature.asc Description: PGP signature
Re: [gentoo-user] How to update dependency cache for emerge?
Mike Kazantsev wrote: On Sat, 10 Oct 2009 09:10:24 +0200 Justin jus...@j-schmitz.net wrote: Mike Kazantsev wrote: 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. Hi that's a problem of the ebuilds in the overlays. Inthe ebuild there is a hardcoded string for the dependency. So in case of a renaming you have to change the ebuilds in the overlays manually. No, the ebuilds in question are (among others) dev-python/nevow and dev-python/ipython, from main portage tree. Furthermore, as I've stated in the original post, the dependencies there are _correct_, it's just that emerge doesn't even trying to check them, while direct ebuild X merge command works just fine. It works here, perhaps try to sync again. The metadacache will be synced with the ebuilds. signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] How to update dependency cache for emerge?
On Sat, 10 Oct 2009 10:26:43 +0200 Justin jus...@j-schmitz.net wrote: It works here, perhaps try to sync again. The metadacache will be synced with the ebuilds. Erm, I think whole point of metadata-transfer is to get the raw metadata and not to use pre-generated cache, am I wrong here? Furthermore, I don't sync the machine (actually several machines) in question via rsync, but use emerge --sync ability to pull PORTDIR from a git repository, which doesn't contain any caches, since machines that pull from there can have different overlays plugged in. And so original post starts from here - I want to generate the cache, not just transfer the one from vanilla portage. -- Mike Kazantsev // fraggod.net signature.asc Description: PGP signature
Re: [gentoo-user] How to update dependency cache for emerge?
Mike Kazantsev wrote: On Sat, 10 Oct 2009 10:26:43 +0200 Justin jus...@j-schmitz.net wrote: It works here, perhaps try to sync again. The metadacache will be synced with the ebuilds. Erm, I think whole point of metadata-transfer is to get the raw metadata and not to use pre-generated cache, am I wrong here? Furthermore, I don't sync the machine (actually several machines) in question via rsync, but use emerge --sync ability to pull PORTDIR from a git repository, which doesn't contain any caches, since machines that pull from there can have different overlays plugged in. And so original post starts from here - I want to generate the cache, not just transfer the one from vanilla portage. Then you are right with egencache --repo=gentoo --update. If there is still a problem, take a look into the ebuilds and the cache if the dependencies are named correctly. signature.asc Description: OpenPGP digital signature
[gentoo-user] How to update dependency cache for emerge?
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 signature.asc Description: PGP signature