| 1 |
Mike Kazantsev wrote: |
| 2 |
> On Sat, 10 Oct 2009 09:10:24 +0200 |
| 3 |
> Justin <justin@×××××××××.net> wrote: |
| 4 |
> |
| 5 |
>> Mike Kazantsev wrote: |
| 6 |
>>> I have portage-2.2 with FEATURES="metadata-transfer", the latter |
| 7 |
>>> probably being the cause of the problem, but seem to be necessarry for |
| 8 |
>>> some overlays I'm using. |
| 9 |
>>> |
| 10 |
>> Hi |
| 11 |
>> that's a problem of the ebuilds in the overlays. Inthe ebuild there is a |
| 12 |
>> hardcoded string for the dependency. So in case of a renaming you have |
| 13 |
>> to change the ebuilds in the overlays manually. |
| 14 |
> |
| 15 |
> No, the ebuilds in question are (among others) dev-python/nevow and |
| 16 |
> dev-python/ipython, from main portage tree. |
| 17 |
> |
| 18 |
> Furthermore, as I've stated in the original post, the dependencies |
| 19 |
> there are _correct_, it's just that emerge doesn't even trying to check |
| 20 |
> them, while direct "ebuild X merge" command works just fine. |
| 21 |
> |
| 22 |
It works here, perhaps try to sync again. The metadacache will be synced |
| 23 |
with the ebuilds. |
Archives