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/uglifier/
Date: Sat,  1 Apr 2023 23:19:54 +0000 (UTC)	[thread overview]
Message-ID: <1680391128.ce31453befd770351bd8eb5d7143828362865a4e.sam@gentoo> (raw)

commit:     ce31453befd770351bd8eb5d7143828362865a4e
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Apr  1 22:34:37 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Apr  1 23:18:48 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ce31453b

dev-ruby/uglifier: enable ruby32

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

 dev-ruby/uglifier/uglifier-4.2.0-r1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-ruby/uglifier/uglifier-4.2.0-r1.ebuild b/dev-ruby/uglifier/uglifier-4.2.0-r1.ebuild
index 63f46cb9ffcb..81cdce0fd6e0 100644
--- a/dev-ruby/uglifier/uglifier-4.2.0-r1.ebuild
+++ b/dev-ruby/uglifier/uglifier-4.2.0-r1.ebuild
@@ -1,8 +1,8 @@
-# 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_RECIPE_TEST="rspec3"
 


             reply	other threads:[~2023-04-01 23:19 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 23:19 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-23  5:37 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/uglifier/ Hans de Graaff
2023-12-31  8:21 Hans de Graaff
2023-04-07 18:25 Sam James
2022-06-25  6:07 Hans de Graaff
2022-06-13  8:06 Yixun Lan
2022-04-17  6:57 Hans de Graaff
2022-03-26 14:30 Hans de Graaff
2020-07-22 13:44 Hans de Graaff
2020-06-02  4:49 Hans de Graaff
2019-11-03  9:28 Hans de Graaff
2019-09-29  9:07 Hans de Graaff
2019-05-13 16:44 Mikle Kolyada
2019-05-05  6:32 Hans de Graaff
2018-11-22  6:17 Hans de Graaff
2018-11-22  6:17 Hans de Graaff
2018-09-17  6:14 Hans de Graaff
2018-08-19  5:09 Hans de Graaff
2018-08-19  5:09 Hans de Graaff
2018-08-09  5:18 Hans de Graaff
2018-07-28  4:47 Hans de Graaff
2018-07-16  6:19 Hans de Graaff
2018-07-04 20:56 Hans de Graaff
2018-07-03  4:24 Hans de Graaff
2018-06-21  4:42 Hans de Graaff
2018-06-12  5:14 Hans de Graaff
2018-06-02  6:01 Hans de Graaff
2018-04-22  4:30 Hans de Graaff
2018-04-13  6:20 Hans de Graaff
2018-03-25 17:58 Sergei Trofimovich
2018-03-23  5:47 Hans de Graaff
2018-03-23  5:47 Hans de Graaff
2018-03-18 12:57 Sergei Trofimovich
2018-02-16  7:34 Hans de Graaff
2018-02-16  7:34 Hans de Graaff
2018-01-29  6:30 Hans de Graaff
2018-01-22  6:44 Hans de Graaff
2018-01-22  6:44 Hans de Graaff
2018-01-08 23:57 Thomas Deutschmann
2018-01-05  6:50 Hans de Graaff
2017-12-29  5:18 Hans de Graaff
2017-12-11  6:24 Hans de Graaff
2017-12-04  6:07 Hans de Graaff
2017-12-03  6:42 Hans de Graaff
2017-12-03  6:42 Hans de Graaff
2017-07-02  5:43 Hans de Graaff
2017-07-02  5:43 Hans de Graaff
2017-07-02  5:43 Hans de Graaff
2017-07-01 13:45 Alexis Ballier
2017-04-11  5:48 Hans de Graaff
2017-04-03  5:09 Hans de Graaff
2017-03-21 16:55 Hans de Graaff
2017-03-16  5:55 Hans de Graaff
2017-03-11  7:21 Hans de Graaff
2017-03-05  7:20 Hans de Graaff
2017-03-01  6:05 Hans de Graaff
2017-03-01  6:05 Hans de Graaff
2016-12-04  6:52 Hans de Graaff
2016-11-09  0:41 Manuel Rüger
2016-10-26  5:32 Hans de Graaff
2016-10-26  5:32 Hans de Graaff
2016-08-21  6:02 Hans de Graaff
2016-07-30  5:23 Hans de Graaff
2016-05-21  7:59 Markus Meier
2016-05-18  8:45 Fabian Groffen
2016-05-13  5:18 Hans de Graaff
2016-03-28 21:48 Manuel Rüger
2016-03-07  2:49 Manuel Rüger
2015-08-27  6:00 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=1680391128.ce31453befd770351bd8eb5d7143828362865a4e.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