From: "Florian Schmaus" <flow@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-tex/rubber/
Date: Sun, 26 Feb 2023 14:25:50 +0000 (UTC) [thread overview]
Message-ID: <1677421540.64eadcd22b1f7793fa8a575f0a26e48e5f6681c4.flow@gentoo> (raw)
commit: 64eadcd22b1f7793fa8a575f0a26e48e5f6681c4
Author: Florian Schmaus <flow <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 26 12:08:51 2023 +0000
Commit: Florian Schmaus <flow <AT> gentoo <DOT> org>
CommitDate: Sun Feb 26 14:25:40 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=64eadcd2
dev-tex/rubber: mark Python 3.11 compatible
Closes: https://bugs.gentoo.org/896912
Signed-off-by: Florian Schmaus <flow <AT> gentoo.org>
dev-tex/rubber/rubber-1.5.1-r1.ebuild | 2 +-
dev-tex/rubber/rubber-1.6.0-r1.ebuild | 2 +-
dev-tex/rubber/rubber-9999.ebuild | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/dev-tex/rubber/rubber-1.5.1-r1.ebuild b/dev-tex/rubber/rubber-1.5.1-r1.ebuild
index f0854a9d276b..2a80c8a79354 100644
--- a/dev-tex/rubber/rubber-1.5.1-r1.ebuild
+++ b/dev-tex/rubber/rubber-1.5.1-r1.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=7
-PYTHON_COMPAT=( python3_{9..10} )
+PYTHON_COMPAT=( python3_{9..11} )
inherit distutils-r1
diff --git a/dev-tex/rubber/rubber-1.6.0-r1.ebuild b/dev-tex/rubber/rubber-1.6.0-r1.ebuild
index 5fd200da2906..5785279df623 100644
--- a/dev-tex/rubber/rubber-1.6.0-r1.ebuild
+++ b/dev-tex/rubber/rubber-1.6.0-r1.ebuild
@@ -3,7 +3,7 @@
EAPI=7
-PYTHON_COMPAT=( python3_{9..10} )
+PYTHON_COMPAT=( python3_{9..11} )
DISTUTILS_USE_SETUPTOOLS="no"
inherit distutils-r1
diff --git a/dev-tex/rubber/rubber-9999.ebuild b/dev-tex/rubber/rubber-9999.ebuild
index 90521d934140..52c54772aed8 100644
--- a/dev-tex/rubber/rubber-9999.ebuild
+++ b/dev-tex/rubber/rubber-9999.ebuild
@@ -3,7 +3,7 @@
EAPI=7
-PYTHON_COMPAT=( python3_{9..10} )
+PYTHON_COMPAT=( python3_{9..11} )
DISTUTILS_USE_SETUPTOOLS="no"
inherit distutils-r1
next reply other threads:[~2023-02-26 14:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 14:25 Florian Schmaus [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-23 13:16 [gentoo-commits] repo/gentoo:master commit in: dev-tex/rubber/ Arthur Zamarin
2025-01-18 10:52 Florian Schmaus
2025-01-18 10:52 Florian Schmaus
2024-12-09 21:00 Florian Schmaus
2024-12-09 21:00 Florian Schmaus
2024-10-25 12:16 Arthur Zamarin
2024-10-25 12:16 Arthur Zamarin
2024-06-03 18:09 Florian Schmaus
2024-05-07 19:24 Sebastian Pipping
2024-04-21 11:38 Ulrich Müller
2024-04-13 14:15 Sebastian Pipping
2024-04-12 8:35 Florian Schmaus
2024-04-10 19:42 Sebastian Pipping
2023-03-31 18:05 Sam James
2022-06-08 8:12 Florian Schmaus
2021-10-26 1:21 Yixun Lan
2021-07-01 9:01 Florian Schmaus
2021-07-01 9:01 Florian Schmaus
2021-06-22 6:34 Florian Schmaus
2021-06-08 7:10 Sam James
2020-12-03 11:10 Sam James
2020-12-03 11:01 Sam James
2020-12-03 9:16 Sam James
2020-12-03 9:16 Sam James
2020-08-20 10:41 Mikle Kolyada
2020-08-11 7:03 Sergei Trofimovich
2020-08-05 13:53 Agostino Sarubbo
2020-02-08 12:44 Ulrich Müller
2017-01-15 10:33 Pacho Ramos
2017-01-01 12:43 Agostino Sarubbo
2016-01-06 9:45 Alexis Ballier
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=1677421540.64eadcd22b1f7793fa8a575f0a26e48e5f6681c4.flow@gentoo \
--to=flow@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