From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/hashie/
Date: Mon, 28 Jan 2019 21:45:58 +0000 (UTC) [thread overview]
Message-ID: <1548711922.b91c67e431631af76962bba4e8eb56771bb30da2.graaff@gentoo> (raw)
commit: b91c67e431631af76962bba4e8eb56771bb30da2
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 28 21:10:00 2019 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Jan 28 21:45:22 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b91c67e4
dev-ruby/hashie: add ~arm to older slot
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
dev-ruby/hashie/hashie-2.1.2-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/hashie/hashie-2.1.2-r1.ebuild b/dev-ruby/hashie/hashie-2.1.2-r1.ebuild
index 946e8853989..dd1bc65c9ee 100644
--- a/dev-ruby/hashie/hashie-2.1.2-r1.ebuild
+++ b/dev-ruby/hashie/hashie-2.1.2-r1.ebuild
@@ -17,7 +17,7 @@ HOMEPAGE="http://intridea.com/posts/hashie-the-hash-toolkit"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="amd64 ~ppc ~ppc64 x86"
+KEYWORDS="amd64 ~arm ~ppc ~ppc64 x86"
IUSE=""
all_ruby_prepare() {
next reply other threads:[~2019-01-28 21:46 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 21:45 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-16 8:25 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/hashie/ Hans de Graaff
2024-01-07 7:49 Hans de Graaff
2023-07-11 8:13 Jakov Smolić
2023-06-23 20:03 Sam James
2023-06-23 9:38 Sam James
2023-04-08 8:42 Arthur Zamarin
2022-07-25 5:42 Hans de Graaff
2022-06-27 4:59 Hans de Graaff
2022-06-27 4:59 Hans de Graaff
2022-03-20 5:49 Hans de Graaff
2021-11-09 6:36 Hans de Graaff
2021-11-07 8:11 Hans de Graaff
2021-10-02 20:40 Sam James
2021-10-02 20:40 Sam James
2021-10-02 19:06 Sam James
2021-10-02 19:06 Sam James
2021-07-07 8:31 Hans de Graaff
2021-07-06 6:27 Hans de Graaff
2020-12-20 19:14 Sam James
2020-12-20 19:03 Sam James
2020-05-23 18:49 Hans de Graaff
2020-04-21 19:45 Sergei Trofimovich
2020-04-21 19:45 Sergei Trofimovich
2020-04-21 19:45 Sergei Trofimovich
2020-04-19 12:22 Sergei Trofimovich
2020-03-10 7:04 Hans de Graaff
2019-11-16 9:13 Hans de Graaff
2019-11-02 5:40 Hans de Graaff
2019-03-29 8:14 Hans de Graaff
2019-01-28 21:45 Hans de Graaff
2019-01-27 19:13 Hans de Graaff
2018-08-14 4:02 Hans de Graaff
2018-08-14 4:02 Hans de Graaff
2018-05-20 6:20 Hans de Graaff
2018-03-25 19:45 Sergei Trofimovich
2018-02-03 18:22 Hans de Graaff
2017-12-20 6:41 Hans de Graaff
2017-09-20 6:07 Hans de Graaff
2017-07-13 4:39 Hans de Graaff
2017-07-05 5:37 Hans de Graaff
2017-03-06 6:12 Hans de Graaff
2017-02-16 6:44 Hans de Graaff
2017-02-01 7:02 Hans de Graaff
2017-01-18 7:16 Hans de Graaff
2016-12-29 13:06 Hans de Graaff
2016-09-18 5:53 Hans de Graaff
2016-09-18 5:53 Hans de Graaff
2016-09-18 5:53 Hans de Graaff
2016-08-05 12:14 Hans de Graaff
2016-06-13 4:37 Richard Farina
2016-05-01 6:34 Hans de Graaff
2016-05-01 6:34 Hans de Graaff
2016-05-01 6:34 Hans de Graaff
2016-04-01 6:52 Hans de Graaff
2016-03-21 21:49 Manuel Rüger
2016-03-21 21:49 Manuel Rüger
2015-12-20 20:21 Hans de Graaff
2015-10-27 5:47 Hans de Graaff
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=1548711922.b91c67e431631af76962bba4e8eb56771bb30da2.graaff@gentoo \
--to=graaff@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