From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rbst/
Date: Sat, 26 Aug 2023 19:07:55 +0000 (UTC) [thread overview]
Message-ID: <1693076869.34b9c8a25981a19e84ee7137b1ca329b8787dcce.graaff@gentoo> (raw)
commit: 34b9c8a25981a19e84ee7137b1ca329b8787dcce
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 26 18:47:35 2023 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Aug 26 19:07:49 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=34b9c8a2
dev-ruby/rbst: enable ruby32
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/rbst/rbst-0.6.5-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/rbst/rbst-0.6.5-r1.ebuild b/dev-ruby/rbst/rbst-0.6.5-r1.ebuild
index dbf9f7fa6bdb..8b44aba69e0c 100644
--- a/dev-ruby/rbst/rbst-0.6.5-r1.ebuild
+++ b/dev-ruby/rbst/rbst-0.6.5-r1.ebuild
@@ -4,7 +4,7 @@
EAPI=8
PYTHON_COMPAT=( python3_{9..11} )
-USE_RUBY="ruby26 ruby27 ruby30 ruby31"
+USE_RUBY="ruby30 ruby31 ruby32"
RUBY_FAKEGEM_NAME="RbST"
RUBY_FAKEGEM_GEMSPEC="RbST.gemspec"
next reply other threads:[~2023-08-26 19:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 19:07 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-03 9:12 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rbst/ Hans de Graaff
2023-08-26 19:07 Hans de Graaff
2022-09-04 10:54 Hans de Graaff
2022-05-20 5:47 Hans de Graaff
2022-05-18 7:36 Michał Górny
2020-09-18 9:38 Michał Górny
2020-08-10 13:24 Michał Górny
2020-02-10 11:54 Michał Górny
2019-07-21 5:43 Hans de Graaff
2019-03-29 12:28 Hans de Graaff
2018-09-09 14:32 Hans de Graaff
2018-07-23 9:25 Michał Górny
2018-07-23 9:25 Michał Górny
2017-10-09 19:43 Michał Górny
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=1693076869.34b9c8a25981a19e84ee7137b1ca329b8787dcce.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