Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-04-21 Thread Mattia Rizzolo
On Tue, Apr 12, 2016 at 09:15:19AM +0200, Daniel Beyer wrote: > I think the version we now have is good for an initial release. If you > agree, feel free to upload it to unstable. Uploaded :) Sorry it took so long, I got distracted by other matters :) I noticed another thing, but didn't want to

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-04-12 Thread Daniel Beyer
Hi Mattia, On Tue, 2016-04-05 at 21:15 +, Mattia Rizzolo wrote: > On Tue, Mar 29, 2016 at 05:45:44PM +0200, Daniel Beyer wrote: > > Hi Mattia, > > > > Am Montag, den 28.03.2016, 21:44 + schrieb Mattia Rizzolo: > > > Hi Daniel :) > > > > > > On Sun, Mar 27, 2016 at 01:01:18PM +0200,

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-04-05 Thread Mattia Rizzolo
On Tue, Mar 29, 2016 at 05:45:44PM +0200, Daniel Beyer wrote: > Hi Mattia, > > Am Montag, den 28.03.2016, 21:44 + schrieb Mattia Rizzolo: > > Hi Daniel :) > > > > On Sun, Mar 27, 2016 at 01:01:18PM +0200, Daniel Beyer wrote: > > (...) > > > > I think your apache snippet is cool, actually. >

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-03-29 Thread Daniel Beyer
Hi Mattia, Am Montag, den 28.03.2016, 21:44 + schrieb Mattia Rizzolo: > Hi Daniel :) > > On Sun, Mar 27, 2016 at 01:01:18PM +0200, Daniel Beyer wrote: > (...) > > I think your apache snippet is cool, actually. > I improved it a bit the thing, by moving it to be a config snippet, > instead

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-03-28 Thread Mattia Rizzolo
Hi Daniel :) On Sun, Mar 27, 2016 at 01:01:18PM +0200, Daniel Beyer wrote: > I might have overcomplicated things a bit with the current packaging > approach (e.g. providing apache configuration). You might want to take a > look yourself and share your thoughts. I think your apache snippet is

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-03-27 Thread Mattia Rizzolo
Control: retitle -1 ITP: letsencrypt.sh -- ACME client implemented in Bash On Sun, Mar 27, 2016 at 01:01:18PM +0200, Daniel Beyer wrote: > On Sat, 2016-03-26 at 21:07 +, Mattia Rizzolo wrote: > > On Thu, Jan 21, 2016 at 08:10:13AM +0100, Daniel Beyer wrote: > > > * Package name:

Processed: Re: Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-03-27 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 ITP: letsencrypt.sh -- ACME client implemented in Bash Bug #812174 [wnpp] letsencrypt.sh -- ACME client implemented in Bash Changed Bug title to 'ITP: letsencrypt.sh -- ACME client implemented in Bash' from 'letsencrypt.sh -- ACME client implemented in

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-03-27 Thread Daniel Beyer
Hi Mattia, thanks a lot for pushing this ITP. On Sat, 2016-03-26 at 21:07 +, Mattia Rizzolo wrote: > On Thu, Jan 21, 2016 at 08:10:13AM +0100, Daniel Beyer wrote: > > * Package name: letsencrypt-sh > > Is there a good reason not to call this package 'letsencrypt.sh', with a > dot, as

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-03-26 Thread Mattia Rizzolo
On Thu, Jan 21, 2016 at 08:10:13AM +0100, Daniel Beyer wrote: > * Package name: letsencrypt-sh Is there a good reason not to call this package 'letsencrypt.sh', with a dot, as the official name? Anyway, this email was to ask how it's going with this. It should be a fairly simple package,

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-01-20 Thread Daniel Beyer
Package: wnpp Severity: wishlist Owner: Daniel Beyer * Package name: letsencrypt-sh Version : 0.0.0~2016.01.21~git23b0ef5 Upstream Author : Lukas Schauer * URL : https://github.com/lukas2511/letsencrypt.sh * License