[tahoe-dev] Build problems: using installed packages, and install failure

Jack Lloyd lloyd at randombit.net
Fri Jan 29 18:21:21 UTC 2010

On Fri, Jan 29, 2010 at 10:50:16AM -0700, Zooko Wilcox-O'Hearn wrote:

> This is probably #657 or #717, but just to confirm, if Twisted is  
> properly installed then the following command-line should confirm it:
> python -c 'import pkg_resources;print pkg_resources.require("Twisted")'

Hrm, so something is broken locally then:

$ python -c 'import pkg_resources;print pkg_resources.require("Twisted")' 
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib64/python2.6/site-packages/pkg_resources.py", line 648, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib64/python2.6/site-packages/pkg_resources.py", line 546, in resolve
    raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: Twisted


I'll try to investigate, but won't have time until next week probably.

> This means that the build tool that is running on your system is not  
> the patched version of setuptools which gets bundled with Tahoe-LAFS  
> which has a patch to make it stop doing that (setuptools ticket #54,  
> distribute ticket #46). Instead you are probably using upstream  
> setuptools.
> A work-around would be to somehow force it to use our patched
> version of setuptools.

Yes - upstream setuptools is already required in Gentoo for installing
a number of packages, on my system these include:

  dev-python/setuptools-0.6.10 pulled in by:

(and in Gentoo zope-interface is pulled in by twisted and nevow, so if
Tahoe is using packaged versions, the upstream setuptools will always
be there)


More information about the tahoe-dev mailing list