On Tue, Aug 24, 2010 at 04:08:10PM +0300, Marius Gedminas wrote: ...
Error: There is a version conflict. We already have: setuptools 0.6c12dev-r84273
...
I have a hunch this is due to virtualenv 1.3.3, which is installed into /usr/local/bin/. I've tried upgrading virtualenv to 1.4.5 (the version in Ubuntu 10.04) and the error now is ... Error: There is a version conflict. We already have: zc.buildout 1.5.0
FWIW I had to downgrade virtualenv back to 1.3.3, since 1.4.5 uses Distribute by default, and zc.zope3recipes 0.6.2 doesn't like Distribute: File "/var/lib/buildbot/eggs/zc.zope3recipes-0.6.2-py2.4.egg/zc/zope3recipes/README.txt", line 78, in README.txt Failed example: print system(join('bin', 'buildout')), Expected: Develop: '/sample-buildout/demo1' Develop: '/sample-buildout/demo2' Installing myapp. Generated script '/sample-buildout/parts/myapp/runzope'. Generated script '/sample-buildout/parts/myapp/debugzope'. Got: Develop: '/sample-buildout/demo1' install_dir /sample-buildout/develop-eggs/tmpGFC-Sdbuild Develop: '/sample-buildout/demo2' install_dir /sample-buildout/develop-eggs/tmpIidjYCbuild Installing myapp. Generated script '/sample-buildout/parts/myapp/runzope'. Generated script '/sample-buildout/parts/myapp/debugzope'.
Looks like the outer buildout.cfg doesn't pin zc.buildout so it always gets the latest version, and the inner one doesn't like that at all. I think the fix is to change buildout steps to do this instead: ... $ cd test && ../sandbox/bin/python ../bootstrap.py && bin/buildout
(instead of cd test && ../bin/buildout) This was the right fix. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development