From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/mitmproxy_wireguard/
Date: Tue, 30 Jul 2024 08:00:26 +0000 (UTC) [thread overview]
Message-ID: <1722326388.ff021cb51d6460ab2fc7a0e547fa353b3aea6159.pacho@gentoo> (raw)
commit: ff021cb51d6460ab2fc7a0e547fa353b3aea6159
Author: Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 30 07:41:36 2024 +0000
Commit: Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Tue Jul 30 07:59:48 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff021cb5
dev-python/mitmproxy_wireguard: enable py3.12
Closes: https://bugs.gentoo.org/929470
Signed-off-by: Pacho Ramos <pacho <AT> gentoo.org>
dev-python/mitmproxy_wireguard/mitmproxy_wireguard-0.1.20.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-python/mitmproxy_wireguard/mitmproxy_wireguard-0.1.20.ebuild b/dev-python/mitmproxy_wireguard/mitmproxy_wireguard-0.1.20.ebuild
index 18f4d27e3683..8b203a51a8e5 100644
--- a/dev-python/mitmproxy_wireguard/mitmproxy_wireguard-0.1.20.ebuild
+++ b/dev-python/mitmproxy_wireguard/mitmproxy_wireguard-0.1.20.ebuild
@@ -1,11 +1,11 @@
-# Copyright 2022-2023 Gentoo Authors
+# Copyright 2022-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
DISTUTILS_EXT=1
DISTUTILS_USE_PEP517=maturin
-PYTHON_COMPAT=( python3_{9..11} )
+PYTHON_COMPAT=( python3_{10..12} )
CRATES="
adler@1.0.2
next reply other threads:[~2024-07-30 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 8:00 Pacho Ramos [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 19:47 [gentoo-commits] repo/gentoo:master commit in: dev-python/mitmproxy_wireguard/ Michał Górny
2024-11-22 19:47 Michał Górny
2023-12-07 16:22 Matthew Smith
2023-06-18 18:47 Michał Górny
2023-02-21 9:30 Sam James
2023-01-18 17:43 Matthew Smith
2022-12-05 20:17 Arthur Zamarin
2022-11-18 8:49 Arthur Zamarin
2022-11-02 12:31 Matthew Smith
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=1722326388.ff021cb51d6460ab2fc7a0e547fa353b3aea6159.pacho@gentoo \
--to=pacho@gentoo.org \
--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