The reason I want to revert back to the system ruby is because I
installed the heroku gem, and it installed without problems:
$ sudo gem install heroku
Password:
Fetching: term-ansicolor-1.0.5.gem (100%)
Fetching: mime-types-1.16.gem (100%)
Fetching: rest-client-1.6.3.gem (100%)
Fetching: configuration-1.3.1.gem (100%)
Fetching: launchy-0.4.0.gem (100%)
Fetching: heroku-2.3.6.gem (100%)
Successfully installed term-ansicolor-1.0.5
Successfully installed mime-types-1.16
Successfully installed rest-client-1.6.3
Successfully installed configuration-1.3.1
Successfully installed launchy-0.4.0
Successfully installed heroku-2.3.6
6 gems installed
Installing ri documentation for term-ansicolor-1.0.5…
Installing ri documentation for mime-types-1.16…
Installing ri documentation for rest-client-1.6.3…
Installing ri documentation for configuration-1.3.1…
Installing ri documentation for launchy-0.4.0…
Installing ri documentation for heroku-2.3.6…
Installing RDoc documentation for term-ansicolor-1.0.5…
Installing RDoc documentation for mime-types-1.16…
Installing RDoc documentation for rest-client-1.6.3…
Installing RDoc documentation for configuration-1.3.1…
Installing RDoc documentation for launchy-0.4.0…
Installing RDoc documentation for heroku-2.3.6…
$
… but the “heroku version” command gave me a “heroku unrecognized”
error. So the heroku gem must have installed in some other gem
directory. Apparently, doing “gem install heroku” (without sudo)
succeeded in installing the heroku gem in the ruby 1.9.2 gem directory.
But now rvm system doesn’t work correctly.
The rvm docs say not to use the sudo command when installing gems–or
else strange things will happen. Now that strange things are happening,
how do I undo the problems?
strange error - until you find a real solution, you could use ‘rvm
list’ to manually select the version you want to use…
-j
No that doesn’t work. “rvm list” only produces the rubies installed
with rvm.
…of course, sorry for the bum lead - have you had any luck?
I did “rvm implode” to uninstall, which didn’t uninstall everything, so
I did a “rm -rf” on the .rvm directory. Then I reinstalled rvm and
various rubies again, but I had so many problems it took me many
uninstalls and many reinstalls before I could get rvm working again.
Now, I am
going to stay away from the “rvm system” command…and any commands
that start with “sudo”.
but I had so many problems it took me many
uninstalls and many reinstalls before I could get rvm working again.
Now, I am
going to stay away from the “rvm system” command…and any commands
that start with “sudo”.