public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/jsonpickle/
Date: Wed, 17 Mar 2021 02:16:03 +0000 (UTC)	[thread overview]
Message-ID: <1615947307.302ece03ea89fb070f7b8fc4c62814ed65294b9a.sam@gentoo> (raw)

commit:     302ece03ea89fb070f7b8fc4c62814ed65294b9a
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 17 02:15:07 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 17 02:15:07 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=302ece03

dev-python/jsonpickle: Stabilize 2.0.0 ALLARCHES, #776088

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/jsonpickle/jsonpickle-2.0.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/jsonpickle/jsonpickle-2.0.0.ebuild b/dev-python/jsonpickle/jsonpickle-2.0.0.ebuild
index cfb3bc40153..629cee7b689 100644
--- a/dev-python/jsonpickle/jsonpickle-2.0.0.ebuild
+++ b/dev-python/jsonpickle/jsonpickle-2.0.0.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm ~arm64 x86 ~amd64-linux ~x86-linux"
 
 # There are optional json backends serializer/deserializers in addition to those selected here
 # jsonlib, yajl.


             reply	other threads:[~2021-03-17  2:16 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  2:16 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-07  6:45 [gentoo-commits] repo/gentoo:master commit in: dev-python/jsonpickle/ Michał Górny
2024-11-07  6:45 Michał Górny
2024-11-06  7:11 Michał Górny
2024-09-21 12:02 Michał Górny
2024-09-21 11:54 Arthur Zamarin
2024-09-03  5:23 Michał Górny
2024-07-07 17:05 Michał Górny
2024-07-06  6:43 Arthur Zamarin
2024-06-21 16:59 Michał Górny
2024-06-10  1:52 Michał Górny
2024-05-22  8:03 Michał Górny
2024-05-01 17:44 Michał Górny
2024-05-01 17:01 Sam James
2024-04-13 16:08 Michał Górny
2024-04-12  3:35 Michał Górny
2024-03-07 19:48 Michał Górny
2024-03-07 18:12 Sam James
2024-02-20  6:13 Michał Górny
2023-11-24 15:02 Arthur Zamarin
2023-10-24  5:40 Michał Górny
2023-09-17 11:26 Michał Górny
2023-08-14  6:26 Michał Górny
2023-01-07 18:55 Arthur Zamarin
2022-12-17 12:34 Michał Górny
2022-12-02 15:39 Michał Górny
2022-12-02 14:03 Arthur Zamarin
2022-11-08  5:00 Michał Górny
2022-11-07 23:18 Sam James
2022-08-29 10:37 Michał Górny
2022-06-13 11:25 Michał Górny
2022-06-13  7:15 Agostino Sarubbo
2022-05-12  7:13 Michał Górny
2022-03-15 14:14 Michał Górny
2022-03-15 11:52 Jakov Smolić
2022-02-04 12:04 Michał Górny
2022-01-28 18:41 Arthur Zamarin
2022-01-14 11:17 Arthur Zamarin
2021-12-13  3:09 Yixun Lan
2021-08-20 12:46 Arthur Zamarin
2021-08-20 12:46 Arthur Zamarin
2021-03-17  7:48 Michał Górny
2021-02-19  8:58 Michał Górny
2021-02-19  3:40 Sam James
2021-02-08 15:07 Michał Górny
2021-02-08  8:44 Michał Górny
2021-01-31  8:53 Michał Górny
2021-01-17  9:02 Michał Górny
2020-12-31  1:17 Sam James
2020-12-30  8:58 Michał Górny
2020-11-30  8:25 Michał Górny
2020-08-18  5:28 Sam James
2020-06-12 15:40 Michał Górny
2020-06-04  6:35 Agostino Sarubbo
2020-06-04  6:23 Agostino Sarubbo
2020-05-19 12:49 Michał Górny
2020-05-04 11:13 Michał Górny
2020-05-01 15:44 Michał Górny
2020-04-29  6:31 Patrick McLean
2020-04-29  5:57 Patrick McLean
2020-03-17  7:23 Michał Górny
2020-03-07 15:03 Michał Górny
2020-03-07 11:03 Agostino Sarubbo
2020-03-07  9:44 Agostino Sarubbo
2020-03-02 12:23 Sebastian Pipping
2020-02-05 15:29 Michał Górny
2019-06-24 20:57 Zac Medico
2018-06-24 15:24 Pacho Ramos
2017-01-18 11:57 Agostino Sarubbo
2017-01-18 11:28 Agostino Sarubbo
2016-03-13 19:04 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=1615947307.302ece03ea89fb070f7b8fc4c62814ed65294b9a.sam@gentoo \
    --to=sam@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