I am considering dropping support for Twisted 12, 13 and 14 in the next txtorcon release. Also, TLS support (i.e. pyOpenSSL) will become mandatory as well (that is, the dependency will be on twisted[tls]). Twisted 12 is only there because of Debian wheezy. Twisted 13 is for wheezy-backports and 14 is for jessie ("stable"). jessie-backports has 16.2.0 and stretch has 16.6.0 Hence I do not believe upgrading this dependency will be a problem for Debian packaging. I do not know the implications for other distributions. Feedback requested if this will negatively affect you! -- meejah
meejah transcribed 1.0K bytes:
I am considering dropping support for Twisted 12, 13 and 14 in the next txtorcon release. Also, TLS support (i.e. pyOpenSSL) will become mandatory as well (that is, the dependency will be on twisted[tls]).
Twisted 12 is only there because of Debian wheezy. Twisted 13 is for wheezy-backports and 14 is for jessie ("stable"). jessie-backports has 16.2.0 and stretch has 16.6.0
Hence I do not believe upgrading this dependency will be a problem for Debian packaging. I do not know the implications for other distributions.
Feedback requested if this will negatively affect you!
For whatever it's worth, all of Tor's infrastructure runs on Debian stable, and I'm not sure if weasel would make exceptions to enable backports. Best, -- ♥Ⓐ isis agora lovecruft _________________________________________________________ OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35 Current Keys: https://fyb.patternsinthevoid.net/isis.txt
isis agora lovecruft <isis@torproject.org> writes:
meejah transcribed 1.0K bytes:
Feedback requested if this will negatively affect you!
For whatever it's worth, all of Tor's infrastructure runs on Debian stable, and I'm not sure if weasel would make exceptions to enable backports.
Makes sense. So this would mean that no tor-infrastucuture stuff could depend on lastest txtorcon until after Stretch is released (but that's next month, right?) Does this affect OONI? They definitely depend on Debian-packaged txtorcon...but they only depend on txtorcon 0.7.0+ according to github (paging hellais!) What will be added next release is: dropping txsocksx for a custom SOCKS implementation (gaining RESOLVE and RESOLVE_PTR via Tor support) and [actualy, full] Python3 support (txsocksx will not support Python3)...so I don't think anyone with existing, deployed code should *need* to upgrade. If there was a security fix or bug-fix required for an older release, I would have no problem releasing e.g. a txtorcon 0.14.x or whatever was needed to support Debian stable or old-stable. -- meejah
participants (2)
-
isis agora lovecruft -
meejah