From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-doc/gimp-help/
Date: Sun, 27 Apr 2025 17:37:39 +0000 (UTC) [thread overview]
Message-ID: <1745775427.3eeacf8b4985940f2c745ba5c7c8885130f3fb3e.sam@gentoo> (raw)
commit: 3eeacf8b4985940f2c745ba5c7c8885130f3fb3e
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 27 17:36:47 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 27 17:37:07 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3eeacf8b
app-doc/gimp-help: enable py3.13 for 2*
gimp-3 isn't ready to stable yet, let's backport py3.13 to 2* instead.
Bug: https://bugs.gentoo.org/953649
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-doc/gimp-help/gimp-help-2.10.34-r2.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-doc/gimp-help/gimp-help-2.10.34-r2.ebuild b/app-doc/gimp-help/gimp-help-2.10.34-r2.ebuild
index 68abe96b8462..5db5559669b9 100644
--- a/app-doc/gimp-help/gimp-help-2.10.34-r2.ebuild
+++ b/app-doc/gimp-help/gimp-help-2.10.34-r2.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-PYTHON_COMPAT=( python3_{10..12} )
+PYTHON_COMPAT=( python3_{10..13} )
inherit python-any-r1
DESCRIPTION="GNU Image Manipulation Program help files"
next reply other threads:[~2025-04-27 17:37 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 17:37 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-05 5:36 [gentoo-commits] repo/gentoo:master commit in: app-doc/gimp-help/ Sam James
2025-03-18 19:23 Sam James
2024-03-21 3:16 Sam James
2023-12-23 20:34 Sam James
2023-12-23 20:33 Sam James
2023-11-30 15:59 Ionen Wolkens
2023-08-18 21:50 Sam James
2023-08-18 9:21 Sam James
2023-08-18 9:21 Sam James
2023-08-18 8:32 Sam James
2023-05-19 23:50 Sam James
2023-05-07 13:35 Ulrich Müller
2023-05-07 13:35 Ulrich Müller
2023-05-05 22:38 Sam James
2023-05-04 6:48 Sam James
2022-10-10 7:43 Arthur Zamarin
2022-10-10 7:43 Arthur Zamarin
2022-10-10 7:43 Arthur Zamarin
2022-10-08 16:49 Arthur Zamarin
2022-06-07 6:34 Joonas Niilola
2022-06-07 6:34 Joonas Niilola
2022-06-07 6:33 Agostino Sarubbo
2022-06-07 6:33 Agostino Sarubbo
2022-06-07 6:32 Agostino Sarubbo
2022-06-07 1:15 Sam James
2022-02-27 0:54 Sam James
2022-02-27 0:54 Sam James
2022-02-27 0:54 Sam James
2021-12-12 14:23 Yixun Lan
2020-09-23 11:07 Michał Górny
2020-09-23 10:29 Agostino Sarubbo
2020-09-23 10:24 Agostino Sarubbo
2020-09-23 10:20 Agostino Sarubbo
2020-09-22 6:33 Sergei Trofimovich
2020-09-20 22:40 Thomas Deutschmann
2020-09-16 8:04 Joonas Niilola
2020-09-16 8:04 Joonas Niilola
2020-02-11 10:20 Michał Górny
2019-12-07 12:47 Joonas Niilola
2019-12-07 12:47 Joonas Niilola
2019-02-18 21:24 Pacho Ramos
2019-02-18 19:48 Sergei Trofimovich
2019-02-17 22:58 Patrice Clement
2019-02-07 10:35 Mikle Kolyada
2019-01-31 21:24 Tobias Klausmann
2019-01-27 14:14 Sergei Trofimovich
2019-01-27 14:09 Sergei Trofimovich
2019-01-27 12:13 Sergei Trofimovich
2018-04-22 21:04 Matt Turner
2018-04-08 22:42 Patrice Clement
2017-06-12 8:58 Michael Palimaka
2017-06-12 8:58 Michael Palimaka
2016-06-24 22:02 Ulrich Müller
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=1745775427.3eeacf8b4985940f2c745ba5c7c8885130f3fb3e.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