-
Notifications
You must be signed in to change notification settings - Fork 584
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
Can't create RVM wrappers since RubyGems 3.2.18 #475
Comments
Sorry, I don't use RVM any more. But it sounds like a bug in RVM? |
This still seems to be working for me, too:
Results in a whole lot of output, and then:
|
That's a nice quick way to test! I followed the same steps as you and got the same result. The missing step is to ensure RubyGems is at the correct version. Ruby 2.7.4 installs RubyGems .... # execute all the previous steps
rvm install 2.7.4
gem update --system 3.2.18 # new
rvm default@mailcatcher --create do gem install mailcatcher --no-document # --no-document speeds-up this step
ln -s "$(rvm default@mailcatcher do rvm wrapper show mailcatcher)" "$rvm_bin_path/"
# error That should trigger the error. After that, you can switch to 3.2.17 and try again without having to start at the top: rvm gemset delete mailcatcher
gem update --system 3.2.17
rvm default@mailcatcher --create do gem install mailcatcher --no-document
ln -s "$(rvm default@mailcatcher do rvm wrapper show mailcatcher)" "$rvm_bin_path/"
mailcatcher --version # => MailCatcher v0.8.0 |
Ah yep, I can replicate with those commands. But it does look like a bug within rvm, or gem-wrappers. Isolated:
It remains in the latest version of rubygems, 3.2.24, as well. |
Reported to rvm/gem-wrappers#15, please track there for a fix |
Thanks for taking a look so quickly! |
The README recommends executing the following for RVM.
The above code works great with RubyGems 3.2.17. 3.2.18 introduced a change that causes the
ln -s ...
line to raise the following error:The .log file contains:
The error seems to occur with all versions of RubyGems from 3.2.18 to at least 3.2.24 (which is currently the latest version). I'm using the following to test:
Ubuntu 20.04 and 18.04
RVM 1.29.12
Ruby 2.7.4
Does mailcather need to update to match RubyGems, or is this a regression in RubyGems?
The text was updated successfully, but these errors were encountered: