Iain Learmonth 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,
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
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
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,
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, symbolic links for old alpha repositories
point to the current
Hi,
On 30/06/18 12:53, Jaskaran Singh wrote:
> 0. Motivation and Overview
> We're using Maxmind's (company registered in the US) GeoIP Database,
> which is not just antithetical to the philosophy that one should not
> totally rely on a service/software for all needs, but has some serious
>
