I'm trying to get a Ruby on Rails project running on my Mac OS Sierra (10.13.3) machine. When I navigate to the Rails folder, RVM tells me the following:
Required ruby-1.9.3-p392 is not installed.
To install do: 'rvm install "ruby-1.9.3-p392"'
However, when I do that install, I get the following:
$ rvm install "ruby-1.9.3-p392"
Searching for binary rubies, this might take some time.
No binary rubies available for: osx/10.13/x86_64/ruby-1.9.3-p392.
Continuing with compilation. Please read 'rvm help mount' to get more information on binary rubies.
Checking requirements for osx.
Installing requirements for osx.
Updating system..........
Installing required custom packages: homebrew/versions.
Error running 'requirements_osx_brew_install_custom homebrew/versions',
please read /Users/petercormack/.rvm/log/1518211184_ruby-1.9.3-p392/install_custom.log
Requirements installation failed with status: 1.
When I look at that log file, I see the following:
[2018-02-09 12:36:30] requirements_osx_brew_install_custom
requirements_osx_brew_install_custom ()
{
\typeset __tap;
for __tap in "$@";
do
brew tap "${__tap}" || return $?;
done
}
current path: /Users/petercormack/podcastsi18n
PATH=/usr/local/opt/qt@5.5/bin:/Users/petercormack/.node/bin:/usr/local/bin:/Applications/Postgres.app/Contents/Versions/latest/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/petercormack/.rvm/bin:/usr/local/Cellar/openssl/1.0.2j/bin/openssl
command(2): requirements_osx_brew_install_custom homebrew/versions
+ typeset __tap
+ for __tap in '"$@"'
+ brew tap homebrew/versions
Error: homebrew/versions was deprecated. This tap is now empty as all its formulae were migrated.
+ return 1
So. RVM seems to be stuck on this idea of installing homebrew/versions, which has been completely removed by Homebrew. I've updated Homebrew. I've updated RVM. I've tried to trick Homebrew into having that tap available (not successful). I've tried to trick RVM into thinking that's not a required custom package (couldn't figure out how). Nothing seems to be working. Help!
EDIT
I got around the problem by actually upgrading the project to use ruby-2.1.0 . Worked like a charm, but of course didn't actually resolve the original issue. Thank you for the answers below, and hopefully they'll help out some other poor soul in the same situation!