From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/constantly/
Date: Wed, 13 Dec 2017 22:15:44 +0000 (UTC) [thread overview]
Message-ID: <1513203337.9f2768c046eaf746f84c408f15d327339f99eab5.slyfox@gentoo> (raw)
commit: 9f2768c046eaf746f84c408f15d327339f99eab5
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 13 22:14:34 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Dec 13 22:15:37 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9f2768c0
dev-python/constantly: keyworded 15.1.0 for sparc, bug #605122 (thanks to Rolf Eike Beer)
Package-Manager: Portage-2.3.16, Repoman-2.3.6
RepoMan-Options: --include-arches="sparc"
dev-python/constantly/constantly-15.1.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/constantly/constantly-15.1.0.ebuild b/dev-python/constantly/constantly-15.1.0.ebuild
index b9a97401708..0b2342f69bb 100644
--- a/dev-python/constantly/constantly-15.1.0.ebuild
+++ b/dev-python/constantly/constantly-15.1.0.ebuild
@@ -12,7 +12,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 x86"
+KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ppc64 ~sparc x86"
IUSE=""
RDEPEND=""
next reply other threads:[~2017-12-13 22:15 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 22:15 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-16 18:31 [gentoo-commits] repo/gentoo:master commit in: dev-python/constantly/ Arthur Zamarin
2025-04-12 18:54 Michał Górny
2025-02-18 12:50 Michał Górny
2024-06-28 7:47 Petr Vaněk
2024-06-05 5:38 Michał Górny
2023-11-29 10:10 Michał Górny
2023-11-29 10:07 Michał Górny
2023-10-29 4:46 Michał Górny
2023-07-05 8:03 Michał Górny
2023-07-05 5:56 Arthur Zamarin
2023-05-29 9:31 Michał Górny
2023-05-28 18:11 Sam James
2022-05-13 9:08 Michał Górny
2022-03-15 11:18 Michał Górny
2022-03-15 11:08 Jakov Smolić
2022-02-02 9:27 Michał Górny
2022-02-02 9:27 Michał Górny
2022-01-27 22:56 James Le Cuirot
2021-06-01 20:35 Michał Górny
2020-11-28 11:43 Sam James
2020-11-28 11:43 Sam James
2020-08-04 12:01 Michał Górny
2020-08-01 21:23 Michał Górny
2020-05-27 15:22 Michał Górny
2020-01-22 23:40 Thomas Deutschmann
2019-12-15 12:36 Pacho Ramos
2019-12-08 4:50 Matt Turner
2019-11-22 23:35 Sergei Trofimovich
2019-11-22 13:44 Matt Turner
2019-11-20 17:28 Aaron Bauman
2019-11-20 11:50 Agostino Sarubbo
2019-11-20 11:48 Agostino Sarubbo
2019-11-20 11:35 Agostino Sarubbo
2019-11-20 11:27 Agostino Sarubbo
2019-11-19 15:40 Agostino Sarubbo
2019-11-19 11:58 Agostino Sarubbo
2019-03-20 10:31 Fabian Groffen
2019-01-17 20:45 Mikle Kolyada
2018-12-31 10:21 Mikle Kolyada
2018-08-20 18:17 Sergei Trofimovich
2018-05-04 13:05 Mart Raudsepp
2018-03-30 18:08 Sergei Trofimovich
2018-02-22 17:02 Michał Górny
2018-02-22 14:22 Michał Górny
2017-10-28 22:34 Sergei Trofimovich
2017-09-28 13:42 Michael Palimaka
2017-07-02 15:02 Sergei Trofimovich
2017-06-28 13:19 Agostino Sarubbo
2017-06-26 20:18 Tobias Klausmann
2017-06-09 14:19 Brian Dolbec
2017-05-26 10:16 Tobias Klausmann
2017-03-30 2:40 Brian Dolbec
2017-03-28 19:07 Brian Dolbec
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=1513203337.9f2768c046eaf746f84c408f15d327339f99eab5.slyfox@gentoo \
--to=slyfox@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