Red Hat Bugzilla – Bug 1163076
Bundler can't see its dependencies after Bundler.setup [rhel-7]
Last modified: 2016-01-04 00:54:26 EST
+++ This bug was initially created as a clone of Bug #1163039 +++ Description of problem: Bundler can't see its dependencies after Bundler.setup. If thor or net-http-persistent are already in memory, Bundler can reuse them just fine, but if Bundler locks the Gemfile and those libs are not already loaded, Bundler doesn't see them even though they are its dependencies. Originally these dependencies are vendored inside the gem, but we removed them in Fedora. For Bundler to function as expected and designed by upstream we should most likely symlink the originally vendored libs to system-installed RubyGems. I am including a simple reproducer for rawhide although I came across this in the real usecase when Vagrant couldn't download remote plugins, because Bundler (which Vagrant uses underneath) uses net-http-persistent for that. How reproducible: $ bundle init $ irb > require 'bundler' > Bundler.setup > require 'bundler/vendored_thor' LoadError: cannot load such file -- thor from /usr/share/gems/gems/bundler-1.7.4/lib/bundler/vendored_thor.rb:7:in `require' from /usr/share/gems/gems/bundler-1.7.4/lib/bundler/vendored_thor.rb:7:in `<top (required)>' from (irb):5:in `require' from (irb):5 from /usr/bin/irb:11:in `<main>'
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-2180.html