From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/repo/
Date: Wed, 17 May 2023 01:38:18 +0000 (UTC) [thread overview]
Message-ID: <1684287337.611dafabe51a79f56b870871205357436f134823.sam@gentoo> (raw)
commit: 611dafabe51a79f56b870871205357436f134823
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed May 17 01:35:37 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed May 17 01:35:37 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=611dafab
dev-vcs/repo: disable py3.9
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-vcs/repo/repo-2.30.ebuild | 2 +-
dev-vcs/repo/repo-2.32.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-vcs/repo/repo-2.30.ebuild b/dev-vcs/repo/repo-2.30.ebuild
index 689627ea3f59..25394f1e60c7 100644
--- a/dev-vcs/repo/repo-2.30.ebuild
+++ b/dev-vcs/repo/repo-2.30.ebuild
@@ -7,7 +7,7 @@
EAPI="7"
-PYTHON_COMPAT=( python3_{9..11} )
+PYTHON_COMPAT=( python3_{10..11} )
inherit bash-completion-r1 python-r1
diff --git a/dev-vcs/repo/repo-2.32.ebuild b/dev-vcs/repo/repo-2.32.ebuild
index 3f8289ccea46..c008c0bbe33c 100644
--- a/dev-vcs/repo/repo-2.32.ebuild
+++ b/dev-vcs/repo/repo-2.32.ebuild
@@ -7,7 +7,7 @@
EAPI="7"
-PYTHON_COMPAT=( python3_{9..11} )
+PYTHON_COMPAT=( python3_{10..11} )
inherit bash-completion-r1 python-r1
next reply other threads:[~2023-05-17 1:38 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 1:38 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-21 22:18 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/repo/ Sam James
2024-12-21 14:15 Michał Górny
2024-12-21 14:15 Michał Górny
2024-12-21 12:49 Arthur Zamarin
2024-12-21 12:43 Arthur Zamarin
2024-12-21 12:43 Arthur Zamarin
2024-12-21 11:54 Florian Schmaus
2024-10-11 9:44 Florian Schmaus
2024-10-11 9:44 Florian Schmaus
2024-07-10 6:59 Florian Schmaus
2024-06-18 10:30 Sam James
2024-06-18 10:30 Sam James
2024-06-18 10:30 Sam James
2024-06-18 10:30 Sam James
2024-06-18 10:20 Sam James
2024-05-23 9:14 Florian Schmaus
2024-05-23 9:14 Florian Schmaus
2023-12-14 20:05 Mike Frysinger
2023-12-14 20:05 Mike Frysinger
2023-12-14 20:02 Mike Frysinger
2023-10-16 9:11 Mike Frysinger
2023-10-16 9:11 Mike Frysinger
2023-10-16 9:11 Mike Frysinger
2023-05-17 1:38 Sam James
2023-05-17 1:38 Sam James
2023-05-01 2:27 Sam James
2023-05-01 2:26 Sam James
2023-05-01 1:55 Sam James
2023-05-01 0:16 Sam James
2023-05-01 0:16 Sam James
2023-05-01 0:12 Sam James
2023-05-01 0:09 Sam James
2022-11-24 6:20 Mike Frysinger
2022-11-24 6:20 Mike Frysinger
2022-11-24 6:20 Mike Frysinger
2022-08-23 15:58 Mike Frysinger
2022-08-23 15:58 Mike Frysinger
2022-05-09 9:58 Jakov Smolić
2022-05-08 4:10 Sam James
2022-05-07 10:57 Jakov Smolić
2022-05-07 10:03 Arthur Zamarin
2022-05-06 23:43 Jakov Smolić
2022-05-06 23:38 Jakov Smolić
2022-02-04 4:12 Mike Frysinger
2022-02-04 4:12 Mike Frysinger
2022-02-04 4:12 Mike Frysinger
2021-10-02 3:41 Mike Frysinger
2021-10-02 3:41 Mike Frysinger
2021-10-02 3:41 Mike Frysinger
2021-05-18 1:09 Mike Frysinger
2021-05-18 1:09 Mike Frysinger
2021-05-18 1:09 Mike Frysinger
2021-04-29 1:52 Sam James
2021-04-19 17:01 Mike Frysinger
2021-04-19 17:01 Mike Frysinger
2021-03-15 17:44 Mike Frysinger
2021-03-15 17:44 Mike Frysinger
2021-03-01 16:20 Mike Frysinger
2021-03-01 16:20 Mike Frysinger
2021-03-01 16:20 Mike Frysinger
2021-01-13 17:20 Mike Frysinger
2021-01-13 17:20 Mike Frysinger
2020-09-19 9:54 Michał Górny
2020-08-20 4:52 Mike Frysinger
2020-08-20 4:52 Mike Frysinger
2020-08-20 4:52 Mike Frysinger
2020-05-19 19:43 Mike Frysinger
2020-05-19 19:43 Mike Frysinger
2020-02-19 23:46 Mike Frysinger
2020-02-19 23:46 Mike Frysinger
2020-02-13 1:45 Mike Frysinger
2020-02-10 21:00 Michał Górny
2020-02-10 15:35 Mike Frysinger
2020-02-10 15:35 Mike Frysinger
2019-11-18 7:53 Mike Frysinger
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=1684287337.611dafabe51a79f56b870871205357436f134823.sam@gentoo \
--to=sam@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