From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Cpanel-JSON-XS/
Date: Sat, 1 Jul 2017 11:14:49 +0000 (UTC) [thread overview]
Message-ID: <1498907670.58d69edbb235438985603f1d18850ef2b0c6a12b.slyfox@gentoo> (raw)
commit: 58d69edbb235438985603f1d18850ef2b0c6a12b
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 1 11:14:12 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Jul 1 11:14:30 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=58d69edb
Revert "dev-perl/Cpanel-JSON-XS: ia64 keyworded, bug #613376"
This reverts commit 8e88176f92c391f4a90bb262f1f3e1b6f8b476a7.
Accidentally dropped package down to ~ia64
dev-perl/Cpanel-JSON-XS/Cpanel-JSON-XS-3.23.300.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/Cpanel-JSON-XS/Cpanel-JSON-XS-3.23.300.ebuild b/dev-perl/Cpanel-JSON-XS/Cpanel-JSON-XS-3.23.300.ebuild
index f5784ede753..fd80826f71b 100644
--- a/dev-perl/Cpanel-JSON-XS/Cpanel-JSON-XS-3.23.300.ebuild
+++ b/dev-perl/Cpanel-JSON-XS/Cpanel-JSON-XS-3.23.300.ebuild
@@ -10,7 +10,7 @@ inherit perl-module
DESCRIPTION="cPanel fork of JSON::XS, fast and correct serializing"
SLOT="0"
-KEYWORDS="amd64 ~arm ~ia64 x86"
+KEYWORDS="amd64 ~arm ia64 x86"
IUSE="test"
RDEPEND=""
next reply other threads:[~2017-07-01 11:14 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 11:14 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-22 4:55 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Cpanel-JSON-XS/ Sam James
2024-11-02 7:10 Sam James
2024-07-27 12:35 Sam James
2024-07-27 12:35 Sam James
2024-07-27 12:35 Sam James
2024-07-27 12:35 Sam James
2024-07-27 12:35 Sam James
2024-06-01 3:31 Sam James
2023-08-19 7:45 Arthur Zamarin
2023-08-19 7:42 Arthur Zamarin
2023-08-19 7:42 Arthur Zamarin
2023-08-19 6:33 Sam James
2023-07-05 0:38 Sam James
2023-06-21 9:12 Arthur Zamarin
2023-06-21 9:12 Arthur Zamarin
2023-06-21 8:24 Arthur Zamarin
2023-06-21 8:24 Arthur Zamarin
2023-06-21 8:19 Arthur Zamarin
2023-06-21 8:18 Sam James
2023-06-03 22:38 Andreas K. Hüttel
2022-06-04 0:06 Sam James
2021-12-12 18:25 Sam James
2021-12-06 6:38 Arthur Zamarin
2021-12-05 3:15 Sam James
2021-12-05 3:15 Sam James
2021-12-05 3:08 Sam James
2021-10-20 0:11 Sam James
2021-10-15 5:59 Agostino Sarubbo
2021-10-14 21:21 Andreas K. Hüttel
2021-10-14 21:21 Andreas K. Hüttel
2021-07-26 6:24 Sam James
2021-07-15 21:42 Sam James
2021-07-15 21:39 Sam James
2021-07-15 21:33 Sam James
2021-05-06 6:57 Agostino Sarubbo
2021-05-05 16:09 Sergei Trofimovich
2021-05-04 21:31 Andreas K. Hüttel
2020-12-27 14:42 Fabian Groffen
2020-12-12 6:46 Kent Fredric
2020-10-19 3:58 Kent Fredric
2020-10-07 23:11 Kent Fredric
2020-09-07 9:26 Kent Fredric
2020-09-06 7:49 Sergei Trofimovich
2020-09-05 12:32 Kent Fredric
2020-08-16 18:08 Kent Fredric
2020-08-16 14:47 Agostino Sarubbo
2020-08-14 23:51 Sam James
2020-08-14 22:48 Sam James
2020-08-12 10:29 Sam James
2020-06-29 15:32 Kent Fredric
2019-05-04 21:46 Mikle Kolyada
2019-01-12 1:59 Kent Fredric
2018-10-29 4:06 Matt Turner
2018-06-08 13:26 Mikle Kolyada
2018-06-03 3:31 Kent Fredric
2018-04-18 7:05 Sergei Trofimovich
2018-04-07 21:13 Matt Turner
2018-04-05 21:07 Sergei Trofimovich
2018-04-05 18:29 Thomas Deutschmann
2018-04-05 14:11 Aaron Bauman
2018-01-23 22:21 Patrice Clement
2017-11-05 18:00 Sergei Trofimovich
2017-11-05 18:00 Sergei Trofimovich
2017-11-04 10:48 Sergei Trofimovich
2017-11-04 10:45 Sergei Trofimovich
2017-10-05 12:22 Kent Fredric
2017-08-03 8:24 Sergei Trofimovich
2017-08-03 8:12 Sergei Trofimovich
2017-07-01 10:23 Sergei Trofimovich
2017-06-30 8:28 Sergei Trofimovich
2017-06-29 8:06 Agostino Sarubbo
2017-05-22 2:20 Kent Fredric
2017-04-05 22:03 Michael Weber
2017-04-02 15:49 Kent Fredric
2017-03-21 1:48 Kent Fredric
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=1498907670.58d69edbb235438985603f1d18850ef2b0c6a12b.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