Thank you for the report, this was already fixed in cauldron during the update to ruby 3, I'll have a look at fixing it on Mageia 8.

Source RPM: ruby-json-2.3.0-33.4.mga8.aarch64.rpm => ruby-2.7.6-33.4.mga8.src.rpm

-33.5.mga8 is currently being built for 8/updates_testing

ruby-2.7.6-33.5.mga8
libruby2.7-2.7.6-33.5.mga8
ruby-rdoc-6.2.1.1-33.5.mga8
ruby-devel-2.7.6-33.5.mga8
ruby-bundler-2.2.24-33.5.mga8
ruby-RubyGems-3.1.2-33.5.mga8
ruby-test-unit-3.3.4-33.5.mga8
ruby-openssl-2.1.3-33.5.mga8
ruby-rake-13.0.1-33.5.mga8
ruby-irb-2.7.6-33.5.mga8
ruby-psych-3.1.0-33.5.mga8
ruby-bigdecimal-2.0.0-33.5.mga8
ruby-json-2.3.0-33.5.mga8
ruby-xmlrpc-0.3.0-33.5.mga8
ruby-io-console-0.5.6-33.5.mga8
ruby-net-telnet-0.2.0-33.5.mga8
ruby-power_assert-1.1.7-33.5.mga8
ruby-did_you_mean-1.4.0-33.5.mga8
ruby-doc-2.7.6-33.5.mga8

from ruby-2.7.6-33.5.mga8.src.rpm

Assignee: pterjan => qa-bugs
CC: (none) => pterjan

mga8, x64

Installed all the pre-update packages.
Not a rails user but tried the installation command:
$ bundle exec rake generate_session_store redmine
Could not locate Gemfile or .bundle/ directory

as user and root.  Not unexpected.

/usr/share/gems/gems/json-2.3.0/lib/json is not a link and nor is the json.rb file.

Updated all the packages (lib64ruby2.7).
As indicated, the redmine installation failed so I have to accept that that cannot be tested on this system without further refinements.

Quick script to show ruby-json working :
see https://linuxhint.com/parse-json-in-ruby/ 
-------------------------------------------
#!/bin/ruby -W0
require "json"

raw_data = File.read( "/usr/share/doc/perl-XString/META.json" )
datahash = JSON.parse( raw_data )
datahash.each { |entry| p entry }
-------------------------------------------

This generates a lot of output:
["abstract", "Isolated String helpers from B"]
["author", ["Nicolas R <atoomic@cpan.org>"]]
["dynamic_config", 0]
["generated_by", "Dist::Zilla version 6.014, CPAN::Meta::Converter version 2.150010"]
["license", ["perl_5"]]
["meta-spec", {"url"=>"http://search.cpan.org/perldoc?CPAN::Meta::Spec", "version"=>2}]
["name", "XString"]
["prereqs", {"configure"=>{"requires"=>{"ExtUtils::MakeMaker"=>"0"}}, "develop"=
.........
["x_generated_by_perl", "v5.30.1"]
["x_serialization_backend", "Cpanel::JSON::XS version 4.19"]
["x_spdx_expression", "Artistic-1.0-Perl OR GPL-1.0-or-later"]

Add "puts datahash.keys":
abstract
author
dynamic_config
generated_by
license
[...]
version
x_Dist_Zilla
x_generated_by_perl
x_serialization_backend
x_spdx_expression

JSON data can be created OK:
----------------------------
require 'json'

this_hash = {:name => "John Doe", :age => 30, :role => "Python Programmer", :group => "AX-100", :Country => "United States"}
jsonified = JSON.generate(this_hash)

puts jsonified
----------------------------
$ ruby qajson.rb
{"name":"John Doe","age":30,"role":"Python Programmer","group":"AX-100","Country":"United States"}

Passing this on the basis of a clean install and "it works".

CC: (none) => tarazed25
Whiteboard: (none) => MGA8-64-OK

Validating.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

With apologies to Jean-Georges, just realised that these tests do not address the original problem.  Maybe we should put this on hold until Jean-Georges has tried it out and reported back.

No problem,
Where can i find these packages to test them

Removing validation for now because of Comment 6.

Keywords: validated_update => (none)

Referring to comment 8, thanks TJ
With reference to comment 7, the update candidates are in Core Updates Testing.
You would actually have to follow QA procedures to use them.  QA is meant to undertake any needed testing before clearing the packages for release but many times we do not have the expertise to tackle particular issues, as in this case.
Using `gem install redmine` works here but delivers redmine version 0.1.4, while you are looking for a much newer version.

It may be that wiser heads could give you better advice than the following - it is the best I can come up with.

Assuming you have the release versions of the ruby packages installed you could either follow the instructions for setting up qarepo (https://wiki.mageia.org/en/QA_Repo) or do it the old way (not recommended), which is to enable Core Updates Testing via
$ sudo drakrpm-edit-media
$ urpmi.update -a
$ drakrpm-update (give user password)

That sounds like too much to ask.  An alternative would be for you to to supply us with enough information, links etcetera, to do the test ourselves.

Failing that we would have to revert to waiting for the update to be pushed and let you try again.

No, comment 9 was a brain fart.  QA should not be treading in developer territory.  Replacing the validation.  Apologies.

Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0090.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED