Package: letsencrypt
Followup-For: Bug #825882
https://letsencrypt.org/2016/03/09/le-client-new-home.html and
https://letsencrypt.org/getting-started/ both talk about transition, the
Getting Started guide mentions certbot. So S. is right here. It could be an
idea to create virtual packages
On letsencrypt site seems that the letsencrypt binary has been superseeded by
certbot. Packages certbot and python-certbot-apache installs just fine from
backports, so this can be a quick workaround for now. Neverthless,
letsencrypt* packages should provide a clean migration path to the certbot*
Package: python-letsencrypt
Version: 0.5.0-1~bpo8+1
Followup-For: Bug #825882
Absolutely. letsencrypt only exists on backports, and there it has
broken dependencies rendering the installation impossible.
python-acme 0.6.0-1~bpo8+1
Breaks: python-certbot (<< 0.6.0), python-letsencrypt (<< 0.6.0)
And there isn't a python-letsencrypt version 0.6.0 on the repository, that
is why it can't be installed.
Achilleas Kotsis | Αχιλλέας Κώτσης
Package: python-letsencrypt
Version: 0.5.0-1~bpo8+1
Severity: important
Tags: upstream
letsencrypt depends on python-letsencrypt, which depends on python-acme.
The latter breaks the installation, even though:
# apt-get install letsencrypt python-letsencrypt
Reading package lists... Done
Building
5 matches
Mail list logo