From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/cloudpickle/
Date: Sun, 30 Jun 2019 22:26:16 +0000 (UTC) [thread overview]
Message-ID: <1561933156.d0e4336b9d905f29d8e67ede22d1aed9210bfda3.zmedico@gentoo> (raw)
commit: d0e4336b9d905f29d8e67ede22d1aed9210bfda3
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 30 22:18:44 2019 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sun Jun 30 22:19:16 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d0e4336b
dev-python/cloudpickle: keyword ~arm64
Fixes: 1bebe34a7bbb ("dev-python/kombu: Bump to version 4.6.3")
Package-Manager: Portage-2.3.67, Repoman-2.3.16
Signed-off-by: Zac Medico <zmedico <AT> gentoo.org>
dev-python/cloudpickle/cloudpickle-1.2.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/cloudpickle/cloudpickle-1.2.1.ebuild b/dev-python/cloudpickle/cloudpickle-1.2.1.ebuild
index c99bc7ac83d..ac484042436 100644
--- a/dev-python/cloudpickle/cloudpickle-1.2.1.ebuild
+++ b/dev-python/cloudpickle/cloudpickle-1.2.1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="mirror://pypi/${PN::1}/${PN}/${P}.tar.gz"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 ~arm64 ~x86 ~amd64-linux ~x86-linux"
IUSE="test"
RESTRICT="!test? ( test )"
next reply other threads:[~2019-06-30 22:26 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 22:26 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-01 11:58 [gentoo-commits] repo/gentoo:master commit in: dev-python/cloudpickle/ Michał Górny
2025-02-01 10:05 Arthur Zamarin
2025-01-15 5:39 Michał Górny
2024-11-02 7:58 Sam James
2024-10-14 17:12 Michał Górny
2024-10-12 4:59 Michał Górny
2024-06-13 17:17 Michał Górny
2024-01-04 17:14 Michał Górny
2023-11-29 10:17 Michał Górny
2023-11-29 10:15 Michał Górny
2023-11-14 4:34 Michał Górny
2023-10-16 13:56 Michał Górny
2023-02-21 7:50 Michał Górny
2023-02-21 7:50 Michał Górny
2023-02-20 19:13 Arthur Zamarin
2023-01-19 17:43 Michał Górny
2022-10-10 20:18 Michał Górny
2022-10-10 18:32 Arthur Zamarin
2022-09-09 7:23 Arthur Zamarin
2022-06-16 9:23 Michał Górny
2022-06-16 9:06 Jakov Smolić
2022-05-21 6:47 Michał Górny
2022-05-13 12:35 Michał Górny
2022-02-03 21:10 Arthur Zamarin
2022-02-02 10:48 Sam James
2022-01-29 18:38 Arthur Zamarin
2022-01-29 13:01 Arthur Zamarin
2022-01-10 4:20 Joshua Kinard
2021-12-31 20:20 James Le Cuirot
2021-12-31 16:53 Matt Turner
2021-12-30 5:49 Sam James
2021-12-28 21:32 Arthur Zamarin
2021-12-28 19:27 Arthur Zamarin
2021-12-28 19:21 Arthur Zamarin
2021-10-16 5:56 Michał Górny
2021-10-15 22:42 Sam James
2021-09-11 7:15 Michał Górny
2021-09-02 17:05 Marek Szuba
2021-05-07 11:25 Michał Górny
2021-02-25 12:00 Sam James
2020-10-07 7:28 Michał Górny
2020-10-01 23:06 Sergei Trofimovich
2020-08-26 10:14 Michał Górny
2020-08-22 5:29 Agostino Sarubbo
2020-08-21 15:36 Agostino Sarubbo
2020-08-18 8:50 Michał Górny
2020-08-18 5:52 Sam James
2020-07-05 13:44 Agostino Sarubbo
2020-07-05 13:17 Michał Górny
2020-07-05 8:47 Sergei Trofimovich
2020-07-02 8:29 Michał Górny
2020-06-15 7:47 Michał Górny
2020-06-14 18:55 Michał Górny
2020-05-04 10:29 Michał Górny
2020-04-30 9:45 Michał Górny
2020-04-27 12:42 Michał Górny
2020-04-26 20:40 Michał Górny
2020-03-26 14:51 Michał Górny
2020-02-10 18:46 Michał Górny
2020-02-02 15:34 Michał Górny
2020-02-02 15:34 Michał Górny
2019-11-19 18:36 Matthew Thode
2019-10-31 21:29 Matthew Thode
2019-09-12 14:11 Michał Górny
2019-07-21 10:00 Sergei Trofimovich
2019-06-29 8:15 Michał Górny
2017-12-02 20:55 Mike Gilbert
2017-11-30 19:02 Thomas Deutschmann
2017-06-28 4:02 Sebastien Fabbro
2017-05-04 18:08 Manuel Rüger
2017-03-07 0:17 Sebastien Fabbro
2016-10-02 13:00 Patrice Clement
2016-10-02 13:00 Patrice Clement
2016-03-18 19:18 Sebastien Fabbro
2016-02-18 17:46 Patrick Lauer
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=1561933156.d0e4336b9d905f29d8e67ede22d1aed9210bfda3.zmedico@gentoo \
--to=zmedico@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