public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/msgpack/
Date: Fri, 24 Nov 2023 09:31:52 +0000 (UTC)	[thread overview]
Message-ID: <1700818222.723a9e37b3398abbc66dea60c070915b1d769b71.sam@gentoo> (raw)

commit:     723a9e37b3398abbc66dea60c070915b1d769b71
Author:     Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Thu Nov 23 19:53:04 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Nov 24 09:30:22 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=723a9e37

dev-ruby/msgpack: Keyword 1.7.2 ppc, #917362

Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-ruby/msgpack/msgpack-1.7.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/msgpack/msgpack-1.7.2.ebuild b/dev-ruby/msgpack/msgpack-1.7.2.ebuild
index 2c3aec847ad7..def9b13b0945 100644
--- a/dev-ruby/msgpack/msgpack-1.7.2.ebuild
+++ b/dev-ruby/msgpack/msgpack-1.7.2.ebuild
@@ -21,7 +21,7 @@ RUBY_S="${PN}-ruby-${PV}"
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~loong ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
 IUSE="doc"
 
 all_ruby_prepare() {


             reply	other threads:[~2023-11-24  9:31 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24  9:31 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-12 10:46 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/msgpack/ Hans de Graaff
2024-11-12 10:46 Hans de Graaff
2024-11-02 11:45 Arthur Zamarin
2024-10-30 15:46 Arthur Zamarin
2024-10-30 14:41 Sam James
2024-10-30 11:07 Sam James
2024-10-30 11:07 Sam James
2024-10-30 11:07 Sam James
2024-10-05  7:00 Hans de Graaff
2024-10-05  7:00 Hans de Graaff
2024-06-01  5:41 Hans de Graaff
2023-12-31 17:15 Hans de Graaff
2023-12-06 17:57 Ionen Wolkens
2023-11-23 21:09 Sam James
2023-11-23 17:12 Sam James
2023-11-15 18:39 Arthur Zamarin
2023-11-15 17:49 Jakov Smolić
2023-07-19  5:26 Hans de Graaff
2023-07-11  9:43 Hans de Graaff
2023-07-02  7:49 Hans de Graaff
2023-06-06 13:40 Hans de Graaff
2023-03-18 23:12 Sam James
2022-10-01  7:06 Hans de Graaff
2022-08-26 11:45 Hans de Graaff
2022-08-26 11:45 Hans de Graaff
2022-07-26  6:45 Hans de Graaff
2022-07-06  5:28 Hans de Graaff
2022-06-25  8:55 Hans de Graaff
2022-05-28  5:39 Hans de Graaff
2022-05-28  5:39 Hans de Graaff
2022-04-09  7:38 Hans de Graaff
2022-03-17  6:40 Hans de Graaff
2022-02-05  6:57 Hans de Graaff
2022-01-30  8:19 Hans de Graaff
2022-01-20  6:40 Hans de Graaff
2021-10-27 11:26 Hans de Graaff
2021-04-02 11:16 Hans de Graaff
2021-02-07  8:24 Hans de Graaff
2020-08-08  6:37 Hans de Graaff
2020-02-05  6:16 Hans de Graaff
2019-08-05  5:17 Hans de Graaff
2019-08-05  5:17 Hans de Graaff
2019-06-21  6:05 Hans de Graaff
2019-05-07  5:16 Hans de Graaff
2019-05-07  5:16 Hans de Graaff
2019-03-11  6:25 Hans de Graaff
2019-03-01  6:09 Hans de Graaff
2019-03-01  6:09 Hans de Graaff
2019-01-09  9:12 Hans de Graaff
2018-04-06  4:54 Hans de Graaff
2018-03-03  6:41 Hans de Graaff
2018-02-04 15:15 Hans de Graaff
2018-01-12  6:01 Hans de Graaff
2018-01-12  6:01 Hans de Graaff
2017-12-07  6:36 Hans de Graaff
2017-10-28 16:23 Andreas Sturmlechner
2017-09-10  7:53 Hans de Graaff
2017-03-07  6:01 Hans de Graaff
2017-01-28  6:48 Hans de Graaff
2016-11-14  6:39 Hans de Graaff
2016-11-14  6:39 Hans de Graaff
2016-10-17  5:23 Hans de Graaff
2016-08-22 19:15 Ole Reifschneider
2016-05-30 18:15 Hans de Graaff
2016-05-30 18:15 Hans de Graaff
2016-05-11  4:55 Hans de Graaff
2016-04-06  5:13 Hans de Graaff
2016-04-06  5:13 Hans de Graaff
2016-01-10  7:28 Hans de Graaff
2016-01-10  7:28 Hans de Graaff
2015-11-24  7:00 Hans de Graaff
2015-10-25  8:30 Hans de Graaff
2015-10-25  8: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=1700818222.723a9e37b3398abbc66dea60c070915b1d769b71.sam@gentoo \
    --to=sam@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