Bundler not found #79

Closed
trans opened this Issue Jan 21, 2013 · 12 comments

Projects

None yet

4 participants

@trans
trans commented Jan 21, 2013

I've been setting up a Radiant site this week and ran into an odd issue. When I ran rake db:bootstrap it told me Bundler wasn't installed. But of course, it is and I had already run bundle install just fine. So I did a chruby system and redid it and it worked fine.

I am not sure if this is solely a Radiant issue or whether it is a broader issue stemming from Rails.

@postmodern
Owner

Could you try to reproduce this, and diff the output of env before and after running chruby system. It could be that something modified GEM_HOME/GEM_PATH. It also could be a weird Bundler/Rails issue.

@trans
trans commented Jan 21, 2013

Okay. Note it happens no matter what rake command I invoke:

  rake
  WARNING: It seems you do not have Bundler installed.
  WARNING: You can install it by doing `gem install bundler`
  Radiant could not be initialized. Have you run `bundle install`?'.

I'll email you the env outputs.

@postmodern
Owner

After diffing the two env outputs, nothing jumps out. /home/trans/.gem/ruby/1.9.3/gems/bundler-1.2.3/bin is even in your PATH (not sure why every gem is in your PATH). I would check with @indirect, this may be a Bundler/Rails issue.

@trans
trans commented Jan 21, 2013

Okay thanks.

The PATH is full of those b/c I'v been working on my load manager and it doesn't have a binstubs feature, it just adds all the paths to PATH. (Eventually it will probably get binstubs, but I haven't really needed it). The gem paths are there b/c I was seeing how well it served up gems --usually I just use it to serve up my workspace.

@postmodern
Owner

A little update, I have recently added a scripts/bug_report.sh to help collect environment info. Also, we have been noticing that most environment issues are being caused by ohmyzsh aliases/hooks.

@postmodern
Owner

@trans can you reproduce this bug, but run the new scripts/bug_report.sh. I'm guessing this is being caused by some shell script that's hooking/overriding some command/function.

@trans
trans commented Feb 24, 2013

Yea, I'll do it sometime this week or so --I need to get back to that project soon anyway.

@robin850

I don't think that this is due to Oh-My-Zsh, I've switched to bash and got the same issue.

@robin850

I've found a little trick to solve this issue temporarily. I've seen that chruby change the value of GEM_HOME to match the current version but using 1.9.x, gems are installed in ~/.gem/ruby/1.9.1 (on my machine at least)

$ GEM_HOME=/home/robin/.gem/ruby/1.9.1 bundle install
Resolving dependencies...
@postmodern
Owner

@robin850 this sounds like an issue with bundler not respecting the current GEM_HOME?

@indirect

If you could file a bug following ISSUES, that would be super helpful. Thanks!

On Tue, May 28, 2013 at 1:43 PM, Postmodern notifications@github.com
wrote:

@robin850 this sounds like an issue with bundler not respecting the current GEM_HOME?

Reply to this email directly or view it on GitHub:
#79 (comment)

@postmodern
Owner

Closing this. Reopen if the issue persists.

@postmodern postmodern closed this Jun 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment