New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix unknown command wrappers #5027
Conversation
Rubygems plugin loading was changed in rubygems >= 3.2 this leads to gem-wrappers not being loaded in a new context. This fix registers the gem-wrappers plugin before its being used. See rubygems/rubygems#3108
7b5d063
to
860efb3
Compare
@pkuczynski @mpapis Happy to see this merged asap 🎉 🎉 Thanks @wintersolutions ! 🤝 c/c: @WillRadi |
@pkuczynski @mpapis I've tested locally the branch, and it worked like a charm 🎉 Ruby 3 installed correctly 🤝 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@pkuczynski When you have time, could you release a minor version of rvm for us? 🤝 We are waiting a official release with this hotfix to upgrade rvm and install ruby3 in our production environments 👍 🏆 Ps: Thanks again @wintersolutions ! 🎖️ |
Thanks! |
I tried multiple clean installs of debian10, and I'm getting this after this change:
|
@teeigeryuh Take a look on this PR that I've created. Thanks for feedback!: #5029 |
Rubygems plugin loading was changed in
rubygems >= 3.2 this leads to gem-wrappers
not being loaded in a new context.
This fix registers the gem-wrappers plugin before its
being used.
See rubygems/rubygems#3108
Fixes #5020.
Changes proposed in this pull request:
gem pristine gem-wrappers --only-plugins
before runninggem wrappers regenerate
to avoid plugin loading issues with rubygems >= 3.2Make sure that your pull request includes entry in the CHANGELOG.