From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/base64/
Date: Wed, 27 Dec 2023 21:13:32 +0000 (UTC) [thread overview]
Message-ID: <1703711606.fe4e851f9659669c414ddd6ad93e1852ac2f7408.graaff@gentoo> (raw)
commit: fe4e851f9659669c414ddd6ad93e1852ac2f7408
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 27 21:01:14 2023 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Dec 27 21:13:26 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fe4e851f
dev-ruby/base64: enable ruby33
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/base64/base64-0.2.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/base64/base64-0.2.0.ebuild b/dev-ruby/base64/base64-0.2.0.ebuild
index ea8a5a9343ba..0a04667c63fa 100644
--- a/dev-ruby/base64/base64-0.2.0.ebuild
+++ b/dev-ruby/base64/base64-0.2.0.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-USE_RUBY="ruby31 ruby32"
+USE_RUBY="ruby31 ruby32 ruby33"
RUBY_FAKEGEM_BINWRAP=""
RUBY_FAKEGEM_EXTRADOC="README.md"
next reply other threads:[~2023-12-27 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 21:13 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 7:48 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/base64/ Hans de Graaff
2024-11-02 11:45 Arthur Zamarin
2024-10-30 15:46 Arthur Zamarin
2024-10-30 11:07 Sam James
2024-09-12 16:16 Jakov Smolić
2024-09-11 14:15 Sam James
2024-09-09 11:11 Sam James
2024-01-27 10:35 Hans de Graaff
2023-11-08 7:02 Hans de Graaff
2023-09-13 4:56 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=1703711606.fe4e851f9659669c414ddd6ad93e1852ac2f7408.graaff@gentoo \
--to=graaff@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