From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-regressions/
Date: Mon, 18 Jan 2021 16:53:23 +0000 (UTC) [thread overview]
Message-ID: <1610988796.6dd2a6e2f899b5dac1d7260e74f7c07ab4b1d4ae.sam@gentoo> (raw)
commit: 6dd2a6e2f899b5dac1d7260e74f7c07ab4b1d4ae
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 18 16:53:16 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jan 18 16:53:16 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6dd2a6e2
dev-python/pytest-regressions: Stabilize 2.1.1 ALLARCHES, #765967
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/pytest-regressions/pytest-regressions-2.1.1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-python/pytest-regressions/pytest-regressions-2.1.1.ebuild b/dev-python/pytest-regressions/pytest-regressions-2.1.1.ebuild
index a0b17c024ef..079a26b29ee 100644
--- a/dev-python/pytest-regressions/pytest-regressions-2.1.1.ebuild
+++ b/dev-python/pytest-regressions/pytest-regressions-2.1.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 x86"
BDEPEND="test? (
dev-python/matplotlib[${PYTHON_USEDEP}]
next reply other threads:[~2021-01-18 16:53 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 16:53 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-20 11:44 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-regressions/ Arthur Zamarin
2025-09-06 7:01 Michał Górny
2025-08-13 19:31 Michał Górny
2025-07-26 10:25 Michał Górny
2025-07-26 10:18 Michał Górny
2025-07-12 5:05 Michał Górny
2025-07-05 6:11 Michał Górny
2025-07-05 4:44 Michał Górny
2025-06-14 13:54 Sam James
2025-05-31 5:17 Michał Górny
2025-05-11 20:37 Sam James
2025-02-16 16:02 Michał Górny
2025-01-25 10:01 Michał Górny
2025-01-25 9:20 Arthur Zamarin
2025-01-10 20:43 Michał Górny
2025-01-04 12:29 Michał Górny
2025-01-04 11:44 Sam James
2024-12-18 7:27 Michał Górny
2024-05-11 11:05 Michał Górny
2023-10-06 15:08 Michał Górny
2023-10-06 14:31 Sam James
2023-09-01 5:06 Michał Górny
2023-08-31 13:22 Michał Górny
2023-05-29 12:49 Michał Górny
2023-05-29 12:49 Michał Górny
2023-04-09 20:40 Andrew Ammerlaan
2023-03-19 17:36 Arthur Zamarin
2023-03-17 15:23 Michał Górny
2023-02-16 20:58 Arthur Zamarin
2023-01-25 16:10 WANG Xuerui
2023-01-14 4:57 Michał Górny
2022-10-22 15:58 Michał Górny
2022-10-22 15:50 Arthur Zamarin
2022-09-19 19:02 Arthur Zamarin
2022-06-24 15:46 Michał Górny
2022-05-17 12:20 Andrew Ammerlaan
2022-05-07 20:00 Michał Górny
2022-03-12 11:17 Arthur Zamarin
2022-03-01 11:30 Agostino Sarubbo
2022-02-28 10:13 Michał Górny
2022-02-28 10:13 Michał Górny
2022-02-28 10:13 Michał Górny
2022-02-28 8:35 Michał Górny
2022-02-13 13:00 Michał Górny
2022-02-13 10:38 Agostino Sarubbo
2022-02-07 11:36 Sam James
2022-01-19 22:59 Michał Górny
2022-01-04 21:46 Arthur Zamarin
2021-11-20 6:35 Sam James
2021-11-19 8:37 Arthur Zamarin
2021-11-19 7:59 Arthur Zamarin
2021-09-27 10:14 James Le Cuirot
2021-09-07 5:30 Sam James
2021-09-07 2:47 Sam James
2021-09-06 21:26 Sam James
2021-08-04 21:57 Marek Szuba
2021-07-25 3:23 Sam James
2021-07-23 14:08 Andrew Ammerlaan
2021-03-02 9:00 Michał Górny
2021-03-02 7:38 Sam James
2021-01-28 8:35 Michał Górny
2021-01-28 8:35 Michał Górny
2021-01-18 18:48 Michał Górny
2020-12-17 0:18 Matt Turner
2020-12-17 0:18 Matt Turner
2020-12-06 9:53 Joonas Niilola
2020-12-06 9:14 Michał Górny
2020-12-05 9:58 Michał Górny
2020-11-05 1:39 Matt Turner
2020-10-17 16:41 Joonas Niilola
2020-10-17 16:41 Joonas Niilola
2020-09-21 16:06 Michał Górny
2020-09-15 8:09 Joonas Niilola
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=1610988796.6dd2a6e2f899b5dac1d7260e74f7c07ab4b1d4ae.sam@gentoo \
--to=sam@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