From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rspec-rails/
Date: Fri, 7 Apr 2023 18:11:12 +0000 (UTC) [thread overview]
Message-ID: <1680890992.5e9d812c1f603680e2e35529af9095d6c49e8671.sam@gentoo> (raw)
commit: 5e9d812c1f603680e2e35529af9095d6c49e8671
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 7 17:41:31 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 7 18:09:52 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e9d812c
dev-ruby/rspec-rails: enable ruby31
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ruby/rspec-rails/rspec-rails-6.0.1.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-ruby/rspec-rails/rspec-rails-6.0.1.ebuild b/dev-ruby/rspec-rails/rspec-rails-6.0.1.ebuild
index 3b74b2332a99..41b8a0ee96f0 100644
--- a/dev-ruby/rspec-rails/rspec-rails-6.0.1.ebuild
+++ b/dev-ruby/rspec-rails/rspec-rails-6.0.1.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-USE_RUBY="ruby27 ruby30"
+USE_RUBY="ruby27 ruby30 ruby31"
RUBY_FAKEGEM_RECIPE_TEST="rspec3"
next reply other threads:[~2023-04-07 18:11 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 18:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-15 9:48 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rspec-rails/ Hans de Graaff
2024-11-24 8:07 Hans de Graaff
2024-11-15 11:13 Hans de Graaff
2024-11-15 11:13 Hans de Graaff
2024-07-17 9:38 Hans de Graaff
2024-06-21 11:21 Hans de Graaff
2024-03-31 6:41 Hans de Graaff
2024-03-20 12:04 Hans de Graaff
2024-02-09 7:49 Hans de Graaff
2023-11-23 7:09 Hans de Graaff
2023-08-29 14:26 Hans de Graaff
2023-08-16 6:14 Hans de Graaff
2023-08-13 8:40 Hans de Graaff
2023-08-13 5:22 Hans de Graaff
2023-07-17 4:55 Hans de Graaff
2023-07-12 18:53 Hans de Graaff
2023-06-18 4:53 Hans de Graaff
2023-06-12 6:21 Hans de Graaff
2023-05-05 8:22 Hans de Graaff
2023-04-14 5:54 Hans de Graaff
2023-03-13 7:14 Hans de Graaff
2022-12-04 10:14 Hans de Graaff
2022-10-20 5:12 Hans de Graaff
2022-10-11 5:31 Hans de Graaff
2022-07-25 5:42 Hans de Graaff
2022-06-26 6:20 Hans de Graaff
2022-05-15 7:50 Hans de Graaff
2022-04-25 5:23 Hans de Graaff
2022-04-12 17:21 Hans de Graaff
2022-01-28 7:06 Hans de Graaff
2021-10-23 6:55 Hans de Graaff
2021-08-16 5:34 Hans de Graaff
2021-07-18 5:40 Hans de Graaff
2021-07-07 6:53 Hans de Graaff
2021-07-07 6:53 Hans de Graaff
2021-07-04 6:18 Hans de Graaff
2021-03-18 6:20 Hans de Graaff
2020-12-29 6:54 Hans de Graaff
2020-09-09 9:28 Hans de Graaff
2020-05-17 5:10 Hans de Graaff
2020-03-25 8:53 Hans de Graaff
2020-03-25 5:52 Hans de Graaff
2020-03-14 11:04 Hans de Graaff
2019-11-02 10:03 Hans de Graaff
2019-05-06 17:58 Hans de Graaff
2019-04-11 17:46 Hans de Graaff
2019-01-21 6:49 Hans de Graaff
2018-12-11 11:34 Hans de Graaff
2018-10-24 6:27 Hans de Graaff
2018-09-22 6:02 Hans de Graaff
2018-08-05 7:05 Hans de Graaff
2018-08-05 6:42 Hans de Graaff
2018-02-24 8:49 Hans de Graaff
2018-01-25 6:34 Hans de Graaff
2018-01-22 20:25 Hans de Graaff
2017-12-09 7:55 Hans de Graaff
2017-12-03 8:31 Hans de Graaff
2017-11-22 6:10 Hans de Graaff
2017-10-21 5:47 Hans de Graaff
2017-08-12 5:14 Hans de Graaff
2017-08-06 5:48 Hans de Graaff
2017-06-25 7:58 Hans de Graaff
2017-06-25 7:58 Hans de Graaff
2017-05-06 5:10 Hans de Graaff
2017-04-21 5:07 Hans de Graaff
2016-12-25 23:21 Manuel Rüger
2016-09-04 6:47 Hans de Graaff
2016-08-26 5:04 Hans de Graaff
2016-07-21 19:38 Hans de Graaff
2016-07-10 5:33 Hans de Graaff
2016-07-03 5:49 Hans de Graaff
2016-04-16 22:04 Manuel Rüger
2016-03-06 19:42 Hans de Graaff
2016-02-04 6:36 Hans de Graaff
2015-11-14 10:13 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=1680890992.5e9d812c1f603680e2e35529af9095d6c49e8671.sam@gentoo \
--to=sam@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