On Fri, 2020-12-04 at 21:45 -0500, Harlan Lieberman-Berg wrote: > As part of the deprecation of the Let's Encrypt v1 endpoint beginning > in January, they are going to begin causing intermittant failures > increasing to a complete shutdown June 2021. > > To prevent users from being affected by this transition, I've > prepared a backport of the piece of code that switches renewals > automatically to v2. In this version of the code, new certificates > were already being issued through the v2 URL.
+python-certbot (0.31.0-1~deb10u1) buster; urgency=high That version number is lower than the package currently in buster. You want 0.31.0-1+deb10u1. + * Switch to use of ACMEv2 API to prevent renewal failures. (Closes: #971045) The metadata for that bug implies that it affects the package in unstable. I'm assuming that's simply an oversight? If so, please add an appropriate fixed version. (I'm not entirely sure why it was cloned from #969126 either, but that's not directly relevant here.) The next point release is likely to be in early February. Assuming the plan outlined at https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 is still current, it sounds like there will be one brown-out for v1 before that point, possibly two if we're unlikely with timing. Are we anticipating that being enough of an issue to warrant pushing the update via stable-updates before the point release? Regards, Adam
