Apparently we don't fully understand the combination of versions that trigger this problem. On my debian/sid system, I see timeout/reactor-unclean failures of tahoe's test_system (and of several foolscap unit tests). This system has:
* python-twisted-8.1.0-1
* python-openssl-0.7-1
* libssl0.9.8g-10.1
However, an Ubuntu/Hardy system we just set up does *not* fail tests, when using what we believe to be twisted-8.1.0, pyopenssl-0.7, and libssl0.9.8g-4ubuntusomething.
If this really only causes failures on sid (but hardy is ok), we're willing to push it out a release.
We still want to get it fixed, but it will probably require the pyopenssl maintainers to
fix [http://twistedmatrix.com/trac/ticket/3218 twisted#3218].
sid users are still advised to hold python-openssl at 0.6-5 .
Apparently we don't fully understand the combination of versions that trigger this problem. On my debian/sid system, I see timeout/ reactor- unclean failures of tahoe's test_system (and of several foolscap unit tests). This system has: twisted- 8.1.0-1 openssl- 0.7-1
* python-
* python-
* libssl0.9.8g-10.1
However, an Ubuntu/Hardy system we just set up does *not* fail tests, when using what we believe to be twisted-8.1.0, pyopenssl-0.7, and libssl0. 9.8g-4ubuntusom ething.
If this really only causes failures on sid (but hardy is ok), we're willing to push it out a release. twistedmatrix. com/trac/ ticket/ 3218 twisted#3218].
We still want to get it fixed, but it will probably require the pyopenssl maintainers to
fix [http://
sid users are still advised to hold python-openssl at 0.6-5 .