From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/yajl-ruby/
Date: Fri, 13 Jul 2018 18:46:31 +0000 (UTC) [thread overview]
Message-ID: <1531507566.b03eebfb5f8b07b94873d1ca9a7bdc4f19439e41.slyfox@gentoo> (raw)
commit: b03eebfb5f8b07b94873d1ca9a7bdc4f19439e41
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Fri Jul 13 14:41:32 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Jul 13 18:46:06 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b03eebfb
dev-ruby/yajl-ruby: stable 1.3.1 for sparc
Bug: https://bugs.gentoo.org/636474
Package-Manager: Portage-2.3.40, Repoman-2.3.9
RepoMan-Options: --include-arches="sparc"
dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild b/dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild
index 25e528409ab..3211a411b19 100644
--- a/dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild
+++ b/dev-ruby/yajl-ruby/yajl-ruby-1.3.1.ebuild
@@ -18,7 +18,7 @@ HOMEPAGE="https://github.com/brianmario/yajl-ruby"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ppc ppc64 ~sparc x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ppc ppc64 sparc x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
IUSE=""
RDEPEND="${RDEPEND} dev-libs/yajl"
next reply other threads:[~2018-07-13 18:46 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 18:46 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-31 8:05 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/yajl-ruby/ Hans de Graaff
2023-03-28 19:24 Sam James
2023-03-28 19:24 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:05 Sam James
2023-03-10 20:29 Hans de Graaff
2022-05-27 5:39 Hans de Graaff
2022-04-15 14:00 Hans de Graaff
2022-04-13 9:32 Jakov Smolić
2022-04-11 6:50 Agostino Sarubbo
2022-04-11 6:35 Jakov Smolić
2022-04-10 17:54 Arthur Zamarin
2022-04-10 17:54 Arthur Zamarin
2022-04-10 17:51 Arthur Zamarin
2022-04-10 17:47 Arthur Zamarin
2022-04-06 5:48 Hans de Graaff
2021-07-07 8:31 Hans de Graaff
2021-01-06 18:32 Fabian Groffen
2020-12-17 7:51 Sam James
2020-11-06 3:21 Sam James
2020-07-19 6:15 Hans de Graaff
2020-06-19 6:40 Sergei Trofimovich
2020-06-15 15:16 Agostino Sarubbo
2020-06-15 15:12 Agostino Sarubbo
2020-06-15 15:03 Agostino Sarubbo
2020-06-14 20:19 Sergei Trofimovich
2020-06-14 20:08 Sergei Trofimovich
2020-01-19 6:52 Hans de Graaff
2019-11-02 5:55 Hans de Graaff
2019-04-27 15:20 Sergei Trofimovich
2019-01-12 7:42 Hans de Graaff
2018-07-28 4:47 Hans de Graaff
2018-07-20 5:33 Hans de Graaff
2018-07-13 19:04 Hans de Graaff
2018-07-11 23:55 Mikle Kolyada
2018-04-30 5:15 Hans de Graaff
2018-04-28 7:23 Mikle Kolyada
2018-04-11 20:43 Thomas Deutschmann
2018-04-06 22:44 Sergei Trofimovich
2018-04-06 17:13 Tobias Klausmann
2018-04-06 14:26 Aaron Bauman
2018-04-06 4:54 Hans de Graaff
2017-12-22 6:00 Hans de Graaff
2017-12-21 19:28 Markus Meier
2017-12-06 22:44 Sergei Trofimovich
2017-11-08 6:37 Hans de Graaff
2017-10-22 21:34 Thomas Deutschmann
2017-10-22 9:21 Hans de Graaff
2017-10-22 9:21 Hans de Graaff
2017-10-14 22:00 Sergei Trofimovich
2017-09-24 16:16 Sergei Trofimovich
2017-08-23 21:43 Sergei Trofimovich
2017-08-23 6:14 Hans de Graaff
2017-06-05 8:44 Hans de Graaff
2016-12-11 7:26 Hans de Graaff
2016-11-02 5:52 Hans de Graaff
2016-07-21 19:39 Hans de Graaff
2016-03-28 10:21 Hans de Graaff
2016-03-06 18:25 Manuel Rüger
2016-03-06 18:25 Manuel Rüger
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=1531507566.b03eebfb5f8b07b94873d1ca9a7bdc4f19439e41.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