9.4.12.0 unable to build itself #8634
Description
I'm currently working to update the packaging for JRuby in Debian, which currently ships 9.4.8.0. I'm able to successfully build 9.4.12.0, but I'm hitting an issue when using 9.4.12.0 in the JRuby build environment.
[INFO] --- polyglot:0.4.11:execute (install_gems) @ jruby-stdlib ---
using jruby 9.4.12.0
install gems unless already installed
/build/reproducible-path/jruby-9.4.12.0+ds/debian/maven-repo/rubygems/rubygems-update/3.5.0/rubygems-update-3.5.0.gem
Exception while verifying /build/reproducible-path/jruby-9.4.12.0+ds/debian/maven-repo/rubygems/rubygems-update/3.5.0/rubygems-update-3.5.0.gem
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for JRuby 9.4.12.0:
[INFO]
[INFO] JRuby .............................................. SUCCESS [ 0.104 s]
[INFO] JRuby Base ......................................... SUCCESS [ 19.878 s]
[INFO] JRuby Core ......................................... SUCCESS [ 6.332 s]
[INFO] JRuby Lib Setup .................................... FAILURE [ 0.365 s]
[INFO] JRuby Artifacts .................................... SKIPPED
[INFO] JRuby Main Maven Artifact .......................... SKIPPED
[INFO] JRuby Complete ..................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 29.303 s
[INFO] Finished at: 2025-02-17T18:01:26Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.takari.polyglot:polyglot-maven-plugin:0.4.11:execute (install_gems) on project jruby-stdlib: org.jruby.exceptions.NameError: (NameError) uninitialized constant Gem::Security::Open
SSL -> [Help 1]
I'm tracked it down the problem to the rubygems-update upgrade to 3.6.3 in c4e369d. If I revert the gem to 3.3.26, then it builds with itself just fine.
I was able to further narrow it down to a change that was introduced in rubygems 3.5.0 specifically. From this version on, the failure occurs, while it doesn't when using 3.4.22 or earlier.
This seems similar to the problem described in these rubygems PRs: