Package: python-pip
Version: 8.1.1-2
When trying to install a package in editable mode using setuptools
extras, pip crashes. Downgrading to pip 8.1.0 fixes the problem. I've
demonstrated the problem below using the Debian Sid docker image and the
pip GitHub repo as an example.
This has been fixed in Certbot's 0.19.0 release.
Package: virtualenv
Version: 15.1.0+ds-1
If a network error occurs while installing a package with pip in a
virtual environment, a TypeError is raised when pip attempts to retry
the request. To cause this, I installed virtualenv and python and ran:
virtualenv venv
. ./venv/bin/activate
After
I’m another upstream developer of Certbot.
Taking 0.21.1 into stable would be the most conservative update that would
resolve this issue. The oldest version you could take is 0.21.0, but 0.21.1 was
released 8 days later and as a result has been much more widely tested. Since
0.21.1 was
Package: python3-lexicon
Version: 2.1.21-1
Over the weekend, lexicon released version 2.2.1 which adds support for
multiple TXT records on the same domain. This functionality is needed in
plugins for Certbot like python3-certbot-dns-dnsimple. Future versions of this
and other Certbot plugins
What can be done to get this issue resolved?
This issue has jumped in priority now that domain validation through the
TLS-SNI-01 challenge will be completely unsupported by Let’s Encrypt on
February 13th, 2019. See
I just wanted to make sure this was still on everyone’s radar. The change
server side where tens of thousands of Debian users will begin being unable to
renew their certificates is in less than a month.
> On Jan 8, 2019, at 4:24 PM, Harlan Lieberman-Berg wrote:
>
> Hello Julien, everyone,
>
To provide a little more information as an upstream maintainer of Certbot, the
lack of an upgrade here will affect a lot of Debian Jessie users.
Let’s Encrypt started sending out multiple emails telling affected users they
needed to upgrade their client or they will become unable to renew their
> On Feb 9, 2019, at 6:19 AM, Holger Levsen wrote:
>
> On Sat, Feb 09, 2019 at 02:54:43PM +0100, Ola Lundqvist wrote:
>> I can also add that I have looked into this for myself and the number of
>> needed dependencies is rather large. So it is not just certbot that need an
>> update, we also
>
> I have not checked if any of the above packages require further dependencies
> so the list may grow larger.
>
> Best regards
>
> // Ola
>
> On Sat, 9 Feb 2019 at 20:58, Brad Warren wrote:
>
>
> > On Feb 9, 2019, at 6:19 AM, Holger Levsen wrote:
&g
I agree with the concerns about updating python3-cryptography in jessie.
If we can’t update jessie, I’d ideally love to see the packages in
jessie-backports updated. Despite the announcement that jessie-backports was
discontinued ~6 months ago, tens of thousands of users and many more domains
Package: python3-acme
Version: 0.28.0-1~deb9u1
The python*-acme packages will no longer work with Let’s Encrypt’s “ACMEv2”
endpoint which is their RFC 8555 compliant endpoint starting November 1st. See
Any updates on this?
Looking at server logs, I expect ~145K+ unique installations to be affected by
this problem if it doesn’t get fixed.
I’m an upstream maintainer of python-acme.
Both Let’s Encrypt [1] and the Certbot client which uses this library encourage
people to use Let’s Encrypt’s staging endpoint to test that they have things
working correctly before using Let’s Encrypt’s production endpoint which has
strict rate
+1 /etc/letsencrypt/archive/nrgcoin.org/{fullchain,chain}{5,6}.pem
Thanks,
Brad Warren
15 matches
Mail list logo
