pivotal-sprout / sprout-rbenv Goto Github PK

Anytime I try to install a ruby version 2.x (tested 2.0.0-p247, 2.1.0 and 2.1.1) ruby-build crashes. The patch is simple, but I'm curious as to whether we want to patch our ruby build or if we want to wait for changes to occur upstream.

Also I wanted to create an issue for other people to stumble upon to generate a conversion and provide some guidance to a temporary solution.

Related issue w/ quick fix on github: rbenv/ruby-build#526

Quick fix:

brew uninstall readline && brew install https://raw.githubusercontent.com/Homebrew/homebrew/0181c8a1633353affefabe257c170edbd6d7c008/Library/Formula/readline.rb

Do we want to fix this issue internally or let home-brew / ruby-build handle the issue?

We have a machine with a previous brew installation of rbenv. sprout-rbenv does not try to update brew and upgrade the ruby-install package. As such, the installation fails if the specified ruby version to be used as the global default is not in the existing ruby-install package's directory.

Running these commands, and then re-running the sprout-rbenv recipes fixed the problem:

brew update
brew install rbenv ruby-build
"$(rbenv init -)"

Hello!

We're just trying to use sprout wrap on a clean build of El Capitan, and we're seeing a strange issue. During the sprout_base_bash_it_enable_feature action, we get a failure due to the ruby_install definition in sprout-rbenv being unable to complete as it cannot write to the /Library/Ruby/Gems/2.0.0 directory.

We can do a temporary workaround by issuing:

sudo chown -R pivotal:staff /Library/Ruby

...but that feels wrong to us.

Please find below the output of running soloist:

soloist_output.txt
ruby-build_output.txt

We are using the latest Pivotal machine image, which appears to be a pretty bare-bones El Capitan 10.11.4. System Integrity Protection is enabled.

Thanks! 😄

Mike and Heather