Closed DorianCoding closed 1 week ago
@DorianCoding you mentioned certbot 3.0.0 but 2.11.0 is the latest release?!
https://community.letsencrypt.org/t/certbot-3-0-could-have-potential-third-party-snap-breakages/226940Le 18 oct. 2024 16:12, helgeerbe @.***> a écrit : @DorianCoding you mentioned certbot 3.0.0 but 2.11.0 is the latest release?!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
https://community.letsencrypt.org/t/certbot-3-0-could-have-potential-third-party-snap-breakages/226940Le 18 oct. 2024 16:12, helgeerbe @.> a écrit : @DorianCoding you mentioned certbot 3.0.0 but 2.11.0 is the latest release?! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>
Thanks for the link. But this will not work for pip packages. You can't use non existent versions as dependency. The only solution is, to update this plugin, as soon as certbot 3.0.0 is available.
Thanks for the link. But this will not work for pip packages. You can't use non existent versions as dependency. The only solution is, to update this plugin, as soon as certbot 3.0.0 is available.
For snap build is blocked and would unlock when it's okay. I don't know for pip packages. But if you're not synchronized with pip by your Github repo, it could be fine for now. Anyway you can keep the pull open and accept when pip package is updated.
Hello,
Please find all my changes to sync our repos (the default one and the one with the snap on it). I've corrected the error when there is some API errors, see new messages:
Thanks.