From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/ruby-hmac/
Date: Tue, 31 Dec 2024 11:39:05 +0000 (UTC) [thread overview]
Message-ID: <1735645122.e4a3e1201b23130e9192da5f4e865fecf66b9183.graaff@gentoo> (raw)
commit: e4a3e1201b23130e9192da5f4e865fecf66b9183
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 31 11:25:33 2024 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Tue Dec 31 11:38:42 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e4a3e120
dev-ruby/ruby-hmac: enable ruby34
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/ruby-hmac/ruby-hmac-0.4.0-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/ruby-hmac/ruby-hmac-0.4.0-r2.ebuild b/dev-ruby/ruby-hmac/ruby-hmac-0.4.0-r2.ebuild
index 713c1da14f64..c8e4d16a6a19 100644
--- a/dev-ruby/ruby-hmac/ruby-hmac-0.4.0-r2.ebuild
+++ b/dev-ruby/ruby-hmac/ruby-hmac-0.4.0-r2.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-USE_RUBY="ruby31 ruby32 ruby33"
+USE_RUBY="ruby31 ruby32 ruby33 ruby34"
RUBY_FAKEGEM_EXTRADOC="History.txt README.txt"
next reply other threads:[~2024-12-31 11:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 11:39 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-09 15:51 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/ruby-hmac/ Hans de Graaff
2023-06-24 20:35 Hans de Graaff
2022-05-26 10:36 Hans de Graaff
2021-11-26 8:17 Hans de Graaff
2021-11-24 6:37 Hans de Graaff
2020-07-26 9:15 Hans de Graaff
2019-03-15 7:13 Hans de Graaff
2018-02-10 7:42 Hans de Graaff
2017-07-31 5:32 Hans de Graaff
2016-12-25 6:55 Hans de Graaff
2016-03-28 22:03 Manuel Rüger
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=1735645122.e4a3e1201b23130e9192da5f4e865fecf66b9183.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