RVM
doesn't behave well if apt-get update
has errors. If your apt
sources
have an invalid repository that gives 404 or GPG error, RVM
will refuse to work. This can be confusing because it happens even if the faulty repository has nothing to do with ruby
or RVM
.
The following fix worked for me (Ubuntu):
Run apt-get update
and see if there are any errors. Edit your sources.list
and precise.list
in /etc/apt
to remove the faulty repositories. Repeat until apt-get update
succeeds without any errors. Then try running RVM
.