Re: [Letsencrypt-devel] Package Name Change

2016-04-15 Thread Francois Marier
On 2016-04-11 07:33, Harlan Lieberman-Berg wrote: At this point, it looks like the python modules will be changing the distribution name, but not the actual module name (i.e., pip install , but import letsencrypt). If that stays the same, I think it's probably OK for us to leave the name of

Re: [Letsencrypt-devel] Bug#815199: ITP: acme-tiny -- letsencrypt tiny python client

2016-03-06 Thread Francois Marier
On 2016-03-04 at 21:43:38, Harlan Lieberman-Berg wrote: > Took a look over it; it looks in good shape! (The only thing I can see, > very nitpicky, is that you could add a debian/watch file explaining > upstream doesn't support versions yet, and what your versioning scheme > is in the meantime.) >

[Letsencrypt-devel] Bug#809355: Bug#809355: letsencrypt: should delegate dir management (e.g. /etc/letsencrypt) to dpkg

2015-12-29 Thread Francois Marier
On 2015-12-29 at 20:15:31, Leo Antunes wrote: > letsencrypt creates /etc/letsencrypt and /var/log/letsencrypt when first > run, instead of having dpkg manage them. This means purging the package > won't get rid of these folders. I've added a postrm script to clean up these directories. This