-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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 install ruby-2.2.x in Centos 6.9 from rvm master without rvmsudo #4358
Comments
OK, weird, I tried ruby-2.3.7, ruby-2.4.4, and ruby-2.5.1, and they all installed without this error. And then afterwards, when I tried to install ruby-2.2.10 again, it worked. I'm going to try other machines with the same setup. |
I tried on other systems:
So it looks like the problem is specific to ruby-2.2.x versions, and installing a version not-2.2.x first in the same login session makes later 2.2.x installs succeed. It's possible that the reason it didn't fail in Centos 7.4.1708 is because before I installed 2.2.10, I installed 2.1.2 first. That makes more sense than it being a Centos 6 vs 7 issue. |
Checked on a Centos 7.4.1708 box in a fresh session, and it failed with the same failure. |
OK, figured it out: ruby-2.2.0 to 2.2.4 installs correctly, but 2.2.5 to 2.2.10 doesn't. Looks like the ruby 798 and rvm #3259 patch needs to apply to later 2.2.x versions. Making a PR. |
Copied the ruby-2.2.4 patch to ruby-2.2.5 to ruby-2.2.10. Fixes rvm#4358 .
Note that it doesn't fail on my single-user rvm install. I think it's limited to multi-user rvm. |
Description
After updating rvm to master with rvmsudo (see #4356), I try to install a ruby version without rvmsudo, and it fails, complaining about a file in the current ruby version's directory - not the version to be installed. Seen in Centos 6.9 and 7.4.1708.
Steps to reproduce
Expected behavior
I expect ruby-2.2.10 to be installed without errors.
Actual behavior
The error is at the end of install.log:
Environment info
The text was updated successfully, but these errors were encountered: