From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/hashery/
Date: Thu, 29 Jun 2023 20:13:56 +0000 (UTC) [thread overview]
Message-ID: <1688069632.2fd49ba9bc0ce3072bbec43f280c1f9d58e4a496.graaff@gentoo> (raw)
commit: 2fd49ba9bc0ce3072bbec43f280c1f9d58e4a496
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 29 20:13:35 2023 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Thu Jun 29 20:13:52 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2fd49ba9
dev-ruby/hashery: enable ruby32
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/hashery/hashery-2.1.2-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/hashery/hashery-2.1.2-r1.ebuild b/dev-ruby/hashery/hashery-2.1.2-r1.ebuild
index 6c9873cfe3e3..739644278ee6 100644
--- a/dev-ruby/hashery/hashery-2.1.2-r1.ebuild
+++ b/dev-ruby/hashery/hashery-2.1.2-r1.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-USE_RUBY="ruby27 ruby30 ruby31"
+USE_RUBY="ruby30 ruby31 ruby32"
RUBY_FAKEGEM_TASK_TEST=""
RUBY_FAKEGEM_RECIPE_DOC="yard"
next reply other threads:[~2023-06-29 20:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 20:13 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 6:49 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/hashery/ Hans de Graaff
2022-06-18 5:48 Hans de Graaff
2021-11-17 6:37 Hans de Graaff
2021-10-23 6:55 Hans de Graaff
2020-02-22 10:22 Hans de Graaff
2019-05-08 19:59 Hans de Graaff
2018-04-15 5:23 Hans de Graaff
2018-03-24 8:35 Hans de Graaff
2017-01-22 1:34 Manuel Rüger
2016-05-24 4:59 Hans de Graaff
2016-05-02 5:26 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=1688069632.2fd49ba9bc0ce3072bbec43f280c1f9d58e4a496.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