[Grok-dev] Distribute version pinning

Alex Leach albl500 at york.ac.uk
Fri Jan 18 13:47:02 UTC 2013


I've just tried migrating a grok project to a new Linux box, and the  
bootstrap process fails as it depends on distribute == 0.6.24, which  
bootstrap tries to install into the system site-packages:-

Creating /usr/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info
error: /usr/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info:  
Permission denied
An error occurred when trying to install distribute 0.6.24. Look above  
this message for any errors that were output by easy_install.
   Getting distribution for 'distribute==0.6.24'.
Error: Couldn't install: distribute 0.6.24

I already have distribute version 0.6.34 installed and the  
setuptools-0.6c11-py2.7.egg-info file already exists. For now, I am just  
testing a non-root user installation. I haven't set up a virtualenv  
sandbox on this user account yet, which would no doubt install distribute  
into the virtualenv's site-packages, but I'm curious as to where the  
distribute version is pinned down.

In buildout.cfg, I have added the following:

extends = http://grok.zope.org/releaseinfo/1.5.5/versions.cfg
# newest= false
versions = versions


distribute >= 0.6.34

However, these changes don't remove the required dependency on distribute  
version 0.6.24. There's no mention of distribute in the versions.cfg file  
or the bootstrap script.

Is there any way I can configure bootstrap to use the version of  
distribute I already have installed?


More information about the Grok-dev mailing list