[tahoe-lafs-trac-stream] [tahoe-lafs] #1383: foolscap 0.6.1 has no such extra feature 'secure_connections'
tahoe-lafs
trac at tahoe-lafs.org
Tue Apr 19 11:48:06 PDT 2011
#1383: foolscap 0.6.1 has no such extra feature 'secure_connections'
---------------------------+-------------------------------------------
Reporter: zooko | Owner: charlesnw
Type: defect | Status: new
Priority: major | Milestone: 1.9.0
Component: packaging | Version: 1.8.2
Resolution: | Keywords: setuptools foolscap pyOpenSSL
Launchpad Bug: |
---------------------------+-------------------------------------------
Comment (by zooko):
Interesting. Okay, so it *does* seem to be a problem with the packaging of
foolscap in Ubuntu 11.04. Please confirm this by finding the metadata (you
earlier found it in {{{/usr/lib/python2.7/dist-packages/foolscap-0.6.1
.egg-info}}}) and attaching it to this ticket. It might be a file or it
might be a directory -- in the latter case please archive the whole thing
(it should only be a few KB) and attach it. Thanks!
I think the way forward is for Tahoe-LAFS to stop asking foolscap for
{{{secure_connections}}} and for foolscap to start making secure
connections available to clients even if they don't ask for them by name.
I've submitted a patch for foolscap that would do this:
http://foolscap.lothar.com/trac/ticket/174 . Here is a patch to Tahoe-LAFS
that you can try out, Charles:
{{{
--- old-ticket1385/src/allmydata/_auto_deps.py 2011-04-19
12:47:39.000000000 -0600
+++ new-ticket1385/src/allmydata/_auto_deps.py 2011-04-19
12:47:39.000000000 -0600
@@ -23,7 +23,7 @@
# of size N.
# foolscap < 0.6 is incompatible with Twisted 10.2.0.
# foolscap 0.6.1 quiets a DeprecationWarning.
- "foolscap[secure_connections] >= 0.6.1",
+ "foolscap >= 0.6.1",
"Nevow >= 0.6.0",
}}}
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1383#comment:24>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list