public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-tex/rubber/
Date: Tue,  8 Jun 2021 07:10:47 +0000 (UTC)	[thread overview]
Message-ID: <1623136239.57801817f5c91dc518de4e176ab72bb4a89c6ca2.sam@gentoo> (raw)

commit:     57801817f5c91dc518de4e176ab72bb4a89c6ca2
Author:     Florian Schmaus <flo <AT> geekplace <DOT> eu>
AuthorDate: Wed Jun  2 14:21:42 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jun  8 07:10:39 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=57801817

dev-tex/rubber: declare Python 3.9 compatibility in 1.5.1

I did some rudiementary testing with Rubber 1.5.1 and Python 3.9. This
combination was able to compile all presented .tex files. I am also
not aware of anything that causes Rubber 1.5/1.6 to be incompatible
with Python 3.9.

So, instead of stabilizing Rubber 1.6.1-alpha1 (bug #793332), sam and
I decided to have rubber 1.5.1 declare Python 3.9 support.

Bug: https://bugs.gentoo.org/793332
Signed-off-by: Florian Schmaus <flo <AT> geekplace.eu>
Closes: https://github.com/gentoo/gentoo/pull/21117
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-tex/rubber/rubber-1.5.1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-tex/rubber/rubber-1.5.1.ebuild b/dev-tex/rubber/rubber-1.5.1.ebuild
index 726374a9f4b..6c5ce209d65 100644
--- a/dev-tex/rubber/rubber-1.5.1.ebuild
+++ b/dev-tex/rubber/rubber-1.5.1.ebuild
@@ -1,8 +1,8 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2021 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
-PYTHON_COMPAT=( python3_{7,8} )
+PYTHON_COMPAT=( python3_{7,8,9} )
 
 inherit distutils-r1
 


             reply	other threads:[~2021-06-08  7:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  7:10 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-18 10:52 [gentoo-commits] repo/gentoo:master commit in: dev-tex/rubber/ 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
2023-02-26 14:25 Florian Schmaus
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
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=1623136239.57801817f5c91dc518de4e176ab72bb4a89c6ca2.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