public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyopengl/
Date: Fri, 24 Mar 2023 10:49:19 +0000 (UTC)	[thread overview]
Message-ID: <1679654942.3c5bb88a4d457bd7118c76cbdf80d9f86bbaffbf.arthurzam@gentoo> (raw)

commit:     3c5bb88a4d457bd7118c76cbdf80d9f86bbaffbf
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 24 10:49:02 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 24 10:49:02 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c5bb88a

dev-python/pyopengl: Stabilize 3.1.6-r2 ppc64, #900427

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-python/pyopengl/pyopengl-3.1.6-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pyopengl/pyopengl-3.1.6-r2.ebuild b/dev-python/pyopengl/pyopengl-3.1.6-r2.ebuild
index 19a75dee2db2..3421e90a261c 100644
--- a/dev-python/pyopengl/pyopengl-3.1.6-r2.ebuild
+++ b/dev-python/pyopengl/pyopengl-3.1.6-r2.ebuild
@@ -24,7 +24,7 @@ S="${WORKDIR}/PyOpenGL-${PV}"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux"
 IUSE="tk"
 
 RDEPEND="


             reply	other threads:[~2023-03-24 10:49 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 10:49 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-08 19:13 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyopengl/ Arthur Zamarin
2024-10-05 11:48 Arthur Zamarin
2024-10-05  9:06 Arthur Zamarin
2024-10-05  9:06 Arthur Zamarin
2024-10-05  8:30 Sam James
2024-08-25 18:38 Arthur Zamarin
2024-07-02 16:05 Michał Górny
2024-05-19 19:43 Arthur Zamarin
2024-01-05 12:56 Michał Górny
2023-12-20  8:29 Michał Górny
2023-12-20  2:34 Ionen Wolkens
2023-12-14  4:15 Sam James
2023-11-10 18:44 Michał Górny
2023-06-27 10:24 Sam James
2023-06-27  7:54 Sam James
2023-06-27  7:14 Sam James
2023-06-27  6:55 Sam James
2023-06-27  6:43 Sam James
2023-05-24  7:02 Michał Górny
2023-03-26 16:21 Michał Górny
2023-03-26 16:04 Arthur Zamarin
2023-03-26 16:04 Arthur Zamarin
2023-03-25  1:43 Sam James
2023-03-24 20:06 Arthur Zamarin
2023-03-24 14:19 Arthur Zamarin
2023-03-22  9:37 Sam James
2023-02-19 19:46 Michał Górny
2023-02-12 19:41 Michał Górny
2023-02-12 19:41 Michał Górny
2023-02-12 19:41 Michał Górny
2023-01-19  1:20 Sam James
2022-04-14  8:11 Agostino Sarubbo
2022-04-02 12:04 Arthur Zamarin
2022-04-02  7:33 Arthur Zamarin
2022-04-01 12:27 Arthur Zamarin
2022-04-01  5:15 Arthur Zamarin
2022-03-31 12:40 Jakov Smolić
2022-03-31 12:34 Jakov Smolić
2022-02-28  7:06 Yixun Lan
2022-02-20 14:03 Michał Górny
2021-10-04 14:22 Arthur Zamarin
2021-02-25  8:44 Michał Górny
2021-02-25  8:33 Sam James
2021-02-25  8:30 Sam James
2020-11-30 21:12 Sergei Trofimovich
2020-09-25 20:22 Michał Górny
2020-08-14 18:02 Sergei Trofimovich
2020-08-02  6:46 Michał Górny
2020-08-02  6:46 Michał Górny
2020-07-26  0:46 Sam James
2020-07-10  0:15 Sam James
2020-07-06 12:43 Michał Górny
2020-04-26  2:11 Patrick McLean
2020-04-23 21:24 James Le Cuirot
2019-05-27 23:41 Aaron Bauman
2017-06-27  9:16 Alexis Ballier
2017-05-03  9:26 Michał Górny
2017-04-26  6:24 Tim Harder
2017-02-24 18:01 Markus Meier
2017-01-25  9:27 Tobias Klausmann
2017-01-23 16:27 Agostino Sarubbo
2017-01-23  6:11 Jeroen Roovers
2017-01-22 16:27 Agostino Sarubbo
2017-01-21 20:33 Agostino Sarubbo
2017-01-20 11:05 Agostino Sarubbo
2017-01-19 10:59 Agostino Sarubbo
2017-01-18 16:52 Agostino Sarubbo
2016-03-28 22:58 Kacper Kowalik

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=1679654942.3c5bb88a4d457bd7118c76cbdf80d9f86bbaffbf.arthurzam@gentoo \
    --to=arthurzam@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