From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/future/
Date: Wed, 12 Feb 2020 07:55:09 +0000 (UTC) [thread overview]
Message-ID: <1581494107.350651f39cefdf635219d9d8eec6bb0a4ed8c18f.ago@gentoo> (raw)
commit: 350651f39cefdf635219d9d8eec6bb0a4ed8c18f
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 12 07:55:07 2020 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Feb 12 07:55:07 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=350651f3
dev-python/future: sparc stable wrt bug #704270
Package-Manager: Portage-2.3.84, Repoman-2.3.20
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-python/future/future-0.18.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/future/future-0.18.2.ebuild b/dev-python/future/future-0.18.2.ebuild
index 7bb1df4ac66..db4fd6cbff3 100644
--- a/dev-python/future/future-0.18.2.ebuild
+++ b/dev-python/future/future-0.18.2.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ppc64 ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ppc64 ~s390 sparc ~x86 ~amd64-linux ~x86-linux"
IUSE="doc"
distutils_enable_tests pytest
next reply other threads:[~2020-02-12 7:55 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 7:55 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-27 6:34 [gentoo-commits] repo/gentoo:master commit in: dev-python/future/ Sam James
2023-05-27 11:14 Sam James
2023-05-27 10:47 Sam James
2023-03-16 3:50 Michał Górny
2022-08-18 6:18 Michał Górny
2022-08-17 19:31 Arthur Zamarin
2022-07-15 13:45 Arthur Zamarin
2022-06-19 18:08 Arthur Zamarin
2021-08-20 7:44 Arthur Zamarin
2021-08-20 7:44 Arthur Zamarin
2021-06-10 7:32 Michał Górny
2020-09-20 15:38 Michał Górny
2020-04-29 4:10 Mike Gilbert
2020-04-29 4:10 Mike Gilbert
2020-03-07 15:23 Michał Górny
2020-03-07 15:23 Michał Górny
2020-03-07 15:11 Michał Górny
2020-02-16 13:51 Sergei Trofimovich
2020-02-12 16:14 Agostino Sarubbo
2020-02-12 7:57 Agostino Sarubbo
2020-02-12 7:53 Agostino Sarubbo
2020-02-12 7:51 Agostino Sarubbo
2020-02-12 7:47 Agostino Sarubbo
2020-02-12 7:46 Agostino Sarubbo
2020-02-12 7:45 Agostino Sarubbo
2019-11-25 12:35 Michał Górny
2019-11-16 11:20 Michał Górny
2019-11-15 22:55 Michał Górny
2019-11-15 17:27 Michał Górny
2019-11-15 17:27 Michał Górny
2019-08-05 9:12 Patrice Clement
2019-05-01 18:06 Matt Turner
2019-04-28 20:40 Mikle Kolyada
2019-04-05 9:24 Mart Raudsepp
2019-03-16 18:40 Sergei Trofimovich
2019-03-16 14:46 Mikle Kolyada
2019-03-09 21:19 Matt Turner
2019-03-09 19:18 Thomas Deutschmann
2019-03-05 6:22 Matt Turner
2019-03-05 6:22 Matt Turner
2019-03-03 6:29 Mikle Kolyada
2019-03-02 21:30 Matt Turner
2019-03-02 20:02 Matt Turner
2019-02-15 17:05 Mikle Kolyada
2019-02-11 0:41 Matt Turner
2018-11-01 0:10 Sergei Trofimovich
2018-10-17 12:11 Tobias Klausmann
2018-08-30 17:50 Matt Thode
2018-08-21 17:07 Patrice Clement
2018-07-25 7:07 Matt Thode
2018-03-17 22:14 Matt Turner
2018-03-17 22:14 Matt Turner
2018-03-02 15:59 Tobias Klausmann
2018-01-06 19:55 Sergei Trofimovich
2017-12-02 20:55 Mike Gilbert
2017-11-30 19:02 Thomas Deutschmann
2017-11-26 20:51 Jeroen Roovers
2017-11-06 21:20 Sergei Trofimovich
2017-10-24 13:15 Jeroen Roovers
2017-09-10 14:03 Sergei Trofimovich
2017-08-13 16:29 Sergei Trofimovich
2017-07-23 11:45 Manuel Rüger
2017-06-23 6:00 Alexis Ballier
2017-04-04 23:06 Brian Dolbec
2016-11-14 14:02 Alexis Ballier
2016-11-01 23:55 Manuel Rüger
2016-09-28 8:47 Tobias Klausmann
2016-09-04 15:56 Mike Gilbert
2016-08-09 23:52 Brian Dolbec
2016-03-16 23:06 Manuel Rüger
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=1581494107.350651f39cefdf635219d9d8eec6bb0a4ed8c18f.ago@gentoo \
--to=ago@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