On Wed, 18 Jul 2012 23:23:41 +0200, "Len Conrad " <[email protected]> wrote: > Learner alert! > > in my virtualenv, my buildout.cfg > > [buildout] > extends = > #http://dist.plone.org/release/4.2/versions.cfg > #parts = instance
Are these two really commented out in the buildout? > extends = > http://download.zope.org/zopetoolkit/index/1.0.7/ztk-versions.cfg And this one you should not need to add it yourself, as the one above already does it for you. And then... [... snip ...] > [versions] > # Zope2-specific > Zope2 = 2.13.15 > AccessControl = 2.13.7 > Acquisition = 2.13.8 > DateTime = 2.12.6 [....] all this version pinnings become unnecessary. > but > > python bootstrap.py --distribute > > gives: > > Traceback (most recent call last): > > File "bootstrap.py", line 124, in <module> > ws.require('zc.buildout' + VERSION) > > File "build/bdist.freebsd-9.0-RELEASE-i386/egg/pkg_resources.py", line 690, > in require > > File "build/bdist.freebsd-9.0-RELEASE-i386/egg/pkg_resources.py", line 592, > in resolve > > pkg_resources.VersionConflict: (zc.buildout 1.5.2 > (/usr/local/lib/python2.7/site-packages/zc.buildout-1.5.2-py2.7.egg), > Requirement.parse('zc.buildout==1.4.4')) In your [versions] section add a pin for the buildout version you already have (or any other). Also, if possible, don't install any libraries into the Python installation you are using unless they will be used by all of your buildouts/virtualenvs using that Python interpreter. Servilio _______________________________________________ Setup mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-setup
