From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/nanoc-checking/
Date: Sun, 28 Apr 2024 08:35:44 +0000 (UTC) [thread overview]
Message-ID: <1714293325.4f63850e0032fe9c53dbd12803435a964d2ec47b.graaff@gentoo> (raw)
commit: 4f63850e0032fe9c53dbd12803435a964d2ec47b
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 28 08:34:43 2024 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Apr 28 08:35:25 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4f63850e
www-apps/nanoc-checking: enable ruby33
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
www-apps/nanoc-checking/nanoc-checking-1.0.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www-apps/nanoc-checking/nanoc-checking-1.0.5.ebuild b/www-apps/nanoc-checking/nanoc-checking-1.0.5.ebuild
index 1c01dd15800d..5ee44c580eef 100644
--- a/www-apps/nanoc-checking/nanoc-checking-1.0.5.ebuild
+++ b/www-apps/nanoc-checking/nanoc-checking-1.0.5.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"
# Upstream has specs but they are not available in the gem and the
# repository upstream is not tagged for this.
next reply other threads:[~2024-04-28 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 8:35 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-22 5:55 [gentoo-commits] repo/gentoo:master commit in: www-apps/nanoc-checking/ Hans de Graaff
2024-04-22 5:55 Hans de Graaff
2024-04-20 7:47 Hans de Graaff
2024-03-17 8:17 Hans de Graaff
2023-08-11 19:14 Hans de Graaff
2023-06-25 5:51 Hans de Graaff
2022-12-07 17:57 Hans de Graaff
2022-08-23 5:34 Sam James
2022-05-29 5:50 Hans de Graaff
2022-04-10 5:06 Hans de Graaff
2022-03-18 6:50 Jakov Smolić
2021-07-11 7:10 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=1714293325.4f63850e0032fe9c53dbd12803435a964d2ec47b.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