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/pyudev/
Date: Thu,  1 Jun 2023 17:22:58 +0000 (UTC)	[thread overview]
Message-ID: <1685640172.7bfdb76b50b96df258ea8938ca51889cf3314ab7.arthurzam@gentoo> (raw)

commit:     7bfdb76b50b96df258ea8938ca51889cf3314ab7
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun  1 17:22:52 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu Jun  1 17:22:52 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7bfdb76b

dev-python/pyudev: Stabilize 0.24.1 ppc64, #907646

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

 dev-python/pyudev/pyudev-0.24.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pyudev/pyudev-0.24.1.ebuild b/dev-python/pyudev/pyudev-0.24.1.ebuild
index c94b0f70659f..de6ec4ca269a 100644
--- a/dev-python/pyudev/pyudev-0.24.1.ebuild
+++ b/dev-python/pyudev/pyudev-0.24.1.ebuild
@@ -12,7 +12,7 @@ HOMEPAGE="https://pyudev.readthedocs.io/en/latest/ https://github.com/pyudev/pyu
 
 LICENSE="LGPL-2.1"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 arm ~arm64 ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~ia64 ~loong ~mips ~ppc ppc64 ~riscv ~sparc ~x86"
 IUSE="qt5"
 
 # Known to fail on test system that aren't exactly the same devices as on CI


             reply	other threads:[~2023-06-01 17:23 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 17:22 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-11 15:29 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyudev/ Patrick McLean
2023-06-04  4:58 Michał Górny
2023-06-03 19:45 Arthur Zamarin
2023-06-01 20:12 Sam James
2023-06-01 20:05 Sam James
2023-06-01 20:04 Sam James
2023-06-01 20:04 Sam James
2023-06-01 17:19 Arthur Zamarin
2023-04-29  5:58 Arthur Zamarin
2023-03-16  4:07 Michał Górny
2022-11-07 17:27 Arthur Zamarin
2022-10-07  8:47 WANG Xuerui
2022-09-26  6:15 Michał Górny
2022-09-25 23:58 Sam James
2022-09-25 23:58 Sam James
2022-09-25 18:43 Arthur Zamarin
2022-09-25 18:39 Arthur Zamarin
2022-09-25 18:24 Arthur Zamarin
2022-09-25 18:10 Arthur Zamarin
2022-08-25 19:25 Arthur Zamarin
2022-08-25 19:25 Arthur Zamarin
2022-08-25 10:43 Marek Szuba
2022-03-18 11:41 Michał Górny
2022-03-18  9:43 Arthur Zamarin
2022-03-17  7:45 Agostino Sarubbo
2022-03-16 23:53 Sam James
2022-03-15 18:23 Jakov Smolić
2022-02-11 21:18 Michał Górny
2022-02-11 19:22 Arthur Zamarin
2022-02-10 11:43 Sam James
2022-02-06  8:05 Agostino Sarubbo
2022-02-06  8:04 Agostino Sarubbo
2022-02-06  7:35 Sam James
2022-02-05 21:09 Jakov Smolić
2022-02-05  9:11 Arthur Zamarin
2022-02-05  9:11 Arthur Zamarin
2022-02-05  9:11 Arthur Zamarin
2021-05-27 19:23 Sam James
2021-05-27 19:18 Sam James
2021-02-28 22:11 Sergei Trofimovich
2021-02-28 20:39 Sergei Trofimovich
2021-01-13 19:28 Sergei Trofimovich
2021-01-03 20:11 Matt Turner
2021-01-03 11:39 Sergei Trofimovich
2020-11-25  8:37 Michał Górny
2020-02-05 23:28 Patrick McLean
2020-02-05 21:21 Michał Górny
2019-04-10 22:44 Matthew Thode
2018-06-25 23:20 Thomas Deutschmann
2018-05-10  8:25 Andreas Sturmlechner
2018-05-10  8:25 Andreas Sturmlechner
2018-05-10  8:25 Andreas Sturmlechner
2018-04-29  6:33 Michał Górny
2018-04-02  6:23 Matt Turner
2018-01-23  5:58 Markus Meier
2017-12-19  8:32 Jason Zaman
2017-11-27 19:26 Andreas Sturmlechner
2017-08-10 16:53 Michał Górny
2017-04-27 11:13 Tim Harder
2017-03-01 13:05 Michael Weber
2017-01-19 10:59 Agostino Sarubbo
2017-01-18 16:52 Agostino Sarubbo
2016-09-04 17:04 Manuel Rüger
2016-05-31 21:34 Patrick McLean
2016-02-28  6:12 Matt Thode

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=1685640172.7bfdb76b50b96df258ea8938ca51889cf3314ab7.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