From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/recover-broken-vdb/
Date: Tue, 10 Jan 2023 03:52:43 +0000 (UTC) [thread overview]
Message-ID: <1673322668.7bf537783704355b8c01a487d291698fecf35a74.sam@gentoo> (raw)
commit: 7bf537783704355b8c01a487d291698fecf35a74
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 10 03:51:08 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jan 10 03:51:08 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7bf53778
app-portage/recover-broken-vdb: enable py3.11
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-portage/recover-broken-vdb/recover-broken-vdb-1.0.0-r1.ebuild | 4 ++--
app-portage/recover-broken-vdb/recover-broken-vdb-9999.ebuild | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/app-portage/recover-broken-vdb/recover-broken-vdb-1.0.0-r1.ebuild b/app-portage/recover-broken-vdb/recover-broken-vdb-1.0.0-r1.ebuild
index 090365bd9c15..9a8d5f3fb8c0 100644
--- a/app-portage/recover-broken-vdb/recover-broken-vdb-1.0.0-r1.ebuild
+++ b/app-portage/recover-broken-vdb/recover-broken-vdb-1.0.0-r1.ebuild
@@ -1,11 +1,11 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
DISTUTILS_SINGLE_IMPL=1
DISTUTILS_USE_PEP517=setuptools
-PYTHON_COMPAT=( python3_{8..10} )
+PYTHON_COMPAT=( python3_{8..11} )
inherit distutils-r1
diff --git a/app-portage/recover-broken-vdb/recover-broken-vdb-9999.ebuild b/app-portage/recover-broken-vdb/recover-broken-vdb-9999.ebuild
index 6577b6801c54..1cb2cd3a33bb 100644
--- a/app-portage/recover-broken-vdb/recover-broken-vdb-9999.ebuild
+++ b/app-portage/recover-broken-vdb/recover-broken-vdb-9999.ebuild
@@ -1,11 +1,11 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
DISTUTILS_SINGLE_IMPL=1
DISTUTILS_USE_PEP517=setuptools
-PYTHON_COMPAT=( python3_{8..10} )
+PYTHON_COMPAT=( python3_{8..11} )
inherit distutils-r1
next reply other threads:[~2023-01-10 3:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 3:52 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-03 9:35 [gentoo-commits] repo/gentoo:master commit in: app-portage/recover-broken-vdb/ Sam James
2024-04-29 21:48 Sam James
2023-01-10 3:52 Sam James
2022-09-18 13:46 Michał Górny
2022-02-20 5:51 Sam James
2022-01-29 6:05 Sam James
2021-12-27 4:16 Sam James
2021-12-27 4:16 Sam James
2021-10-05 3:40 Sam James
2021-10-03 23:35 Sam James
2021-10-03 23:35 Sam James
2021-10-01 3:07 Sam James
2021-09-30 0:45 Sam James
2021-09-30 0:45 Sam James
2021-09-29 21:08 Sam James
2021-09-29 20:48 Sam James
2021-09-29 17:04 Sam James
2021-09-29 17:04 Sam James
2021-09-29 16:01 Sam James
2021-09-29 16:01 Sam James
2021-09-29 16:01 Sam James
2021-09-28 23:54 Sam James
2021-09-27 19:14 Sam James
2021-09-27 19:14 Sam James
2021-09-24 5:39 Sam James
2021-09-23 23:00 Sam James
2021-09-23 20:56 Sam James
2021-09-21 17:41 Sam James
2021-09-21 17:41 Sam James
2021-09-21 2:55 Sam James
2021-09-20 22:14 Sam James
2021-09-20 22:14 Sam James
2021-09-20 21:11 Sam James
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=1673322668.7bf537783704355b8c01a487d291698fecf35a74.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