apparent serious integrity problem in build system - setuptools bug?

jg71 jg71 at
Fri Mar 21 17:42:01 UTC 2014

* Greg Troxel <gdt at> wrote:

> Zooko Wilcox-OHearn <zooko at> writes:
> > To change it so that it *doesn't* automatically download packages
> > #over the Net is ticket 1220.
> OK - this is the basic bug.  By default, it should fail with an error,
> and do this autofetching if given the --autofetch or whatever option.


> I have now figured that out.  py-OpenSSL was updated to 0.14 in pkgsrc,
> but it was not marked as depending on six and cryptography.  When
> *building* py-OpenSSL, these weren't used, so one got a package. 
> But when using it (via "import OpenSSL"), or trying to test it (via
> setuptools test), it failed.

Same here, "tahoe -V" with pyOpenSSL 0.14 installed fails on a
Slackware64 14.1 system, first complaining about six, and after
installing six about the dep on cryptography>=0.2.1

Currently cryptography is not listed at - I plan to
submit a BuildScript this weekend, unless a lurker beats me to it
(which would be fine with me :-)

Best case would be (and let's be optimistic here) that tahoe just
works with pyOpenSSL 0.14, including the new deps on six and

Anyway, I'll get back to you after having run some tests.

Feel the magic of Tahoe-LAFS.

More information about the tahoe-dev mailing list