Closed brettswift closed 8 years ago
@brettswift I just was able to successfully run boxen
by rbenv use
-ing, in my case, 2.0.0
. I'm unsure if it was the fact that it was 2.0.0
or the fact that perhaps it was the Ruby version I initially used when I setup Boxen, or something else entirely, but was having the exact same issue as you were beforehand.
I ran into the same issue and, like @kulte points out, it seems to have to do with the fact that El Capitan system ruby is now 2.2.3 and boxen works best (only?) with 2.0.0.
$ mkdir ruby-test
$ cd ruby-test
$ rbenv local system
$ ruby -v
ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin14]
Here's how I fixed it:
cd /opt/boxen/repo
rbenv install 2.0.0-p647
rbenv local 2.0.0-p647
gem install bundler
rbenv rehash
script/boxen
sorry for the delayed response, this worked on my home macbook, and just got it running on my work one. (I delay changes quite a bit here).
This fix might actually help me with a vagrant issue I'm having - specifically with beaker and rbenv and vagrant... ruby paths are a pain in the butt!
A late Thanks
I just updated my boxen from this upstream module and with or without my changes I see an error when I run boxen.
Below is a boxen run, and then a bundle exec gem list.. showing the gem is there.
My ruby environment might be a bit mangled I'm guessing, but using
rbenv local
to try a few different rubies, andrbenv system
to try my system ruby, nothing seems to get through this.What am I missing here.. how could boxen report a missing gem, yet a
bundle exec gem list
show the exact version it wants... ???