Let me know if there's anything else I can do to help.
(If anyone's curious, the script I used for testing is at https://pastebin.com/DvQb3mT6. It uses some code we normally use for python-acme development and after running all tests, the script errors out due to not hitting the minimum code coverage percentage. This is OK and only happens because our tests aren't configured to monitor coverage on files located outside of our git repo. If you modify the script to stop installing python3-acme from proposed, the script fails much earlier due to the unpatched version of python3-acme not recognizing the new status type.)
I agree that this should be released early if possible.
The diff at https:/ /launchpadlibra rian.net/ 374731991/ python- acme_0. 22.2-1_ 0.22.2- 1ubuntu0. 1.diff. gz looks good and I tested this successfully using a modified version of https:/ /wiki.ubuntu. com/StableRelea seUpdates/ Certbot/ TestScript. The acme package I used during testing was:
python3-acme 0.22.2-1ubuntu0.1
Let me know if there's anything else I can do to help.
(If anyone's curious, the script I used for testing is at https:/ /pastebin. com/DvQb3mT6. It uses some code we normally use for python-acme development and after running all tests, the script errors out due to not hitting the minimum code coverage percentage. This is OK and only happens because our tests aren't configured to monitor coverage on files located outside of our git repo. If you modify the script to stop installing python3-acme from proposed, the script fails much earlier due to the unpatched version of python3-acme not recognizing the new status type.)