Re: [Letsencrypt-devel] Certbot in Debian Stretch

On Tue, Nov 22, 2016 at 9:40 AM, Peter Eckersley wrote: > currently working with an ACME backwards compatibilty window of 6-12 months, > but probably not longer than that. I note that letsencrypt 0.4.1-1 (before the rename to certbot) is available in Ubuntu xenial, which is scheduled for 5 years

Re: [Letsencrypt-devel] Certbot in Debian Stretch

On November 25, 2016 4:05:30 PM EST, James Cloos wrote: >It may have been; in any case it took *weeks* for the bug I saw to get >fixed. And it doesn't matter where the bug was, it still made it >impossible to apt-get install the certbot package. Which still defines >the

Re: [Letsencrypt-devel] Certbot in Debian Stretch

> "HL" == Harlan Lieberman-Berg writes: HL> In fact, letsencrypt was never in jessie either. Both certbot and HL> letsencrypt have only ever been in stable-bpo, stretch, and sid. Ok. That must have been before I was forced to switch my openvz systems from sid to

Re: [Letsencrypt-devel] Certbot in Debian Stretch

James Cloos writes: > HL> Certbot has never been in jessie, so I imagine it wouldn't have been > usable. > > Certbot, letsencrypt, python-acme, et cetera; the package name doesn't > matter for this purpose. In fact, letsencrypt was never in jessie either. Both certbot and

Re: [Letsencrypt-devel] Certbot in Debian Stretch

> "HL" == Harlan Lieberman-Berg writes: HL> Certbot has never been in jessie, so I imagine it wouldn't have been usable. Certbot, letsencrypt, python-acme, et cetera; the package name doesn't matter for this purpose. HL> I'm also haven't gotten any tickets about it