Bill Allombert:
> On Thu, Aug 09, 2018 at 07:55:00AM +, Niels Thykier wrote:
>> [...]
>>
>> Excellent, I am looking forward to it. :) Do you have an estimate of
>> when 1.67 will be in unstable?
>
> Now. Sorry I prepared the package one month ago, tested it (which is
> slow) and then forgot to
On Thu, Aug 09, 2018 at 07:55:00AM +, Niels Thykier wrote:
> On Sun, 20 May 2018 15:50:16 +0200 Bill Allombert
> wrote:
> > [...]
> >
> > Thanks! (and apologies to Tim to have missed the opportunuity to check Tim
> > original popularity-contest.gpg report).
> >
> > I have received it just o
On Sun, 20 May 2018 15:50:16 +0200 Bill Allombert
wrote:
> [...]
>
> Thanks! (and apologies to Tim to have missed the opportunuity to check Tim
> original popularity-contest.gpg report).
>
> I have received it just one (via http) on Sun May 20 08:02:01 UTC 2018
> (however popcon cron.daily has
On Sun, May 20, 2018 at 08:06:00AM +, Niels Thykier wrote:
> On Wed, 7 Sep 2016 16:51:32 +0200 Bill Allombert
> wrote:
> > On Sat, Aug 27, 2016 at 12:03:52AM +0100, Tim Retout wrote:
> > > A few more things before you consider shipping this (sorry for not
> > > thinking of them before my previ
On Wed, 7 Sep 2016 16:51:32 +0200 Bill Allombert
wrote:
> On Sat, Aug 27, 2016 at 12:03:52AM +0100, Tim Retout wrote:
> > A few more things before you consider shipping this (sorry for not
> > thinking of them before my previous email):
> >
> > - torify is just a wrapper around torsocks. The tor
On Sat, Aug 27, 2016 at 12:03:52AM +0100, Tim Retout wrote:
> A few more things before you consider shipping this (sorry for not
> thinking of them before my previous email):
>
> - torify is just a wrapper around torsocks. The tor package might be
> installed but not running, or some people might
A few more things before you consider shipping this (sorry for not
thinking of them before my previous email):
- torify is just a wrapper around torsocks. The tor package might be
installed but not running, or some people might have machines with
torsocks configured to talk to a remote Tor daemon
Hi! I stumbled across this bug, and it looked like there were a
couple of issues with the previous version of the patch:
- mentioned "sockproxy" instead of "torsocks" in one place
- disabling SMTP relied on USETOR=yes, but the torify function assumed
"always/auto/no"
So I've updated the patch ag
8 matches
Mail list logo
