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/bigdecimal/
Date: Thu, 09 Oct 2025 00:07:15 +0000 (UTC)	[thread overview]
Message-ID: <1759968404.09dc4c653126794ea6d50b7f325744eda4cb9ef2.sam@gentoo> (raw)

commit:     09dc4c653126794ea6d50b7f325744eda4cb9ef2
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Oct  9 00:06:44 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Oct  9 00:06:44 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=09dc4c65

dev-ruby/bigdecimal: Stabilize 3.2.3 arm64, #963943

Signed-off-by: Sam James <sam <AT> gentoo.org>

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

diff --git a/dev-ruby/bigdecimal/bigdecimal-3.2.3.ebuild b/dev-ruby/bigdecimal/bigdecimal-3.2.3.ebuild
index 7e2dfff6ade1..f9c4621236e8 100644
--- a/dev-ruby/bigdecimal/bigdecimal-3.2.3.ebuild
+++ b/dev-ruby/bigdecimal/bigdecimal-3.2.3.ebuild
@@ -18,7 +18,7 @@ SRC_URI="https://github.com/ruby/bigdecimal/archive/v${PV}.tar.gz -> ${P}.tar.gz
 
 LICENSE="|| ( Ruby-BSD BSD-2 )"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha ~amd64 ~arm arm64 ~hppa ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
 IUSE="test"
 
 ruby_add_bdepend "test? ( dev-ruby/test-unit dev-ruby/test-unit-ruby-core )"


             reply	other threads:[~2025-10-09  0:07 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09  0:07 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-17 12:30 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/bigdecimal/ Arthur Zamarin
2025-10-10  7:09 Hans de Graaff
2025-10-09  0:07 Sam James
2025-10-09  0:07 Sam James
2025-10-09  0:07 Sam James
2025-10-08 11:41 Hans de Graaff
2025-10-08 11:41 Hans de Graaff
2025-09-04 16:45 Hans de Graaff
2025-08-18  9:52 Hans de Graaff
2025-06-05  4:44 Hans de Graaff
2025-05-31  6:47 Hans de Graaff
2025-05-31  6:47 Hans de Graaff
2025-05-30  5:51 Hans de Graaff
2025-05-21 10:56 Arthur Zamarin
2025-05-20 21:04 Sam James
2025-05-18 17:57 Arthur Zamarin
2025-05-18 17:57 Arthur Zamarin
2025-05-18  9:39 Sam James
2025-05-18  9:38 Sam James
2024-12-25  5:25 Hans de Graaff
2024-12-25  5:25 Hans de Graaff
2024-10-13 20:39 Sam James
2024-10-10 16:20 Arthur Zamarin
2024-10-09  2:53 Jakov Smolić
2024-10-06 14:29 Arthur Zamarin
2024-10-06 11:21 Sam James
2024-10-06 11:12 Sam James
2024-10-06 11:11 Sam James
2024-09-11 15:04 Arthur Zamarin
2024-07-12  6:21 Ionen Wolkens
2024-07-02  3:56 Ionen Wolkens
2024-06-13  4:53 Sam James
2024-06-08 11:12 Arthur Zamarin
2024-05-08  5:06 Hans de Graaff
2024-05-08  5:06 Hans de Graaff
2024-03-15  6:08 Hans de Graaff
2024-01-19  8:08 Hans de Graaff
2023-12-27 20:59 Hans de Graaff
2023-12-14  6:30 Hans de Graaff
2023-10-13  5:37 Hans de Graaff
2023-10-13  5:37 Hans de Graaff
2023-09-02  6:19 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=1759968404.09dc4c653126794ea6d50b7f325744eda4cb9ef2.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