[Grok-dev] grokproject broken

modiadi adi at modiadi.com
Thu Jun 18 09:38:07 EDT 2009


Is there any update on this issue, because I am still getting errors  
like :

Error: There is a version conflict.
We already have: zope.lifecycleevent 3.4.0
but zope.container 3.8.2 requires 'zope.lifecycleevent>=3.5.2'.

And I am using grok-1.0a4.cfg .

I am not sure what to do.

PS: I just copied an existing project from one computer (where it  
works) to another. After running buildout I get this error. All  
directory structures are the same except missing ~/.buildout

Thank you.

On May 19, 2009, at 10:32 AM, Uli Fouquet wrote:

> Hi there,
> Michael Haubenwallner wrote:
>> same reason as yesterday (grok trunk broken)
>> fresh 'easy_install grokproject' and creating a new project gets me:
>> ...
>> Installing eggbasket.
>> While:
>>  Installing eggbasket.
>> Error: There is a version conflict.
>> We already have: zope.lifecycleevent 3.4.0
>> but zope.container 3.8.2 requires 'zope.lifecycleevent>=3.5.2'.
>> Reason is, that zope.container is not pinned in grokcore.view
> Uh, so existing installations of grokproject are broken as well, as I
> suspected yesterday. :-/
>> I think we need a new grokcore.view release and as gc.v version is
>> pinned to 1.5 also need a new grokproject release. We could as well
>> create a grok1.0a4 at the same time.
>> How can we organize to get that done? I'll do the grokproject part.
> If someone releases a new grokcore.view, then we could release a new
> grok egg. I think the current grokproject (and also older versions)
> afterwards should run smoothly again, shouldn't they?
> However, people that want to install a project with older Grok (up to
> current 1.0a3) would still fail. They had (after buildout aborting the
> install throwing nasty messages) have to pin down zope.container
> manually.
> So for all, that run into the zope.container/zope.lifecycleevent  
> version
> conflict with grokproject/grok: Add::
>  zope.container = 3.8.1
> to your versions.cfg or to the [versions] section in your buildout.cfg
> and rerun buildout afterwards.
> We could easily fix that problem for fresh installs by adding
> zope.container to the already existing KnownGoodSet lists (aka
> grok-n.nn.cfgs) on grok.zope.org/releaseinfo/. Then also installs of
> older grok versions with grokproject would work again. I expect a good
> load of opposition to this proposal but am willing to learn from your
> arguments.
> Best regards,
> -- 
> Uli
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list