From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/sure/
Date: Thu, 17 Dec 2015 16:28:21 +0000 (UTC) [thread overview]
Message-ID: <1450369694.378ccfd5dad89a85441c70e5af4d9fa8c652e8ac.jlec@gentoo> (raw)
commit: 378ccfd5dad89a85441c70e5af4d9fa8c652e8ac
Author: Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 17 16:12:40 2015 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Thu Dec 17 16:28:14 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=378ccfd5
dev-python/sure: Add python3.5 support and fix QA issues
Package-Manager: portage-2.2.26
Signed-off-by: Justin Lecher <jlec <AT> gentoo.org>
dev-python/sure/sure-1.2.5-r1.ebuild | 16 ++++++----------
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/dev-python/sure/sure-1.2.5-r1.ebuild b/dev-python/sure/sure-1.2.5-r1.ebuild
index 177d280..dbb9ff4 100644
--- a/dev-python/sure/sure-1.2.5-r1.ebuild
+++ b/dev-python/sure/sure-1.2.5-r1.ebuild
@@ -3,16 +3,15 @@
# $Id$
EAPI=5
-PYTHON_COMPAT=( python2_7 python3_{3,4} pypy )
+
+PYTHON_COMPAT=( python2_7 python3_{3,4,5} pypy )
inherit distutils-r1 vcs-snapshot
-DESCRIPTION="utility belt for automated testing in python for python"
+DESCRIPTION="Utility belt for automated testing in python for python"
HOMEPAGE="https://github.com/gabrielfalcao/sure"
SRC_URI="https://github.com/gabrielfalcao/${PN}/archive/${PV}.tar.gz -> ${P}-r1.tar.gz"
-S="${WORKDIR}/${P}-r1"
-
LICENSE="GPL-3"
SLOT="0"
KEYWORDS="amd64 x86"
@@ -28,15 +27,12 @@ DEPEND="
"
RDEPEND="${CDEPEND}"
+S="${WORKDIR}/${P}-r1"
+
python_prepare_all() {
- ebegin 'patching setup.py'
sed \
-e "82s/read_version()/'${PV}'/" \
- -i setup.py
- STATUS=$?
- eend ${STATUS}
- [[ ${STATUS} -gt 0 ]] && die
-
+ -i setup.py || die
distutils-r1_python_prepare_all
}
next reply other threads:[~2015-12-17 16:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 16:28 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-20 16:35 [gentoo-commits] repo/gentoo:master commit in: dev-python/sure/ Justin Lecher
2017-04-22 13:52 Michał Górny
2017-06-19 18:12 Alexis Ballier
2017-12-02 20:55 Mike Gilbert
2018-02-13 19:28 Matt Thode
2019-06-18 7:07 Michał Górny
2019-06-18 7:07 Michał Górny
2019-07-28 6:41 Michał Górny
2019-09-13 0:00 Thomas Deutschmann
2019-09-13 6:36 Agostino Sarubbo
2019-09-13 12:03 Agostino Sarubbo
2019-12-29 20:48 Michał Górny
2019-12-29 20:48 Michał Górny
2020-02-11 7:39 Michał Górny
2020-05-28 19:39 Michał Górny
2020-07-16 2:02 Sam James
2020-07-16 19:34 Sam James
2020-07-17 0:17 Sam James
2020-07-19 13:37 Sergei Trofimovich
2020-08-02 9:33 Michał Górny
2020-08-18 11:18 Agostino Sarubbo
2020-08-29 23:22 Sam James
2020-09-01 4:22 Sam James
2021-06-22 5:54 Michał Górny
2021-07-24 9:04 Michał Górny
2021-07-25 1:04 Sam James
2021-07-25 8:41 Michał Górny
2021-09-19 15:37 Arthur Zamarin
2022-05-14 8:25 Michał Górny
2022-05-14 8:25 Michał Górny
2022-06-16 9:06 Jakov Smolić
2022-06-16 9:23 Michał Górny
2023-02-06 17:07 Michał Górny
2023-03-11 8:10 Arthur Zamarin
2023-03-11 9:39 Michał Górny
2023-03-11 9:39 Michał Górny
2023-05-27 19:21 Arthur Zamarin
2024-05-18 9:41 Michał Górny
2025-01-14 6:05 WANG Xuerui
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=1450369694.378ccfd5dad89a85441c70e5af4d9fa8c652e8ac.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