[tahoe-lafs-trac-stream] [tahoe-lafs] #1383: foolscap 0.6.1 has no such extra feature 'secure_connections'

[tahoe-lafs]

#1383: foolscap 0.6.1 has no such extra feature  'secure_connections'
---------------------------+-------------------------------------------
     Reporter:  zooko      |      Owner:  charlesnw
         Type:  defect     |     Status:  reopened
     Priority:  major      |  Milestone:  1.9.0
    Component:  packaging  |    Version:  1.8.2
   Resolution:             |   Keywords:  setuptools foolscap pyOpenSSL
Launchpad Bug:  782414     |
---------------------------+-------------------------------------------

Comment (by warner):

 After discussing this on IRC, our plan is to make tahoe depend upon
 pyopenssl. It's not the cleanest solution: ideally Foolscap could change
 its internals to not depend upon pyopenssl some day (maybe using libgnutls
 instead), and then Tahoe would have a spurious dependency, but I don't
 plan to change Foolscap in this way any time soon.

 The other options we discussed:

 * change Foolscap to unconditionally require openssl: I still remember the
 ipython folks wanting to avoid this dependency
 * change Foolscap to unconditionally require setuptools (which would have
 caused that ubuntu build to fail rather than producing a package that
 didn't have a `[secure_connections]` dependency upon openssl).

 I think the immediate problem here was the incorrect ubuntu build (which
 didn't mark setuptools as a source dependency, thus the foolscap package
 was built in an environment without setuptools, thus foolscap's setup.py
 didn't include the `secure_connections` marker, thus tahoe was unsatisfied
 with the foolscap .deb that was already installed). And I think that
 problem has been fixed on the Ubuntu side.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1383#comment:35>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage