Skip to content

None new gems get installed via Bundler #3

Closed
millisami opened this Issue Dec 19, 2012 · 4 comments

3 participants

@millisami

After installing this gem, now whenever I run bundle install, I always get the following msg and none of the new gems or its dependencies gets installed.

bundle
...
....
Using gmaps4rails (1.5.6) 
Installing listen (0.6.0) 
LoadError: cannot load such file -- rubygems/commands/ctags_command
An error occurred while installing listen (0.6.0), and Bundler cannot continue.
Make sure that `gem install listen -v '0.6.0'` succeeds before bundling.

I've installed ctags via homebrew and the $PATH is:

echo $PATH                                                                                         1.9.3-p194@global 
/Users/millisami/.rbenv/shims:/Users/millisami/.rbenv/bin:/usr/local/share/npm/bin:/Users/millisami/.oh-my-zsh/custom/shell-scripts:/usr/local/bin:/Users/millisami/.rbenv/shims:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/deployd/bin:/usr/local/git/bin:/usr/X11/bin

Do I've to do some conf change for the bundle to run without the above error?

@tpope tpope added a commit that referenced this issue Dec 19, 2012
@tpope Attempt to fix LoadError seen in #3 b0e8085
@tpope
Owner
tpope commented Dec 19, 2012

I've seen this before, but never at a time where I had the luxury to dig in. I've got a pretty good guess how to fix it, and I pushed it to the fix_load_error branch. Could you check out that branch, rake install, and see if it fixes it for you?

@iamkristian

I got the same error

LoadError: cannot load such file -- rubygems/commands/ctags_command
An error occurred while installing carrierwave (0.6.2), and Bundler cannot continue.
Make sure that `gem install carrierwave -v '0.6.2'` succeeds before bundling.

With your fix on branch fix_load_error it works! 👍

Thanks for the fix and top notch work

@millisami

Yup, that branch works! 👍

@tpope tpope added a commit that closed this issue Dec 20, 2012
@tpope Fix LoadError
Closes #3.  I haven't narrowed down the exact trigger for this but the
error message makes the solution pretty obvious.
2827450
@tpope tpope closed this in 2827450 Dec 20, 2012
@tpope
Owner
tpope commented Dec 20, 2012

Good deal. This warrants cutting a release in the very near future!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.