From: Encolpe D. <enc...@fr...> - 2014-08-23 14:43:58
|
Le 23/08/2014 08:13, dieter a écrit : > David Siedband <tec...@oc...> writes: > >> Heres the trace from running buildout: >> [ ] >> Getting distribution for 'zope.contenttype==3.4.3'. >> Got zope.contenttype 3.4.3. >> While: >> Installing. >> Loading extensions. >> Getting section zeoclient1. >> Initializing section zeoclient1. >> Installing recipe plone.recipe.zope2instance. >> >> An internal error occured due to a bug in either zc.buildout or in a >> recipe being used: >> Traceback (most recent call last): >> ... >> raise VersionConflict(dist,req) # XXX add more info >> VersionConflict: (distribute 0.6.49 (/home/zope/buildout/eggs/distribute-0.6.49-py2.7.egg), Requirement.parse('distribute==0.6.16')) > I interprete this as follows: > > "plone.recipe.zope2instance" (or something > specified globally to "buildout") has a dependency on > "distribute==0.6.16" but your setup has "distribute==0.6.49"). > > Check whether your "buildout" configuration pins "distribute" to > "0.6.16" -- in this case, change it to the installed version. > Otherwise, check whether "plone.recipe.zope2instance" is responsible > for the pin -- either upgrade this recipe (in a way that is like > the installed "distribute" version) or downgrade the "distribute" > in your Python installtion to "0.6.16". First, you should use 'bin/buildout annotate' to check where the version are pinned. After, if you are using a virtualenv running 'env/bin/python boostrap.py' can resolve the problem. Else you can delete '/home/zope/buildout/eggs/distribute-0.6.49-py2.7.egg', cross your finger and run 'bin/buildout'. Regards -- Encolpe DEGOUTE http://encolpe.degoute.free.fr/ Logiciels libres, hockey sur glace et autres activités cérébrales |