On Tue, 2019-09-03 at 22:16 -0400, Harlan Lieberman-Berg wrote: > We have a proposed update for acme in stretch (oldstable). This is > necessary to prevent the package, and all its dependencies, stopping > to work due to changes to the web service that the acme module is > primarily used for. (Let's Encrypt)
Apparently this is now only an issue for the staging endpoint in the immediate future, according to https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauthenticated-resource-gets/74380/3 On that basis, could releasing this update now wait until the next stretch point release, or is the change to the staging endpoint still likely to have a significant enough impact to want to make an earlier release? Regards, Adam
