From: "David Roman" <davidroman96@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: app-crypt/certbot-dns-rfc2136/
Date: Tue, 11 Mar 2025 13:35:51 +0000 (UTC) [thread overview]
Message-ID: <1741699840.06b267b5d8f28fc3ddc8275a8bd799773ed0864b.davidroman@gentoo> (raw)
commit: 06b267b5d8f28fc3ddc8275a8bd799773ed0864b
Author: Thibaud CANALE <thican <AT> thican <DOT> net>
AuthorDate: Tue Mar 11 13:26:35 2025 +0000
Commit: David Roman <davidroman96 <AT> gmail <DOT> com>
CommitDate: Tue Mar 11 13:30:40 2025 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=06b267b5
app-crypt/certbot-dns-rfc2136: provide transition package
The new merged app-crypt/certbot has blockers on all the old split
modules like certbot-nginx, which leads to poor UX when users who have
e.g. certbot-nginx in their world file now to try to upgrade.
Add a dummy set of ebuilds for the old split modules to depend on the
merged certbot with the right USE, which we can last-rite in a while.
Signed-off-by: Thibaud CANALE <thican <AT> thican.net>
.../certbot-dns-rfc2136-3.2.0-r100.ebuild | 30 ++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/app-crypt/certbot-dns-rfc2136/certbot-dns-rfc2136-3.2.0-r100.ebuild b/app-crypt/certbot-dns-rfc2136/certbot-dns-rfc2136-3.2.0-r100.ebuild
new file mode 100644
index 000000000..372aa0938
--- /dev/null
+++ b/app-crypt/certbot-dns-rfc2136/certbot-dns-rfc2136-3.2.0-r100.ebuild
@@ -0,0 +1,30 @@
+# Copyright 1999-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DESCRIPTION="RFC 2136 DNS Authenticator plugin for Certbot (Let’s Encrypt Client)"
+HOMEPAGE="
+ https://github.com/certbot/certbot
+ https://pypi.org/project/certbot-dns-rfc2136/
+ https://certbot-dns-rfc2136.readthedocs.io/en/stable/
+ https://letsencrypt.org/
+"
+
+LICENSE="metapackage"
+SLOT="0"
+
+KEYWORDS="~amd64 ~arm64 ~riscv"
+
+# Meta package for transition
+# No need to upgrade thanks to ">="
+RDEPEND="
+ >=app-crypt/certbot-${PV}-r100[certbot-dns-rfc2136]
+"
+
+pkg_postinst() {
+ elog "This is a meta-package to help in transition to single package "
+ elog "app-crypt/certbot."
+ elog "It is advice to simply deselect this package and to emerge "
+ elog "app-crypt/certbot[certbot-dns-rfc2136] for this module."
+}
next reply other threads:[~2025-03-11 13:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:35 David Roman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 13:35 [gentoo-commits] repo/proj/guru:master commit in: app-crypt/certbot-dns-rfc2136/ David Roman
2025-03-11 13:35 David Roman
2025-03-04 9:39 David Roman
2025-01-09 10:39 David Roman
2024-11-16 4:00 Haelwenn Monnier
2024-05-15 16:06 Julien Roy
2024-04-04 10:09 Florian Schmaus
2024-02-23 23:40 Julien Roy
2024-02-23 23:40 Julien Roy
2023-12-20 9:10 David Roman
2023-12-20 9:10 David Roman
2023-11-21 15:05 David Roman
2023-11-21 15:05 David Roman
2023-05-16 5:08 Viorel Munteanu
2023-05-16 5:08 Viorel Munteanu
2023-04-09 10:05 Viorel Munteanu
2023-03-16 8:41 Florian Schmaus
2023-03-16 8:41 Florian Schmaus
2023-01-30 10:29 Viorel Munteanu
2023-01-30 10:29 Viorel Munteanu
2022-10-07 13:13 Arthur Zamarin
2022-10-07 13:13 Arthur Zamarin
2022-09-13 10:53 Andrew Ammerlaan
2022-09-13 10:53 Andrew Ammerlaan
2022-07-20 9:35 Andrew Ammerlaan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1741699840.06b267b5d8f28fc3ddc8275a8bd799773ed0864b.davidroman@gentoo \
--to=davidroman96@gmail.com \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox