Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch

2018-07-02 Thread Peter Palfrader
On Tue, 03 Jul 2018, Peter Palfrader wrote: > On Sun, 01 Jul 2018, Iain Learmonth wrote: > > > Hi, > > > > On 30/06/18 15:42, nusenu wrote: > > > but maybe someone else would be willing to invoke a > > > "ln" commands everytime a new new alpha repo is born. > > > > > > tor-alpha-jessie -> tor-e

Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch

2018-07-02 Thread Peter Palfrader
On Tue, 03 Jul 2018, teor wrote: > Maybe there is no good solution to this problem. > What’s the least worse solution? Stop shipping alpha versions where people can find them easily? -- | .''`. ** Debian ** Peter Palfrader | : :' : The univer

Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch

2018-07-02 Thread Peter Palfrader
On Sun, 01 Jul 2018, Iain Learmonth wrote: > Hi, > > On 30/06/18 15:42, nusenu wrote: > > but maybe someone else would be willing to invoke a > > "ln" commands everytime a new new alpha repo is born. > > > > tor-alpha-jessie -> tor-experimental-0.3.4.x-jessie > > As an alternative strategy, sym

Re: [tor-dev] the consequences of deprecating debian alpha repos with every new major branch

2018-07-02 Thread teor
> On 2 Jul 2018, at 00:57, Iain Learmonth wrote: > > Signed PGP part > Hi, > > On 30/06/18 15:42, nusenu wrote: >> but maybe someone else would be willing to invoke a >> "ln" commands everytime a new new alpha repo is born. >> >> tor-alpha-jessie -> tor-experimental-0.3.4.x-jessie But then op

Re: [tor-dev] txtorcon 18.0.1

2018-07-02 Thread meejah
Iain Learmonth 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! -- meejah ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproje

Re: [tor-dev] txtorcon 18.0.1

2018-07-02 Thread meejah
-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.o

Re: [tor-dev] documenting reload vs. restart requirements per torrc option

2018-07-02 Thread nusenu
teor: > >> On 3 Jul 2018, at 05:52, nusenu wrote: >> >> Hi, >> >> I like unbound's documentation with this regards, for example they say >> in their man page: >> >>> The interfaces are not changed on a reload (kill -HUP) >>> but only on restart. >> >> Could we add such information

Re: [tor-dev] documenting reload vs. restart requirements per torrc option

2018-07-02 Thread teor
> On 3 Jul 2018, at 05:52, nusenu wrote: > > Hi, > > I like unbound's documentation with this regards, for example they say > in their man page: > >> The interfaces are not changed on a reload (kill -HUP) >> but only on restart. > > Could we add such information to every torrc o

[tor-dev] documenting reload vs. restart requirements per torrc option

2018-07-02 Thread nusenu
Hi, I like unbound's documentation with this regards, for example they say in their man page: > The interfaces are not changed on a reload (kill -HUP) > but only on restart. Could we add such information to every torrc option in the manual? background: In relayor I need to re

Re: [tor-dev] txtorcon 18.0.1

2018-07-02 Thread Iain Learmonth
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 keywor