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/flaky/
Date: Fri,  3 Mar 2023 17:37:13 +0000 (UTC)	[thread overview]
Message-ID: <1677865022.680b65c33f64a3483bf6f8a8a613de6cb45f0503.arthurzam@gentoo> (raw)

commit:     680b65c33f64a3483bf6f8a8a613de6cb45f0503
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar  3 17:37:02 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Mar  3 17:37:02 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=680b65c3

dev-python/flaky: Stabilize 3.7.0-r4 ALLARCHES, #899108

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

 dev-python/flaky/flaky-3.7.0-r4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/flaky/flaky-3.7.0-r4.ebuild b/dev-python/flaky/flaky-3.7.0-r4.ebuild
index b80e2f72f774..0c6362329466 100644
--- a/dev-python/flaky/flaky-3.7.0-r4.ebuild
+++ b/dev-python/flaky/flaky-3.7.0-r4.ebuild
@@ -17,7 +17,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 SLOT="0"
 LICENSE="Apache-2.0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2023-03-03 17:37 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 17:37 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-09 13:12 [gentoo-commits] repo/gentoo:master commit in: dev-python/flaky/ Michał Górny
2024-05-09 13:12 Michał Górny
2024-03-30 14:14 Michał Górny
2024-03-30 13:59 Michał Górny
2024-03-13  6:51 Michał Górny
2024-03-11  4:10 Michał Górny
2024-03-05  5:18 Michał Górny
2023-05-23 15:42 Michał Górny
2023-03-03 17:48 Michał Górny
2023-03-03 17:48 Michał Górny
2023-02-01 13:18 Michał Górny
2022-12-25  9:43 Michał Górny
2022-06-10  6:54 Michał Górny
2022-06-10  3:09 Sam James
2022-05-10 10:07 Michał Górny
2022-05-10 10:07 Michał Górny
2021-05-06 18:45 Michał Górny
2020-11-28 15:26 Sam James
2020-10-16 18:22 Michał Górny
2020-09-20 15:38 Michał Górny
2020-09-18 14:48 Michał Górny
2020-09-08 22:46 Sam James
2020-09-08 19:11 Michał Górny
2020-07-10  6:30 Michał Górny
2020-05-25 19:48 Michał Górny
2020-01-26 17:21 Michał Górny
2019-12-24 14:21 Mikle Kolyada
2019-12-19 18:35 Sergei Trofimovich
2019-12-15 13:53 Agostino Sarubbo
2019-12-15 13:36 Sergei Trofimovich
2019-12-15 13:24 Sergei Trofimovich
2019-12-15 11:38 Agostino Sarubbo
2019-12-02 21:13 Aaron Bauman
2019-11-15 23:51 Michał Górny
2019-11-15 23:51 Michał Górny
2019-04-09  1:32 Aaron Bauman
2019-02-27  4:39 Aaron Bauman
2018-11-19 21:15 Fabian Groffen
2018-08-18  3:03 Mikle Kolyada
2018-02-21 22:11 Michał Górny
2017-10-08 16:53 Tim Harder
2017-08-02  4:06 Sebastien Fabbro
2017-08-01 20:06 Michał Górny
2017-05-02 11:58 Michał Górny
2017-01-21 11:48 Jeroen Roovers
2016-12-06 19:35 Markus Meier
2016-11-27 15:09 Tobias Klausmann
2016-11-27 13:51 Tobias Klausmann
2016-11-25 18:54 Agostino Sarubbo
2016-11-25 18:27 Agostino Sarubbo
2016-07-18  9:56 Patrick Lauer
2016-02-18 18:14 Patrick Lauer
2016-01-20  8:20 Justin Lecher
2016-01-07  8:56 Justin Lecher
2015-11-06 10:44 Justin Lecher
2015-11-04 14:15 Justin Lecher
2015-11-04 14:15 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=1677865022.680b65c33f64a3483bf6f8a8a613de6cb45f0503.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