The same problem was causing build failures via python-openssl, since 0.6 is not being distributed anymore (or it's been removed from certain sf.net mirrors, or sf.net is having connectivity problems). In [2931] I added a workaround: just add --site-dirs=/var/lib/python-support/python2.5/ to the 'setup.py develop' command line. This should fix the problem on debian-like systems and not cause any ill effects on other platforms.
I expect that this ought to cause our buildslaves to stop trying to build nevow and openssl when they are already installed.
The same problem was causing build failures via python-openssl, since 0.6 is not being distributed anymore (or it's been removed from certain sf.net mirrors, or sf.net is having connectivity problems). In [2931] I added a workaround: just add --site- dirs=/var/ lib/python- support/ python2. 5/ to the 'setup.py develop' command line. This should fix the problem on debian-like systems and not cause any ill effects on other platforms.
I expect that this ought to cause our buildslaves to stop trying to build nevow and openssl when they are already installed.