From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rspec-retry/
Date: Sun, 25 Mar 2018 19:58:51 +0000 (UTC) [thread overview]
Message-ID: <1522007925.368af56c755e61ee9e35bcca3225cc15ed89320e.slyfox@gentoo> (raw)
commit: 368af56c755e61ee9e35bcca3225cc15ed89320e
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 25 19:56:59 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Mar 25 19:58:45 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=368af56c
dev-ruby/rspec-retry: keyworded 0.5.6 for ppc, bug #570052
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc"
dev-ruby/rspec-retry/rspec-retry-0.5.6.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/rspec-retry/rspec-retry-0.5.6.ebuild b/dev-ruby/rspec-retry/rspec-retry-0.5.6.ebuild
index 8a16d107962..eea79143a8f 100644
--- a/dev-ruby/rspec-retry/rspec-retry-0.5.6.ebuild
+++ b/dev-ruby/rspec-retry/rspec-retry-0.5.6.ebuild
@@ -16,7 +16,7 @@ IUSE=""
SLOT="0"
LICENSE="MIT"
-KEYWORDS="~amd64 ~arm ~ppc64 ~x86 ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~amd64 ~arm ~ppc ~ppc64 ~x86 ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
ruby_add_rdepend ">=dev-ruby/rspec-core-3.3:3"
next reply other threads:[~2018-03-25 19:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 19:58 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-06 10:49 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rspec-retry/ Sam James
2024-10-06 10:49 Sam James
2024-10-06 10:49 Sam James
2024-10-06 10:49 Sam James
2024-10-06 10:49 Sam James
2024-10-06 10:49 Sam James
2024-09-11 18:12 Arthur Zamarin
2023-12-31 10:29 Hans de Graaff
2023-12-08 14:24 Arthur Zamarin
2023-12-05 18:25 Ionen Wolkens
2023-12-01 20:26 Arthur Zamarin
2023-09-18 18:25 WANG Xuerui
2023-09-18 10:56 Sam James
2023-09-11 11:41 Arthur Zamarin
2023-09-11 6:48 Jakov Smolić
2023-09-10 12:25 Sam James
2023-09-10 12:25 Sam James
2023-09-10 12:25 Sam James
2023-09-10 5:57 Hans de Graaff
2021-02-04 7:58 Agostino Sarubbo
2021-02-03 23:55 Thomas Deutschmann
2020-04-25 12:44 Sergei Trofimovich
2020-04-14 21:06 Sergei Trofimovich
2020-02-29 6:00 Hans de Graaff
2020-02-29 6:00 Hans de Graaff
2019-11-22 9:03 Hans de Graaff
2019-07-24 23:16 Aaron Bauman
2019-01-26 16:45 Hans de Graaff
2019-01-26 16:45 Hans de Graaff
2018-06-12 5:14 Hans de Graaff
2018-05-16 4:55 Hans de Graaff
2018-03-25 17:58 Sergei Trofimovich
2018-03-18 6:25 Hans de Graaff
2018-03-18 6:25 Hans de Graaff
2017-11-06 5:45 Hans de Graaff
2017-09-12 8:18 Sergei Trofimovich
2017-09-12 8:18 Sergei Trofimovich
2017-08-24 5:49 Hans de Graaff
2017-08-23 6:14 Hans de Graaff
2017-05-10 4:15 Hans de Graaff
2017-01-12 6:08 Hans de Graaff
2017-01-12 6:08 Hans de Graaff
2016-10-06 6:05 Hans de Graaff
2016-10-01 6:10 Hans de Graaff
2016-10-01 6:10 Hans de Graaff
2016-08-09 5:21 Hans de Graaff
2016-01-17 19:45 Fabian Groffen
2016-01-09 19:12 Markus Meier
2015-12-29 9:03 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=1522007925.368af56c755e61ee9e35bcca3225cc15ed89320e.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