From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/six/
Date: Mon, 2 Nov 2015 11:50:44 +0000 (UTC) [thread overview]
Message-ID: <1446464832.c0b4061d1ac772e47b97f8bcea404d9f69144d97.jlec@gentoo> (raw)
commit: c0b4061d1ac772e47b97f8bcea404d9f69144d97
Author: Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 1 18:09:57 2015 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Mon Nov 2 11:47:12 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c0b4061d
dev-python/six: Restrict failing tests
Package-Manager: portage-2.2.23
Signed-off-by: Justin Lecher <jlec <AT> gentoo.org>
dev-python/six/six-1.10.0.ebuild | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/dev-python/six/six-1.10.0.ebuild b/dev-python/six/six-1.10.0.ebuild
index 465102a..943c0f6 100644
--- a/dev-python/six/six-1.10.0.ebuild
+++ b/dev-python/six/six-1.10.0.ebuild
@@ -26,6 +26,16 @@ PATCHES=(
"${FILESDIR}"/1.9.0-mapping.patch
)
+python_prepare_all() {
+ # https://bitbucket.org/gutworth/six/issues/139/
+ sed \
+ -e 's:test_assertCountEqual:_&:g' \
+ -e 's:test_assertRegex:_&:g' \
+ -e 's:test_assertRaisesRegex:_&:g' \
+ -i test_six.py || die
+ distutils-r1_python_prepare_all
+}
+
python_compile_all() {
use doc && emake -C documentation html
}
next reply other threads:[~2015-11-02 11:50 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 11:50 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-21 11:34 [gentoo-commits] repo/gentoo:master commit in: dev-python/six/ Michał Górny
2024-12-21 11:31 Michał Górny
2024-12-05 5:39 Michał Górny
2024-10-14 12:42 Michał Górny
2024-05-08 18:31 Michał Górny
2023-05-23 15:42 Michał Górny
2022-06-10 4:18 Michał Górny
2022-06-10 3:09 Sam James
2022-05-09 20:38 Michał Górny
2022-05-09 15:01 Michał Górny
2021-06-05 21:20 Michał Górny
2021-06-05 20:35 Sam James
2021-05-06 8:21 Michał Górny
2021-05-05 17:05 Michał Górny
2021-05-05 17:05 Michał Górny
2021-01-06 22:30 Fabian Groffen
2020-09-26 15:50 Michał Górny
2020-09-26 15:50 Michał Górny
2020-09-26 15:50 Michał Górny
2020-09-20 14:56 Michał Górny
2020-07-16 18:01 Sam James
2020-07-16 18:01 Sam James
2020-07-09 8:41 Agostino Sarubbo
2020-07-09 8:16 Agostino Sarubbo
2020-05-25 16:16 Michał Górny
2020-05-22 4:46 Michał Górny
2020-05-14 11:57 Michał Górny
2020-03-29 8:19 Michał Górny
2020-03-29 8:19 Michał Górny
2020-03-25 15:27 Agostino Sarubbo
2020-03-25 14:52 Agostino Sarubbo
2020-03-25 13:27 Agostino Sarubbo
2020-03-25 13:12 Agostino Sarubbo
2020-03-25 12:36 Agostino Sarubbo
2020-03-25 12:23 Agostino Sarubbo
2020-01-16 4:39 Michał Górny
2019-11-16 11:02 Michał Górny
2019-11-06 7:26 Michał Górny
2018-12-10 13:19 Michał Górny
2018-01-11 19:43 Mike Frysinger
2017-10-01 11:39 Tim Harder
2017-10-01 11:39 Tim Harder
2017-03-16 8:16 Michael Weber
2017-03-09 15:54 Michael Haubenwallner
2017-01-31 4:44 Mike Gilbert
2017-01-29 17:28 Fabian Groffen
2016-10-03 15:33 Mike Gilbert
2016-09-24 22:39 Mike Gilbert
2016-09-23 20:15 Tim Harder
2016-06-09 16:18 Mike Gilbert
2016-03-11 2:33 Mike Gilbert
2016-01-27 14:11 Mike Gilbert
2016-01-27 4:17 Mike Gilbert
2016-01-26 20:10 Mike Gilbert
2016-01-26 19:09 Justin Lecher
2015-12-28 16:28 Mike Gilbert
2015-12-08 16:33 Mike Gilbert
2015-12-07 18:15 Mike Gilbert
2015-12-07 16:56 Mike Gilbert
2015-12-07 15:48 Mike Gilbert
2015-11-30 7:24 Justin Lecher
2015-11-22 8:38 Markus Meier
2015-11-22 5:38 Jeroen Roovers
2015-11-20 11:29 Justin Lecher
2015-11-19 10:25 Agostino Sarubbo
2015-11-16 15:01 Agostino Sarubbo
2015-11-05 11:52 Agostino Sarubbo
2015-11-04 16:09 Agostino Sarubbo
2015-11-04 15:50 Agostino Sarubbo
2015-11-02 13:12 Agostino Sarubbo
2015-11-02 13:09 Agostino Sarubbo
2015-10-11 11:25 Justin Lecher
2015-10-11 8:58 Dirkjan Ochtman
2015-10-11 7:05 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=1446464832.c0b4061d1ac772e47b97f8bcea404d9f69144d97.jlec@gentoo \
--to=jlec@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