From: "Markus Meier" <maekke@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/rubygems/
Date: Tue, 11 Jul 2017 04:58:28 +0000 (UTC) [thread overview]
Message-ID: <1499748623.5556b2017aee381e15f9c809f2e02456cc443081.maekke@gentoo> (raw)
commit: 5556b2017aee381e15f9c809f2e02456cc443081
Author: Markus Meier <maekke <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 11 04:50:23 2017 +0000
Commit: Markus Meier <maekke <AT> gentoo <DOT> org>
CommitDate: Tue Jul 11 04:50:23 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5556b201
virtual/rubygems: arm stable, bug #615818
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
virtual/rubygems/rubygems-11.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virtual/rubygems/rubygems-11.ebuild b/virtual/rubygems/rubygems-11.ebuild
index 5321375896c..6e1af6ad661 100644
--- a/virtual/rubygems/rubygems-11.ebuild
+++ b/virtual/rubygems/rubygems-11.ebuild
@@ -8,7 +8,7 @@ inherit ruby-ng
DESCRIPTION="Virtual ebuild for rubygems"
SLOT="0"
-KEYWORDS="alpha amd64 ~arm ~arm64 hppa ia64 ~mips ppc ppc64 ~s390 ~sh ~sparc x86 ~ppc-aix ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~mips ppc ppc64 ~s390 ~sh ~sparc x86 ~ppc-aix ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
RDEPEND="
ruby_targets_rbx? ( dev-lang/rubinius )
next reply other threads:[~2017-07-11 4:58 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 4:58 Markus Meier [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-29 12:35 [gentoo-commits] repo/gentoo:master commit in: virtual/rubygems/ Sam James
2024-07-17 4:38 Viorel Munteanu
2024-04-01 8:47 Hans de Graaff
2024-04-01 8:47 Hans de Graaff
2023-09-23 7:07 Hans de Graaff
2023-08-26 15:39 Hans de Graaff
2023-08-26 15:39 Hans de Graaff
2023-06-23 9:38 Sam James
2023-05-15 9:10 Hans de Graaff
2023-04-10 11:04 Hans de Graaff
2022-08-27 7:53 Sam James
2022-08-27 7:53 Sam James
2022-05-08 16:12 WANG Xuerui
2022-05-08 15:11 WANG Xuerui
2022-04-15 5:46 Sam James
2022-03-12 7:21 Hans de Graaff
2021-11-17 8:19 Sam James
2021-10-14 9:07 Sam James
2021-10-14 9:07 Sam James
2021-10-14 9:07 Sam James
2021-10-11 1:36 Sam James
2021-10-11 1:17 Sam James
2021-10-11 1:07 Sam James
2021-10-11 1:07 Sam James
2021-09-12 7:56 Hans de Graaff
2021-07-21 10:27 Marek Szuba
2021-05-13 15:19 David Seifert
2021-01-06 12:42 Fabian Groffen
2020-12-28 7:46 Hans de Graaff
2020-12-27 19:00 Fabian Groffen
2020-08-07 7:46 Hans de Graaff
2019-12-26 11:06 Hans de Graaff
2019-12-02 11:28 Hans de Graaff
2019-08-21 16:28 Hans de Graaff
2019-04-27 19:48 Aaron Bauman
2019-04-09 5:53 Hans de Graaff
2019-01-09 10:44 Hans de Graaff
2018-12-30 3:43 Matt Turner
2018-12-27 2:57 Matt Turner
2018-12-27 2:57 Matt Turner
2018-12-26 8:20 Hans de Graaff
2018-12-25 11:11 Sergei Trofimovich
2018-12-15 14:25 Mikle Kolyada
2018-12-11 16:42 Thomas Deutschmann
2018-11-18 8:11 Hans de Graaff
2018-11-18 8:11 Hans de Graaff
2018-11-17 21:34 Thomas Deutschmann
2018-06-28 14:22 Mikle Kolyada
2018-04-27 7:09 Hans de Graaff
2017-12-25 17:02 Hans de Graaff
2017-12-15 23:34 Sergei Trofimovich
2017-08-06 5:48 Hans de Graaff
2017-08-06 5:48 Hans de Graaff
2017-06-05 21:53 Sergei Trofimovich
2017-05-15 13:28 Michał Górny
2017-04-30 8:10 Jeroen Roovers
2017-04-25 7:08 Tobias Klausmann
2017-03-26 7:50 Hans de Graaff
2017-03-08 23:39 Michael Weber
2017-03-01 13:05 Michael Weber
2016-12-26 19:17 Hans de Graaff
2016-12-04 8:43 Hans de Graaff
2016-04-03 6:56 Hans de Graaff
2015-12-27 9:22 Hans de Graaff
2015-08-24 5:03 Jeroen Roovers
2015-08-09 16:03 Mikle Kolyada
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=1499748623.5556b2017aee381e15f9c809f2e02456cc443081.maekke@gentoo \
--to=maekke@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