Hi Paul,
I experimented a litle bit.
I removed zope.publisher-3.4.1-py2.4.egg/ and zope.traversing-3.4.0-py2.4.egg/
Then I transfered zope.traversing-3.5.0a1.dev_r78730-py2.4.egg/ and
zope.publisher-3.5.0a1.dev_r78838-py2.4.egg/ from another box where the update
of zcontact was
Hi Peter,
I recently switched setup.py and buildout to use the new zope3.4 KGS
and this caused some problems for existing installations of zcontact.
Please submit a bug on launchpad (http://launchpad.net/zcontact) and
I'll see if I can find what is causing the clonflict sometime today.
- Paul
Hello,
how can the error be corrected?
./bin/easy_install -U zcontact
Searching for zcontact
Reading http://pypi.python.org/simple/zcontact/
Reading http://launchpad.net/zcontact
Best match: zcontact 0.1.0a9
Processing zcontact-0.1.0a9-py2.4.egg
zcontact 0.1.0a9 is already the active version in
What's causing the conflict is the fact that
zope.traversing=3.5.0a1.dev-r78730 isn't in the KGS (nor will it get
in there). It might help for Peter to move his zope.app.publisher egg
aside (which is the thing that depends on this release) and try the -U
again.
On Nov 14, 2007, at 3:21
