public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-timeout/
Date: Sat, 23 Mar 2024 10:41:08 +0000 (UTC)	[thread overview]
Message-ID: <1711190458.61428e2dd73acc4c5591171a86e11a6ddc0c1a3a.mgorny@gentoo> (raw)

commit:     61428e2dd73acc4c5591171a86e11a6ddc0c1a3a
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 23 10:40:58 2024 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sat Mar 23 10:40:58 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=61428e2d

dev-python/pytest-timeout: Stabilize 2.3.1 ALLARCHES, #927613

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/pytest-timeout/pytest-timeout-2.3.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pytest-timeout/pytest-timeout-2.3.1.ebuild b/dev-python/pytest-timeout/pytest-timeout-2.3.1.ebuild
index ea860f7df388..2d48986cbf02 100644
--- a/dev-python/pytest-timeout/pytest-timeout-2.3.1.ebuild
+++ b/dev-python/pytest-timeout/pytest-timeout-2.3.1.ebuild
@@ -17,7 +17,7 @@ HOMEPAGE="
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux"
 
 # do not rdepend on pytest, it won't be used without it anyway
 # pytest-cov used to test compatibility


             reply	other threads:[~2024-03-23 10:41 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23 10:41 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-15 11:30 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-timeout/ Michał Górny
2024-05-09 16:48 Michał Górny
2024-03-23 10:45 Michał Górny
2024-03-08  5:40 Michał Górny
2023-11-11 20:36 Michał Górny
2023-11-11 19:21 Sam James
2023-10-10  7:13 Michał Górny
2023-10-10  7:13 Michał Górny
2023-10-08 17:48 Michał Górny
2023-05-23 18:36 Arthur Zamarin
2023-03-17 15:23 Michał Górny
2022-05-09 20:38 Michał Górny
2022-02-27 18:46 Michał Górny
2022-01-18 22:44 Michał Górny
2022-01-13 21:53 Michał Górny
2022-01-13 19:29 Arthur Zamarin
2021-12-14 10:21 Michał Górny
2021-11-13  9:26 Arthur Zamarin
2021-10-11  7:56 Michał Górny
2021-09-21 21:37 James Le Cuirot
2021-05-24  2:39 Joshua Kinard
2021-05-19 18:32 Michał Górny
2020-11-18  8:47 Michał Górny
2020-10-22 21:06 Michał Górny
2020-10-22  7:18 Sam James
2020-09-21 16:06 Michał Górny
2020-09-20 14:30 Michał Górny
2020-08-01 21:48 Michał Górny
2020-07-17  5:56 Michał Górny
2020-07-11  8:06 Michał Górny
2020-07-11  7:51 Michał Górny
2020-07-09  8:59 Agostino Sarubbo
2020-07-08  8:26 Michał Górny
2020-06-16  8:18 Michał Górny
2020-06-15  7:23 Michał Górny
2020-06-11 21:48 Sergei Trofimovich
2020-05-28 18:20 Sergei Trofimovich
2020-05-26 10:35 Michał Górny
2020-05-06 16:43 Mikle Kolyada
2020-05-05 22:13 Sergei Trofimovich
2020-04-29 11:03 Michał Górny
2020-04-18 14:25 Michał Górny
2020-04-08 14:01 Agostino Sarubbo
2020-04-07  7:03 Georgy Yakovlev
2020-03-28 18:49 Michał Górny
2020-03-16  5:54 Matt Turner
2020-03-14 16:33 Michał Górny
2020-03-08 10:46 Agostino Sarubbo
2020-03-08 10:37 Agostino Sarubbo
2020-03-08 10:25 Agostino Sarubbo
2020-02-06 21:11 Sergei Trofimovich
2019-12-04 19:44 Sergei Trofimovich
2019-12-02 21:13 Aaron Bauman
2019-04-28  8:15 Maxim Koltsov
2017-12-05  4:53 Tim Harder
2017-05-03  7:37 Michał Górny
2017-03-22 19:48 Markus Meier
2017-02-13  9:03 Zac Medico
2017-01-21 18:54 Agostino Sarubbo
2017-01-21 17:27 Agostino Sarubbo
2016-11-30 14:45 Lars Wendler
2016-06-29 18:49 Patrick Lauer
2015-10-15  9:21 Justin Lecher

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=1711190458.61428e2dd73acc4c5591171a86e11a6ddc0c1a3a.mgorny@gentoo \
    --to=mgorny@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