From main package app-crypt/certbot, and starting from ebuild release 3.2.0-r100, Certbot modules including ACME are packaged into a single atom. News item covering this situation had been published almost one month ago, 2025-03-07. I will consider last rites in 90 days, 3 months, so users have time to update their configuration, maybe more time? Also see bug 950247 for last rite on app-crypt/certbot-dns-dnsimple.
I forgot the current "stable" version is not yet using the single package procedure, so this last rite should be postponed.
(In reply to Thibaud CANALE from comment #1) > I forgot the current "stable" version is not yet using the single package > procedure, so this last rite should be postponed. Yeah, the clock should really start once it's all stabled.
(In reply to Sam James from comment #2) > (In reply to Thibaud CANALE from comment #1) > > I forgot the current "stable" version is not yet using the single package > > procedure, so this last rite should be postponed. > > Yeah, the clock should really start once it's all stabled. Agree as I thought about it, I decided at least to do the main work and I will update the date in the PR once necessary. Also, except if I missed something, the current work is waiting to be proceed; don’t hesitate to notify me if you need it.
Thibaud, what's the reasoning behind all the "certbot-" prefixes on the USE flags? Makes them harder to read for no benefit (at least that I understand).
(In reply to John R. Graham from comment #4) > Thibaud, what's the reasoning behind all the "certbot-" prefixes on the USE > flags? Makes them harder to read for no benefit (at least that I understand). This is not related to this issue, thanks to create a new dedicated entry without rhetorical question. Best regards.
