| Summary: | dev-ruby/bundler-1.0.13 bundle exec does not work together with bundle install installed gems | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
| Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | ewoud+gentoo, jstein |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Could you figure out where the 'bundle install' action put the rake binary? If things are installed in your home directory then that should be ${HOME}/bin/rake, but it might also have ended up in /usr/local/bin/rake due to a bug in our rubygems defaults.
There's do exist:
/home/betelgeuse/.gem/ruby/1.8/gems/rake-0.9.1/bin/rake
/home/betelgeuse/.gem/ruby/1.8/bin/rake
These don't exist:
betelgeuse@pena ~/test/gemfile $ file /usr/local/bin/rake
/usr/local/bin/rake: ERROR: cannot open `/usr/local/bin/rake' (No such file or directory)
betelgeuse@pena ~/test/gemfile $ file ${HOME}/bin/rake
/home/betelgeuse/bin/rake: ERROR: cannot open `/home/betelgeuse/bin/rake' (No such file or directory)
(In reply to comment #2) > There's do exist: > > /home/betelgeuse/.gem/ruby/1.8/gems/rake-0.9.1/bin/rake > /home/betelgeuse/.gem/ruby/1.8/bin/rake ok, that's the usual gem layout. > betelgeuse@pena ~/test/gemfile $ file /usr/local/bin/rake > /usr/local/bin/rake: ERROR: cannot open `/usr/local/bin/rake' (No such file or > directory) > betelgeuse@pena ~/test/gemfile $ file ${HOME}/bin/rake > /home/betelgeuse/bin/rake: ERROR: cannot open `/home/betelgeuse/bin/rake' (No > such file or directory) So it appears that bundle install doesn't add the bin wrappers like gem install does. As far as I know we don't do anything unusual in this area. Bundler is vanilla on our systems, and I don't think anything we do in rubygems should be of influence. Would be interesting to test this on macos to see what happens. That way we can find out if this is an upstream issue, or something we do. (In reply to comment #3) > > Would be interesting to test this on macos to see what happens. That way we can > find out if this is an upstream issue, or something we do. What I can make of this issue with a quick look is as follows: betelgeuse@pena ~/hobo/gentoocouncil $ bundle exec rake /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/rubygems_integration.rb:194:in `bin_path': can't find executable rake (Gem::Exception) from /home/betelgeuse/.gem/ruby/1.8/bin/rake:19 Here bundler tries to use the bundle install installed nrake binary for version 0.9.1. The rake binary for the rake version locked by Gemfile is the system binary: betelgeuse@pena ~/hobo/gentoocouncil $ bundle show rake /usr/lib/ruby/gems/1.8/gems/rake-0.8.7 My guess is that the bundler installed rake binary can't be used to activate Portage installed fakegem binaries. I think I'm running into the same issue. Is the status CONFIRMED still correct? Could someone retest this with a more recent version of bundler and maybe create reproduceable steps to trigger this issue? It might be related to us adding more default gem paths, which bundler probably doesn't anticipate. |
betelgeuse@pena ~/hobo/gentoocouncil/site $ bundle exec rake /usr/lib/ruby/gems/1.8/gems/bundler-1.0.13/lib/bundler/rubygems_integration.rb:194:in `bin_path': can't find executable rake (Gem::Exception) from /home/betelgeuse/.gem/ruby/1.8/bin/rake:19 betelgeuse@pena ~/hobo/gentoocouncil/site $ bundle show rake /usr/lib/ruby/gems/1.8/gems/rake-0.8.7 I think the cause of this is me testing bundle install with a simple Gemfile for newest rails which resulted in a newer rake being installed: betelgeuse@pena ~/test/gemfile $ bundle show rake /home/betelgeuse/.gem/ruby/1.8/gems/rake-0.9.1