-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Unfortunately there was a problem when parsing onion services on Python2, which is fixed by txtorcon 18.0.1
You can download the release from PyPI or GitHub (or of course "pip install txtorcon"):
https://pypi.python.org/pypi/txtorcon/18.0.1 https://github.com/meejah/txtorcon/releases/tag/v18.0.1
Releases are also available from the hidden service:
http://timaq4ygg2iegci7.onion/txtorcon-18.0.1.tar.gz http://timaq4ygg2iegci7.onion/txtorcon-18.0.1.tar.gz.asc
Or via a "version 3" service:
http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtorc... http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtorc...
You can verify the sha256sum of both by running the following 4 lines in a shell wherever you have the files downloaded:
cat <<EOF | sha256sum --check 4c158ee5cfc294a0e20c00dde2a146f04ebe6c6d1c3d7c164c0bd1c56e3d1bc6 dist/txtorcon-18.0.1.tar.gz 2c3f7c768bebf081d0742cdce023b4496bf3b44c423ed7f06bd8d6254e07273e dist/txtorcon-18.0.1-py2.py3-none-any.whl EOF
thanks, meejah
Hi meejah,
On 30/06/18 06:11, meejah wrote:
Unfortunately there was a problem when parsing onion services on Python2, which is fixed by txtorcon 18.0.1
Is it possible for you to make a GitHub "release" for 18.0.1? For the Debian packaging I fetch the signatures from here and verify them, which doesn't work if you've only tagged the release.
Thanks, Iain.
What's a github release? I think you mean a commit which is tagged and I'm pretty sure meejah tags release commits.
On Sun, Jul 01, 2018 at 04:09:26PM +0100, Iain Learmonth wrote:
Hi meejah,
On 30/06/18 06:11, meejah wrote:
Unfortunately there was a problem when parsing onion services on Python2, which is fixed by txtorcon 18.0.1
Is it possible for you to make a GitHub "release" for 18.0.1? For the Debian packaging I fetch the signatures from here and verify them, which doesn't work if you've only tagged the release.
Thanks, Iain.
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hi,
On 01/07/18 16:30, dawuud wrote:
What's a github release? I think you mean a commit which is tagged and I'm pretty sure meejah tags release commits.
I mean what GitHub calls a "release" which is different to a tag. It allows me to base the Debian packaging on a signed tarball from meejah as opposed to me signing a tarball to say "I checked this matches up with meejah's signed commit, trust me".
See: https://github.com/meejah/txtorcon/releases
Thanks, Iain.
Iain Learmonth irl@torproject.org writes:
Is it possible for you to make a GitHub "release" for 18.0.1? For the Debian packaging I fetch the signatures from here and verify them, which doesn't work if you've only tagged the release.
Ah, sorry yes I missed this step. The GitHub release is updated.
thanks, meejah
Hi meejah,
On 02/07/18 06:38, meejah wrote:
Ah, sorry yes I missed this step. The GitHub release is updated.
Thanks!
I've just looked at updating the Debian packaging with this but unfortunately I'm blocked by Debian#902766 which appears to be a Python 3.7 issue (async is now a reserved keyword).
I will look again once this is resolved.
Thanks, Iain.
Iain Learmonth irl@torproject.org writes:
I will look again once this is resolved.
I believe 18.0.2 fixes this (also reported by Brian Warner for magic-wormhole). Sorry about that!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Python3.4 doesn't support async-def or await, but the guards being used only accounted for Python2 -- this is fixed by txtorcon 18.0.2
You can download the release from PyPI or GitHub (or of course "pip install txtorcon"):
https://pypi.python.org/pypi/txtorcon/18.0.2 https://github.com/meejah/txtorcon/releases/tag/v18.0.2
Releases are also available from the hidden service:
http://timaq4ygg2iegci7.onion/txtorcon-18.0.2.tar.gz http://timaq4ygg2iegci7.onion/txtorcon-18.0.2.tar.gz.asc
Or via a "version 3" service:
http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtorc... http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtorc...
You can verify the sha256sum of both by running the following 4 lines in a shell wherever you have the files downloaded:
cat <<EOF | sha256sum --check ce50fdd00abb8b490b72809a2c664684f67f3c9467f392642d36f58309395a87 dist/txtorcon-18.0.2.tar.gz cb1a681e424744c50eefb02b7b777cce80a505da1e89ee4886fe62013afaf858 dist/txtorcon-18.0.2-py2.py3-none-any.whl EOF
thanks, meejah
-
dawuud -
Iain Learmonth -
meejah