From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rspec-pending_for/
Date: Mon, 5 Dec 2022 19:54:05 +0000 (UTC) [thread overview]
Message-ID: <1670270036.729dcacf9fd9936c940345803d4e3f59162c38fd.arthurzam@gentoo> (raw)
commit: 729dcacf9fd9936c940345803d4e3f59162c38fd
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 5 19:53:56 2022 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Mon Dec 5 19:53:56 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=729dcacf
dev-ruby/rspec-pending_for: Keyword 0.1.16 x86, #859448
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
dev-ruby/rspec-pending_for/rspec-pending_for-0.1.16.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/rspec-pending_for/rspec-pending_for-0.1.16.ebuild b/dev-ruby/rspec-pending_for/rspec-pending_for-0.1.16.ebuild
index e1083bce56d2..1e751c417c96 100644
--- a/dev-ruby/rspec-pending_for/rspec-pending_for-0.1.16.ebuild
+++ b/dev-ruby/rspec-pending_for/rspec-pending_for-0.1.16.ebuild
@@ -17,7 +17,7 @@ SRC_URI="https://github.com/pboling/rspec-pending_for/archive/v${PV}.tar.gz -> $
LICENSE="MIT"
SLOT="$(ver_cut 1)"
-KEYWORDS="~amd64 ~ppc ~ppc64"
+KEYWORDS="~amd64 ~ppc ~ppc64 ~x86"
IUSE=""
ruby_add_rdepend "
next reply other threads:[~2022-12-05 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 19:54 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-29 14:30 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rspec-pending_for/ Arthur Zamarin
2024-05-29 7:05 Hans de Graaff
2023-07-11 8:13 Jakov Smolić
2023-04-29 7:23 Hans de Graaff
2022-07-20 17:01 Sam James
2022-07-20 17:01 Sam James
2022-07-19 6:30 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=1670270036.729dcacf9fd9936c940345803d4e3f59162c38fd.arthurzam@gentoo \
--to=arthurzam@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