Mike Kazantsev wrote:
> On Sat, 10 Oct 2009 10:26:43 +0200
> Justin 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
On Sat, 10 Oct 2009 10:26:43 +0200
Justin 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 sy
Mike Kazantsev wrote:
> On Sat, 10 Oct 2009 09:10:24 +0200
> Justin 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
On Sat, 10 Oct 2009 09:10:24 +0200
Justin 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
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 depend
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 i
6 matches
Mail list logo
