public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/sexp_processor/
Date: Mon, 27 Mar 2023 09:15:43 +0000 (UTC)	[thread overview]
Message-ID: <1679908466.dd3a6da76ef3e7983d9d71adaaf7f2e3c8f4270a.sam@gentoo> (raw)

commit:     dd3a6da76ef3e7983d9d71adaaf7f2e3c8f4270a
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 27 08:57:17 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Mar 27 09:14:26 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dd3a6da7

dev-ruby/sexp_processor: enable ruby32

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-ruby/sexp_processor/sexp_processor-4.16.1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-ruby/sexp_processor/sexp_processor-4.16.1.ebuild b/dev-ruby/sexp_processor/sexp_processor-4.16.1.ebuild
index c27d8b477f73..cc3eb63c3fb8 100644
--- a/dev-ruby/sexp_processor/sexp_processor-4.16.1.ebuild
+++ b/dev-ruby/sexp_processor/sexp_processor-4.16.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="ruby26 ruby27 ruby30 ruby31"
+USE_RUBY="ruby27 ruby30 ruby31 ruby32"
 
 RUBY_FAKEGEM_DOCDIR="doc"
 RUBY_FAKEGEM_EXTRADOC="README.rdoc History.rdoc"


             reply	other threads:[~2023-03-27  9:15 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  9:15 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-12 10:46 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/sexp_processor/ Hans de Graaff
2024-11-12 10:46 Hans de Graaff
2024-07-10  5:08 Hans de Graaff
2024-05-31 13:41 Arthur Zamarin
2024-05-31 10:46 Arthur Zamarin
2024-05-28  4:54 Hans de Graaff
2024-01-19 17:57 Hans de Graaff
2023-12-27  9:36 Hans de Graaff
2023-05-06  6:06 Hans de Graaff
2023-03-31  1:03 Sam James
2022-12-04  7:21 Hans de Graaff
2022-07-22  7:44 Agostino Sarubbo
2022-07-22  7:43 Agostino Sarubbo
2022-04-10  4:56 Hans de Graaff
2022-04-02  5:56 Hans de Graaff
2021-12-11  6:04 Hans de Graaff
2021-12-07  6:22 Agostino Sarubbo
2021-12-06 15:23 Sam James
2021-12-06  8:19 Hans de Graaff
2021-10-29  6:03 Hans de Graaff
2021-05-21  5:07 Hans de Graaff
2021-01-17  7:42 Hans de Graaff
2021-01-17  7:42 Hans de Graaff
2020-09-24  6:46 Agostino Sarubbo
2020-09-21 18:53 Sergei Trofimovich
2020-09-18 10:07 Agostino Sarubbo
2020-09-09  5:27 Hans de Graaff
2020-07-25 17:10 Hans de Graaff
2020-06-12  5:50 Hans de Graaff
2020-03-09  6:32 Hans de Graaff
2020-02-08  7:52 Hans de Graaff
2020-02-02 15:47 Hans de Graaff
2019-09-27  4:41 Hans de Graaff
2019-06-04  5:42 Hans de Graaff
2019-05-11  7:15 Hans de Graaff
2019-04-20 17:57 Mikle Kolyada
2019-04-17 20:01 Sergei Trofimovich
2019-04-14 16:18 Mikle Kolyada
2019-04-13 14:18 Mikle Kolyada
2019-04-10 17:27 Hans de Graaff
2019-03-13  7:03 Hans de Graaff
2019-01-25  6:10 Hans de Graaff
2018-04-21  4:56 Hans de Graaff
2018-02-24  7:19 Hans de Graaff
2018-02-13  6:33 Hans de Graaff
2017-12-22  5:38 Hans de Graaff
2017-12-21 19:28 Markus Meier
2017-11-09 22:37 Sergei Trofimovich
2017-10-22  7:06 Hans de Graaff
2017-10-22  7:06 Hans de Graaff
2017-07-18  4:56 Hans de Graaff
2017-04-15  6:06 Hans de Graaff
2017-02-02  7:07 Hans de Graaff
2017-01-15  7:01 Hans de Graaff
2016-11-27  8:13 Hans de Graaff
2016-11-06 10:12 Hans de Graaff
2016-10-02  8:42 Jeroen Roovers
2016-09-23 17:40 Tobias Klausmann
2016-08-06 11:12 Markus Meier
2016-07-22  7:05 Hans de Graaff
2016-02-19  6:03 Hans de Graaff
2016-01-22  7:55 Hans de Graaff
2016-01-22  7:55 Hans de Graaff
2015-08-26 11:55 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=1679908466.dd3a6da76ef3e7983d9d71adaaf7f2e3c8f4270a.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