You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometime between 1.24.12 and 1.26.10 rvm install removes gem preferences. This has a bad side-effect where running a bundle post rvm install won't install into the proper gemset.
1.24.12 RVM Behavior
QA jenkins@jenkins01.qa:~$
rvm --version
rvm 1.24.12 (1.24.12) by Wayne E. Seguin <wayneeseguin@gmail.com>, Michal Papis <mpapis@gmail.com> [https://rvm.io/]
QA jenkins@jenkins01.qa:~$
cd authy/
QA jenkins@jenkins01.qa:~/authy (Jenkins@master)$
rvm info | head -2
ruby-2.0.0-p353@authy:
QA jenkins@jenkins01.qa:~/authy (Jenkins@master)$
rvm install ruby-2.0.0-p353
Warning, new version of rvm available '1.26.10', you are using older version '1.24.12'.
You can disable this warning with: echo rvm_autoupdate_flag=0 >> ~/.rvmrc
You can enable auto-update with: echo rvm_autoupdate_flag=2 >> ~/.rvmrc
Already installed ruby-2.0.0-p353.
To reinstall use:
rvm reinstall ruby-2.0.0-p353
QA jenkins@jenkins01.qa:~/authy (Jenkins@master)$
rvm info | head -2
ruby-2.0.0-p353@authy:
1.26.10 RVM Behavior
QA jenkins@jenkins01.qa:~/authy (Jenkins@master)$
rvm --version
rvm 1.26.10 (1.26.10) by Wayne E. Seguin <wayneeseguin@gmail.com>, Michal Papis <mpapis@gmail.com> [https://rvm.io/]
QA jenkins@jenkins01.qa:~/authy (Jenkins@master)$
rvm info | head -2
ruby-2.0.0-p353@authy:
QA jenkins@jenkins01.qa:~/authy (Jenkins@master)$
rvm install ruby-2.0.0-p353
Already installed ruby-2.0.0-p353.
To reinstall use:
rvm reinstall ruby-2.0.0-p353
QA jenkins@jenkins01.qa:~/authy (Jenkins@master)$
rvm info | head -2
ruby-2.0.0-p353:
The text was updated successfully, but these errors were encountered:
Sometime between 1.24.12 and 1.26.10
rvm install
removes gem preferences. This has a bad side-effect where running abundle
postrvm install
won't install into the proper gemset.1.24.12 RVM Behavior
1.26.10 RVM Behavior
The text was updated successfully, but these errors were encountered: