Ruby

Unfortunately, Ruby 3.1 is already EOL. There is no chance to fix that on ruby_3_1 branch and relase package.

If that issue happened with the current master HEAD, we should fix this for Ruby 3.5. Could you confirm that?

hsbt (Hiroshi SHIBATA) wrote in #note-1:

Unfortunately, Ruby 3.1 is already EOL. There is no chance to fix that on ruby_3_1 branch and relase package.

If that issue happened with the current master HEAD, we should fix this for Ruby 3.5. Could you confirm that?

Unfortunatly no, that means also that we can backport something from 3.3 or 3.5

Note that we need only a patch or even a reason why it regress, we know it is our work on distro side, but we need here help

Bastien

rouca (Bastien Roucaries) wrote in #note-2:

hsbt (Hiroshi SHIBATA) wrote in #note-1:

Unfortunately, Ruby 3.1 is already EOL. There is no chance to fix that on ruby_3_1 branch and relase package.

If that issue happened with the current master HEAD, we should fix this for Ruby 3.5. Could you confirm that?

Unfortunatly no, that means also that we can backport something from 3.3 or 3.5

Note that we need only a patch or even a reason why it regress, we know it is our work on distro side, but we need here help

Bastien
it's trying to load from /usr/lib/ruby/gems/3.1.0/extensions/x86_64-linux/... while the files are actually in /usr/lib/ruby/gems/3.1.0/extensions/x86_64-linux-gnu/...

Note that 3.3.7 load from /usr/lib/ruby/gems/3.1.0/extensions/x86_64-linux-gnu/

Could you close we have worked arround
https://salsa.debian.org/ruby-team/ruby/-/blob/9607233ec1ff78b721895bd9e822c24db304d49a/debian/patches/Gem-Platform-emulate-3.3.15-behavior-on-Ruby-3.1.patch