bundle install failing on Lion

I'm attempting to follow thru with a sample demo "notebook" application demonstrated in one of the screencasts. Upon setting up the Rails project I get a complain from RubyMine that there are missing gems. It doesn't tell which those are but pops up a dialog to do a "bundle install" . Upon accepting this I get:

/usr/bin/ruby -e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift) /usr/bin/bundle install
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/ui.rb:46: uninitialized constant Gem::SilentUI (NameError)
 from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/cli.rb:17:in `initialize'
 from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/vendor/thor.rb:246:in `new'
 from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/vendor/thor.rb:246:in `dispatch'
 from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/bundler-1.0.0/lib/bundler/vendor/thor/base.rb:389:in `start'
 from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/bundler-1.0.0/bin/bundle:13
 from /usr/bin/bundle:19:in `load'
 from /usr/bin/bundle:19
 from -e:1:in `load'
 from -e:1

Process finished with exit code 1


I have the latest generation Mac Mini running Lion , stock Ruby  and Rails are installed i.e. that which comes with Lion , I also have Xcode 4.2 installed. Also I'm running the latest RubyMine.

What do I need to do ?

t;hanks in advance,


-Charles


2 comments

It's a compatibility issue with bundler and rubugems version. You can simply update bundler to the latest version, for example using Tools | Quick install gem

0

that helped thanks, however, after doing that I still had some issues which required updating rake. For some reason , running the update from within RubyMine did not work, so I did it a terminal which did. I was able to then proceed with running the Rails app.

0

Please sign in to leave a comment.