From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/jaraco-envs/
Date: Wed, 4 Dec 2019 19:44:34 +0000 (UTC) [thread overview]
Message-ID: <1575488624.1ef37588d921f899d37323546449a1f8cb546eaf.slyfox@gentoo> (raw)
commit: 1ef37588d921f899d37323546449a1f8cb546eaf
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Wed Dec 4 16:00:56 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Dec 4 19:43:44 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1ef37588
dev-python/jaraco-envs: keyworded 1.0.1 for hppa/sparc, bug #700918
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="hppa sparc"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-python/jaraco-envs/jaraco-envs-1.0.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/jaraco-envs/jaraco-envs-1.0.1.ebuild b/dev-python/jaraco-envs/jaraco-envs-1.0.1.ebuild
index c325ff5c459..4619f5e41c9 100644
--- a/dev-python/jaraco-envs/jaraco-envs-1.0.1.ebuild
+++ b/dev-python/jaraco-envs/jaraco-envs-1.0.1.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/jaraco/jaraco.envs/archive/v${PV}.tar.gz -> ${P}.tar
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="~amd64 ~hppa ~sparc ~x86"
RDEPEND="dev-python/namespace-jaraco[${PYTHON_USEDEP}]
dev-python/path-py[${PYTHON_USEDEP}]
next reply other threads:[~2019-12-04 19:44 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 19:44 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-16 20:45 [gentoo-commits] repo/gentoo:master commit in: dev-python/jaraco-envs/ Michał Górny
2024-06-29 15:54 Andreas K. Hüttel
2024-05-11 17:02 Michał Górny
2023-11-25 10:42 Michał Górny
2023-11-25 8:51 Sam James
2023-10-24 5:27 Michał Górny
2023-05-27 17:13 Michał Górny
2023-03-21 16:45 Michał Górny
2023-02-12 19:05 Michał Górny
2023-02-07 9:26 Michał Górny
2022-05-31 7:28 Michał Górny
2022-05-31 7:17 Jakov Smolić
2022-05-12 10:53 Michał Górny
2022-04-30 7:35 Michał Górny
2022-04-25 19:00 Sam James
2022-03-31 16:03 Michał Górny
2022-03-31 14:33 Jakov Smolić
2022-02-28 8:28 Michał Górny
2022-02-04 12:04 Michał Górny
2022-01-26 22:42 James Le Cuirot
2021-12-30 21:30 Michał Górny
2021-12-30 19:54 Arthur Zamarin
2021-11-30 10:01 Michał Górny
2021-11-12 9:40 Michał Górny
2021-07-28 23:38 Marek Szuba
2021-05-05 18:20 Michał Górny
2021-04-18 7:05 Michał Górny
2021-04-18 1:41 Sam James
2021-03-15 8:34 Michał Górny
2021-02-19 8:35 Michał Górny
2021-02-19 2:54 Sam James
2021-01-06 10:00 Michał Górny
2020-09-06 17:34 Sam James
2020-08-01 8:53 Sergei Trofimovich
2020-07-28 17:28 Sergei Trofimovich
2020-07-25 21:01 Sam James
2020-07-25 14:08 Sam James
2020-07-09 10:39 Michał Górny
2020-07-09 10:39 Michał Górny
2020-06-05 13:57 Michał Górny
2020-06-01 20:30 Michał Górny
2020-05-31 10:04 Sergei Trofimovich
2020-05-30 14:37 Michał Górny
2020-05-30 11:51 Michał Górny
2020-05-27 11:00 Michał Górny
2020-05-27 7:16 Michał Górny
2020-05-27 7:16 Michał Górny
2020-03-04 5:01 Michał Górny
2019-12-04 22:28 Patrick McLean
2019-11-25 8:32 Patrick McLean
2019-11-22 3:15 Patrick McLean
2019-11-22 0:20 Patrick McLean
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=1575488624.1ef37588d921f899d37323546449a1f8cb546eaf.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