Brew Update failed with Git
I have a problem with the launch of both rvm use ruby --install --default
and brew update
. It looks like the later issue is the reason I see the first issue.
Below is the error for rvm use ruby --install --default
:
ruby-2.1.2 is not installed - installing.
Searching for binary rubies, this might take some time.
Found remote file https://rvm.io/binaries/osx/10.9/x86_64/ruby-2.1.2.tar.bz2
Checking requirements for osx.
Installing requirements for osx.
Updating system......
Error running 'requirements_osx_brew_update_system ruby-2.1.2',
showing last 15 lines of /Users/connorphillips/.rvm/log/1408816616_ruby-2.1.2/update_system.log
https://github.com/Homebrew/homebrew/wiki/Common-Issues
and make sure `brew update` works before continuing.'
++ rvm_pretty_print stderr
++ case "${rvm_pretty_print_flag:=auto}" in
++ case "${TERM:-dumb}" in
++ case "$1" in
++ [[ -t 2 ]]
++ return 1
++ printf %b 'Failed to update Homebrew, follow instructions here:
https://github.com/Homebrew/homebrew/wiki/Common-Issues
and make sure `brew update` works before continuing.\n'
Failed to update Homebrew, follow instructions here:
https://github.com/Homebrew/homebrew/wiki/Common-Issues
and make sure `brew update` works before continuing.
++ return 1
Requirements installation failed with status: 1.
Gemset '' does not exist, 'rvm ruby-2.1.2 do rvm gemset create ' first, or append '--create'.
Then I try brew update
and this is the error I see:
fatal: unable to access 'https://github.com/Homebrew/homebrew.git/': Could not resolve host: github.com
Error: Failure while executing: git pull -q origin refs/heads/master:refs/remotes/origin/master
What is the source of the problem / fix.
source to share
I had a similar problem but was able to solve it. Every time I tried to update brew I would get this error:
fatal: Unable to access https://github.com/Homebrew/homebrew.git/ ': Could not resolve host: github.com
Error: Error while executing: git pull --quiet origin refs / heads / master: refs / remotes / origin / master
My problem was that I was using a VPN, but after disabling it, it worked for me.
source to share