From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/ruby2ruby/
Date: Wed, 17 Apr 2019 20:01:34 +0000 (UTC) [thread overview]
Message-ID: <1555531274.4f20329f84c47afc6535938db047c98ea84f46b4.slyfox@gentoo> (raw)
commit: 4f20329f84c47afc6535938db047c98ea84f46b4
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Wed Apr 17 16:25:27 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Apr 17 20:01:14 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4f20329f
dev-ruby/ruby2ruby: stable 2.4.2 for hppa, bug #683250
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Package-Manager: Portage-2.3.62, Repoman-2.3.11
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
dev-ruby/ruby2ruby/ruby2ruby-2.4.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/ruby2ruby/ruby2ruby-2.4.2.ebuild b/dev-ruby/ruby2ruby/ruby2ruby-2.4.2.ebuild
index 6d4a31f5eca..41fd8f20fcb 100644
--- a/dev-ruby/ruby2ruby/ruby2ruby-2.4.2.ebuild
+++ b/dev-ruby/ruby2ruby/ruby2ruby-2.4.2.ebuild
@@ -15,7 +15,7 @@ HOMEPAGE="https://github.com/seattlerb/ruby2ruby"
LICENSE="GPL-2"
SLOT="2"
-KEYWORDS="~alpha amd64 arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x64-solaris ~x86-solaris"
IUSE="test"
ruby_add_rdepend "
next reply other threads:[~2019-04-17 22:40 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 20:01 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-06 18:39 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/ruby2ruby/ Arthur Zamarin
2024-10-06 14:27 Sam James
2024-07-13 5:36 Hans de Graaff
2024-07-13 5:36 Hans de Graaff
2024-05-31 13:41 Arthur Zamarin
2024-05-31 10:46 Arthur Zamarin
2024-03-30 8:49 Hans de Graaff
2023-04-02 6:36 Hans de Graaff
2021-07-20 5:18 Hans de Graaff
2021-07-03 7:22 Hans de Graaff
2020-09-27 10:05 Sergei Trofimovich
2020-09-24 6:46 Agostino Sarubbo
2020-09-18 10:07 Agostino Sarubbo
2020-07-25 17:10 Hans de Graaff
2020-02-02 15:47 Hans de Graaff
2019-09-28 5:47 Hans de Graaff
2019-06-04 5:42 Hans de Graaff
2019-05-11 7:15 Hans de Graaff
2019-04-20 17:57 Mikle Kolyada
2019-04-14 16:18 Mikle Kolyada
2019-04-13 14:18 Mikle Kolyada
2019-04-10 17:27 Hans de Graaff
2019-03-13 7:03 Hans de Graaff
2019-01-26 16:45 Hans de Graaff
2018-02-24 7:19 Hans de Graaff
2017-12-22 5:38 Hans de Graaff
2017-12-21 19:28 Markus Meier
2017-11-09 22:37 Sergei Trofimovich
2017-10-22 7:06 Hans de Graaff
2017-10-22 7:06 Hans de Graaff
2017-07-18 4:56 Hans de Graaff
2017-03-29 4:57 Hans de Graaff
2016-12-05 6:43 Hans de Graaff
2016-11-27 8:13 Hans de Graaff
2016-11-06 10:12 Hans de Graaff
2016-10-15 5:49 Hans de Graaff
2016-10-02 8:42 Jeroen Roovers
2016-09-23 17:40 Tobias Klausmann
2016-09-06 5:50 Hans de Graaff
2016-08-06 11:15 Markus Meier
2016-04-19 22:02 Manuel Rüger
2016-02-21 11:19 Manuel Rüger
2015-08-26 11:52 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=1555531274.4f20329f84c47afc6535938db047c98ea84f46b4.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