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/pytest-shell-utilities/
Date: Sat, 14 Sep 2024 12:33:33 +0000 (UTC)	[thread overview]
Message-ID: <1726317209.3c851ed425e4ca7ae2f6992d32fd687b9d0336d3.arthurzam@gentoo> (raw)

commit:     3c851ed425e4ca7ae2f6992d32fd687b9d0336d3
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 14 12:33:29 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Sep 14 12:33:29 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c851ed4

dev-python/pytest-shell-utilities: Stabilize 1.9.3 ALLARCHES, #939614

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

 dev-python/pytest-shell-utilities/pytest-shell-utilities-1.9.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pytest-shell-utilities/pytest-shell-utilities-1.9.3.ebuild b/dev-python/pytest-shell-utilities/pytest-shell-utilities-1.9.3.ebuild
index 6a16f052360e..94538dbf4c7e 100644
--- a/dev-python/pytest-shell-utilities/pytest-shell-utilities-1.9.3.ebuild
+++ b/dev-python/pytest-shell-utilities/pytest-shell-utilities-1.9.3.ebuild
@@ -20,7 +20,7 @@ SRC_URI="
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm arm64 ~riscv x86"
 
 RDEPEND="
 	>=dev-python/attrs-22.1.0[${PYTHON_USEDEP}]


             reply	other threads:[~2024-09-14 12:33 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14 12:33 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-02  8:59 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-shell-utilities/ Michał Górny
2024-11-02  8:49 Michał Górny
2024-10-23  6:16 Michał Górny
2024-10-19  6:03 Michał Górny
2024-10-18  4:29 Michał Górny
2024-09-14 12:40 Michał Górny
2024-08-27  7:39 Michał Górny
2024-07-11 18:37 Michał Górny
2024-03-09 14:19 Michał Górny
2024-03-09 14:19 Michał Górny
2024-03-09 11:03 Jakov Smolić
2024-02-24  8:49 Michał Górny
2023-11-24 17:04 Arthur Zamarin
2023-11-06 17:05 Michał Górny
2023-08-03 17:40 Michał Górny
2023-08-03 15:10 Sam James
2023-08-03 15:10 Sam James
2023-07-03  4:15 Michał Górny
2023-07-03  4:15 Michał Górny
2022-11-04  8:38 Michał Górny
2022-11-04  8:16 Agostino Sarubbo
2022-11-03 22:04 Sam James
2022-09-23 20:07 Arthur Zamarin
2022-08-30 19:01 Michał Górny
2022-08-30 17:08 Jakov Smolić
2022-08-30 17:08 Jakov Smolić
2022-07-29 10:12 Arthur Zamarin
2022-07-29 10:12 Arthur Zamarin
2022-06-16 11:47 Michał Górny
2022-06-16  9:41 Jakov Smolić
2022-06-16  9:37 Jakov Smolić
2022-06-05  5:46 Michał Górny
2022-06-03  5:37 Michał Górny
2022-05-30 13:51 Jakov Smolić
2022-05-27  6:10 Michał Górny
2022-05-26 18:54 Michał Górny
2022-05-24  6:16 Michał Górny
2022-05-21  6:47 Michał Górny
2022-05-17  6:54 Michał Górny
2022-05-06 19:59 Arthur Zamarin
2022-05-06 19:58 Arthur Zamarin
2022-04-16  8:43 Jakov Smolić
2022-04-02  8:45 Arthur Zamarin
2022-04-02  8:28 Arthur Zamarin
2022-03-31  1:28 Patrick McLean
2022-02-25 12:49 Arthur Zamarin
2022-02-25 11:24 Arthur Zamarin

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=1726317209.3c851ed425e4ca7ae2f6992d32fd687b9d0336d3.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