From: "Thibaud CANALE" <thican@thican.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: app-crypt/certbot-dns-rfc2136/
Date: Thu, 6 Oct 2022 22:12:56 +0000 (UTC) [thread overview]
Message-ID: <1665094181.deb75c74ab2508bcbccbc980c2c3b01a4f852b95.thican@gentoo> (raw)
commit: deb75c74ab2508bcbccbc980c2c3b01a4f852b95
Author: Thibaud CANALE <thican <AT> thican <DOT> net>
AuthorDate: Tue Oct 4 18:40:52 2022 +0000
Commit: Thibaud CANALE <thican <AT> thican <DOT> net>
CommitDate: Thu Oct 6 22:09:41 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=deb75c74
app-crypt/certbot-dns-rfc2136: add 1.31.0
Signed-off-by: Thibaud CANALE <thican <AT> thican.net>
app-crypt/certbot-dns-rfc2136/Manifest | 1 +
.../certbot-dns-rfc2136-1.31.0.ebuild | 67 ++++++++++++++++++++++
2 files changed, 68 insertions(+)
diff --git a/app-crypt/certbot-dns-rfc2136/Manifest b/app-crypt/certbot-dns-rfc2136/Manifest
index 8ae96f64b..4374c9ab7 100644
--- a/app-crypt/certbot-dns-rfc2136/Manifest
+++ b/app-crypt/certbot-dns-rfc2136/Manifest
@@ -1,2 +1,3 @@
DIST certbot-1.29.0.tar.gz 1367853 BLAKE2B c0d8d2c05a061b2d50564a97bf17ae883bd443321bf99cea13fbae196c7ec876231d803d5389e524997dd8632035d5ad60b1a99b025a22a65d0865d564cfafc5 SHA512 755781e12e0e4cdb41aa16d90ab6a334ef41a98630e08127a867c8e8813ee45ebd3f6f54168fe747900f6ab59539e414ffed7891c05746b3a7af2e2a96a8d522
DIST certbot-1.30.0.tar.gz 1370072 BLAKE2B c9286bc6dfee59c5a7b458430b08ee273615b42e40d2355b41c5d58a0b8757d83551e947058660e4abda88d7f11c16184a248c313b4d01e145df0e39b717bf86 SHA512 15727a7a38a9cbe4890a347c0cc2a795be19502ece28034400d41cf96a6d4bef197890bd85cd02ecc6a792e3502ae8aa663aad45e980047567f0d3b161cbe3df
+DIST certbot-1.31.0.tar.gz 1371459 BLAKE2B 95fc9f29b1e91f5bc12a9b7146d00f4f3b4647eeda8e866c46c17d8d8a2443bd46cfa04758e8571e84b2bbf70bd68943c47ceaf6d830d3e5121e41d9548da051 SHA512 a2f6d7714bfc8e2c400e69be038404da138b53f0dc09e071048d560ba9e9527cc0b786b8d210b62c3d07c3aeadaee12dc0d060d144af4b5c3178576fde65b052
diff --git a/app-crypt/certbot-dns-rfc2136/certbot-dns-rfc2136-1.31.0.ebuild b/app-crypt/certbot-dns-rfc2136/certbot-dns-rfc2136-1.31.0.ebuild
new file mode 100644
index 000000000..c08c715c9
--- /dev/null
+++ b/app-crypt/certbot-dns-rfc2136/certbot-dns-rfc2136-1.31.0.ebuild
@@ -0,0 +1,67 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+PYTHON_COMPAT=( python3_{8..10} )
+DISTUTILS_USE_SETUPTOOLS=rdepend
+
+inherit distutils-r1
+
+PARENT_PN="${PN%-dns-rfc2136}"
+PARENT_P="${PARENT_PN}-${PV}"
+
+if [[ "${PV}" == *9999 ]]; then
+ inherit git-r3
+
+ EGIT_REPO_URI="https://github.com/certbot/certbot.git"
+ EGIT_SUBMODULES=()
+ EGIT_CHECKOUT_DIR="${WORKDIR}/${PARENT_PN}"
+else
+ # To rename with .gh.tar.gz extension once parent package also uses this naming.
+ SRC_URI="
+ https://github.com/certbot/certbot/archive/v${PV}.tar.gz
+ -> ${PARENT_P}.tar.gz
+ "
+ KEYWORDS="~amd64 ~arm ~arm64 ~x86"
+fi
+
+DESCRIPTION="RFC 2136 DNS Authenticator plugin for Certbot (Let’s Encrypt client)"
+HOMEPAGE="
+ https://letsencrypt.org/
+"
+
+LICENSE="Apache-2.0"
+SLOT="0"
+
+S="${WORKDIR}/${PARENT_P}/${PN}"
+
+RDEPEND="
+ ${PYTHON_DEPS}
+ >=app-crypt/acme-${PV}[${PYTHON_USEDEP}]
+ >=app-crypt/certbot-${PV}[${PYTHON_USEDEP}]
+ >=dev-python/pyopenssl-22.0.0[${PYTHON_USEDEP}]
+ >=dev-python/pyparsing-3.0.9[${PYTHON_USEDEP}]
+ >=dev-python/zope-interface-5.4.0[${PYTHON_USEDEP}]
+"
+
+distutils_enable_tests pytest
+
+# Same than PATCHES but from repository's root directory,
+# please see function `python_prepare_all` below.
+# Simplier for users IMHO.
+PARENT_PATCHES=(
+)
+
+# Here for patches within "${PN}" subdirectory.
+PATCHES=(
+)
+
+python_prepare_all() {
+ pushd "${WORKDIR}/${PARENT_P}" > /dev/null || die
+ [[ -n "${PARENT_PATCHES[@]}" ]] && eapply "${PARENT_PATCHES[@]}"
+ eapply_user
+ popd > /dev/null || die
+
+ distutils-r1_python_prepare_all
+}
next reply other threads:[~2022-10-06 22:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 22:12 Thibaud CANALE [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 13:31 [gentoo-commits] repo/proj/guru:dev commit in: app-crypt/certbot-dns-rfc2136/ Thibaud CANALE
2025-03-11 13:31 Thibaud CANALE
2025-03-11 13:31 Thibaud CANALE
2025-03-03 15:16 Thibaud CANALE
2025-01-08 17:17 Thibaud CANALE
2024-11-15 22:09 Thibaud CANALE
2024-09-22 14:34 Thibaud CANALE
2024-09-22 14:34 Thibaud CANALE
2024-05-15 16:06 [gentoo-commits] repo/proj/guru:master " Julien Roy
2024-05-15 15:45 ` [gentoo-commits] repo/proj/guru:dev " Julien Roy
2024-05-08 18:07 Thibaud CANALE
2024-04-04 1:02 Thibaud CANALE
2024-02-23 19:51 Thibaud CANALE
2024-02-23 19:51 Thibaud CANALE
2023-12-19 13:25 Thibaud CANALE
2023-12-19 13:25 Thibaud CANALE
2023-11-20 18:32 Thibaud CANALE
2023-11-20 18:32 Thibaud CANALE
2023-05-14 20:09 Thibaud CANALE
2023-05-14 20:07 Thibaud CANALE
2023-04-07 23:02 Thibaud CANALE
2023-03-15 0:41 Thibaud CANALE
2023-03-15 0:38 Thibaud CANALE
2023-01-30 0:50 Thibaud CANALE
2023-01-30 0:50 Thibaud CANALE
2022-11-12 2:32 Thibaud CANALE
2022-11-12 1:28 Thibaud CANALE
2022-11-11 20:23 Jack Sangdahl
2022-10-06 22:12 Thibaud CANALE
2022-09-12 21:13 Thibaud CANALE
2022-09-12 21:13 Thibaud CANALE
2022-07-17 21:59 Thibaud CANALE
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=1665094181.deb75c74ab2508bcbccbc980c2c3b01a4f852b95.thican@gentoo \
--to=thican@thican.net \
--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