From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] package/ruby: bump to 4.0.2
Date: Mon, 23 Mar 2026 07:34:05 +0100 [thread overview]
Message-ID: <acDe3WDkqsQZlkOK@waldemar-brodkorb.de> (raw)
See here for news in the release:
https://www.ruby-lang.org/en/news/2026/03/16/ruby-4-0-2-released/
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/ruby/ruby.hash | 4 ++--
package/ruby/ruby.mk | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/ruby/ruby.hash b/package/ruby/ruby.hash
index bd64f97339..9908fe8d4f 100644
--- a/package/ruby/ruby.hash
+++ b/package/ruby/ruby.hash
@@ -1,5 +1,5 @@
-# https://www.ruby-lang.org/en/news/2026/01/13/ruby-4-0-1-released/
-sha256 0531fe57dfdb56bf591620d2450642ea0e0964f3512a6ebee7dc9305de69395f ruby-4.0.1.tar.xz
+# https://www.ruby-lang.org/en/news/2026/03/16/ruby-4-0-2-released/
+sha256 4618db85bb9ec04d8152d0099db488694a3d3c4f52106625e4ad547f1318db87 ruby-4.0.2.tar.xz
# License files, Locally calculated
sha256 a74812486cffbdc55141a5d9f165d782cbb202660d827622ec966237d4717b99 LEGAL
diff --git a/package/ruby/ruby.mk b/package/ruby/ruby.mk
index 5e8b40a556..6bd8ad43c5 100644
--- a/package/ruby/ruby.mk
+++ b/package/ruby/ruby.mk
@@ -5,7 +5,7 @@
################################################################################
RUBY_VERSION_MAJOR = 4.0
-RUBY_VERSION = $(RUBY_VERSION_MAJOR).1
+RUBY_VERSION = $(RUBY_VERSION_MAJOR).2
RUBY_VERSION_EXT = 4.0.0
RUBY_SITE = http://cache.ruby-lang.org/pub/ruby/$(RUBY_VERSION_MAJOR)
RUBY_SOURCE = ruby-$(RUBY_VERSION).tar.xz
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-03-23 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 6:34 Waldemar Brodkorb [this message]
2026-03-23 20:09 ` [Buildroot] [PATCH] package/ruby: bump to 4.0.2 Julien Olivain via buildroot
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=acDe3WDkqsQZlkOK@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.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