From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/highline/
Date: Sat, 21 Oct 2017 09:10:51 +0000 (UTC) [thread overview]
Message-ID: <1508576979.840c04a6e64275abb05f7ab4ebd880cc85b8ab97.slyfox@gentoo> (raw)
commit: 840c04a6e64275abb05f7ab4ebd880cc85b8ab97
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 21 09:09:39 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Oct 21 09:09:39 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=840c04a6
dev-ruby/highline: stable 1.7.8 for ppc/ppc64, bug #634930
Package-Manager: Portage-2.3.12, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc ppc64"
dev-ruby/highline/highline-1.7.8.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/highline/highline-1.7.8.ebuild b/dev-ruby/highline/highline-1.7.8.ebuild
index 3a347a53d82..617ac90a150 100644
--- a/dev-ruby/highline/highline-1.7.8.ebuild
+++ b/dev-ruby/highline/highline-1.7.8.ebuild
@@ -16,7 +16,7 @@ HOMEPAGE="https://github.com/JEG2/highline"
IUSE=""
LICENSE="|| ( GPL-2 Ruby )"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ppc ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x64-solaris ~x86-solaris"
all_ruby_prepare() {
# fix up gemspec file not to call git
next reply other threads:[~2017-10-21 9:10 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 9:10 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 6:48 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/highline/ Hans de Graaff
2024-10-15 5:22 Sam James
2024-10-09 2:53 Jakov Smolić
2024-10-06 11:18 Sam James
2024-10-06 11:11 Sam James
2024-10-06 11:11 Sam James
2024-08-31 9:11 Hans de Graaff
2024-08-31 6:00 Hans de Graaff
2024-07-17 5:57 Hans de Graaff
2024-04-28 19:11 Ionen Wolkens
2024-04-06 7:21 Hans de Graaff
2023-07-04 9:41 Hans de Graaff
2023-04-13 6:11 Sam James
2023-04-10 10:56 Sam James
2023-04-10 10:56 Sam James
2023-04-10 10:54 Sam James
2023-04-10 10:54 Sam James
2023-04-10 10:54 Sam James
2023-03-28 22:26 Sam James
2023-03-28 22:12 Sam James
2023-03-28 21:52 Sam James
2023-03-28 21:44 Sam James
2023-03-11 7:37 Hans de Graaff
2022-07-30 7:46 Hans de Graaff
2022-05-06 6:54 Hans de Graaff
2021-04-10 6:17 Hans de Graaff
2020-09-05 8:01 Hans de Graaff
2020-01-22 7:54 Hans de Graaff
2019-12-28 16:01 Mikle Kolyada
2019-11-25 7:30 Sergei Trofimovich
2019-11-23 16:57 Agostino Sarubbo
2019-11-23 15:51 Agostino Sarubbo
2019-11-23 15:50 Agostino Sarubbo
2019-11-23 15:40 Agostino Sarubbo
2019-11-23 13:30 Agostino Sarubbo
2019-11-23 13:26 Agostino Sarubbo
2019-11-23 7:22 Hans de Graaff
2019-10-12 6:14 Hans de Graaff
2019-04-21 17:00 Hans de Graaff
2019-04-21 17:00 Hans de Graaff
2019-04-10 6:09 Hans de Graaff
2019-01-25 6:10 Hans de Graaff
2019-01-15 6:02 Hans de Graaff
2018-06-21 4:42 Hans de Graaff
2018-02-04 10:45 Hans de Graaff
2017-12-25 7:05 Hans de Graaff
2017-11-30 20:06 Sergei Trofimovich
2017-11-27 8:50 Sergei Trofimovich
2017-10-23 18:42 Thomas Deutschmann
2017-10-22 21:42 Tobias Klausmann
2017-10-22 7:11 Hans de Graaff
2017-10-21 10:19 Sergei Trofimovich
2017-02-05 15:09 Hans de Graaff
2016-12-03 6:15 Hans de Graaff
2016-05-04 13:22 Manuel Rüger
2016-05-04 13:22 Manuel Rüger
2015-11-24 7:00 Hans de Graaff
2015-11-07 23:21 Mikle Kolyada
2015-10-26 7:03 Jeroen Roovers
2015-10-26 5:26 Jeroen Roovers
2015-10-23 9:05 Agostino Sarubbo
2015-10-20 5:13 Hans de Graaff
2015-10-20 5:13 Hans de Graaff
2015-09-26 0:44 Manuel Rüger
2015-09-18 5:25 Hans de Graaff
2015-09-16 17:36 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=1508576979.840c04a6e64275abb05f7ab4ebd880cc85b8ab97.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