From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-rerunfailures/
Date: Wed, 29 Apr 2020 11:03:05 +0000 (UTC) [thread overview]
Message-ID: <1588158177.8a756304d861e3f190ac3ffd5d5e65ea7db67a4c.mgorny@gentoo> (raw)
commit: 8a756304d861e3f190ac3ffd5d5e65ea7db67a4c
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 29 10:54:06 2020 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Apr 29 11:02:57 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8a756304
dev-python/pytest-rerunfailures: Add missing mock py2-test-dep
Closes: https://bugs.gentoo.org/719996
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/pytest-rerunfailures/pytest-rerunfailures-8.0.ebuild | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/dev-python/pytest-rerunfailures/pytest-rerunfailures-8.0.ebuild b/dev-python/pytest-rerunfailures/pytest-rerunfailures-8.0.ebuild
index e93e988df37..a1904fda3ee 100644
--- a/dev-python/pytest-rerunfailures/pytest-rerunfailures-8.0.ebuild
+++ b/dev-python/pytest-rerunfailures/pytest-rerunfailures-8.0.ebuild
@@ -18,6 +18,9 @@ IUSE=""
RDEPEND="dev-python/setuptools[${PYTHON_USEDEP}]
>=dev-python/pytest-4.4[${PYTHON_USEDEP}]"
-BDEPEND="${RDEPEND}"
+BDEPEND="
+ test? (
+ $(python_gen_cond_dep 'dev-python/mock[${PYTHON_USEDEP}]' -2)
+ )"
distutils_enable_tests pytest
next reply other threads:[~2020-04-29 11:03 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 11:03 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-rerunfailures/ Michał Górny
2024-12-07 11:36 Michał Górny
2024-12-07 10:49 Arthur Zamarin
2024-11-20 11:13 Michał Górny
2024-05-09 17:08 Michał Górny
2024-05-09 17:08 Michał Górny
2024-03-30 14:59 Michał Górny
2024-03-30 14:53 Michał Górny
2024-03-14 11:44 Michał Górny
2023-12-09 13:56 Michał Górny
2023-12-09 13:52 Michał Górny
2023-11-23 4:19 Michał Górny
2023-08-11 19:08 Michał Górny
2023-08-11 19:02 Arthur Zamarin
2023-07-07 3:15 Michał Górny
2023-05-23 15:54 Michał Górny
2023-03-24 19:48 Michał Górny
2023-03-24 19:43 Arthur Zamarin
2023-03-09 17:00 Michał Górny
2023-02-17 18:51 Michał Górny
2023-02-16 20:28 Michał Górny
2023-02-16 17:22 Arthur Zamarin
2023-02-12 19:05 Michał Górny
2023-02-10 6:52 Michał Górny
2023-01-13 7:09 Michał Górny
2022-12-25 17:41 Michał Górny
2022-12-25 16:42 Sam James
2022-11-23 8:41 Michał Górny
2022-06-13 8:20 Michał Górny
2022-05-12 10:40 Michał Górny
2022-05-12 10:40 Michał Górny
2022-01-15 9:59 Michał Górny
2022-01-14 23:51 Matt Turner
2022-01-10 5:04 Joshua Kinard
2022-01-09 15:45 James Le Cuirot
2021-11-14 20:35 Sam James
2021-10-24 20:52 Michał Górny
2021-10-24 16:52 Agostino Sarubbo
2021-09-17 8:31 Michał Górny
2021-09-12 9:13 Sam James
2021-09-12 8:16 Sam James
2021-09-07 17:45 Sam James
2021-08-27 20:06 Sam James
2021-08-16 6:19 Michał Górny
2021-08-16 6:19 Michał Górny
2021-08-16 5:13 Agostino Sarubbo
2021-08-11 0:20 Sam James
2021-08-04 21:12 Marek Szuba
2021-07-05 7:03 Michał Górny
2021-07-02 21:02 Michał Górny
2021-05-26 20:39 Michał Górny
2021-05-22 18:18 Michał Górny
2021-05-22 18:18 Michał Górny
2021-05-22 18:18 Michał Górny
2020-11-18 9:12 Michał Górny
2020-11-14 22:13 Michał Górny
2020-10-09 23:08 Patrick McLean
2020-09-21 16:06 Michał Górny
2020-08-02 9:15 Michał Górny
2020-07-29 18:18 Sam James
2020-04-28 15:41 Mikle Kolyada
2020-03-28 18:49 Michał Górny
2019-12-03 2:19 Patrick McLean
2019-11-19 18:36 Matthew Thode
2019-06-29 6:44 Zac Medico
2019-05-10 17:47 Patrick McLean
2019-04-28 8:15 Maxim Koltsov
2018-07-21 0:08 Mikle Kolyada
2018-07-01 15:19 Pacho Ramos
2017-04-28 16:22 Manuel Rüger
2017-01-30 19:47 Sebastien Fabbro
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=1588158177.8a756304d861e3f190ac3ffd5d5e65ea7db67a4c.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