Bug with latest RubyGems #1068

Closed
virtualfunction opened this Issue Mar 5, 2011 · 2 comments

Projects

None yet

2 participants

@virtualfunction

Just updated to RubyGems 1.6.1, and now I get this:

internal:gem_prelude:168:in load_full_rubygems_library': undefined local variable or methodpath' for Gem::QuickLoader:Module (NameError)
from /usr/local/lib/ruby/gems/1.9.1/gems/bundler-1.0.10/lib/bundler/rubygems_ext.rb:5:in <top (required)>' from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:inrequire'
from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in require' from /usr/local/lib/ruby/gems/1.9.1/gems/bundler-1.0.10/lib/bundler.rb:11:in<top (required)>'
from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in require' from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:inrequire'
from /usr/local/lib/ruby/gems/1.9.1/gems/bundler-1.0.10/bin/bundle:4:in <top (required)>' from /usr/local/bin/bundle:19:inload'
from /usr/local/bin/bundle:19:in `

'

I'm not sure if this is a bundler issue or a RubyGems issue. I'm guessing what's happened is that the new RubyGems has changed something that relates to how Bundler uses Rubygems.

For now, I've hacked round the issue by commenting out

Gem::QuickLoader.load_full_rubygems_library

My guess this will need still need calling for older gem versions so will need to be guarded with an version check conditional.

Owner
hone commented Sep 20, 2011

Is this still an issue on 1.0.20.rc? If so, can you provide your Gemfile + Gemfile.lock?

I think this disappeared after RubyGems 1.7.x, I'm guessing they did some voodoo on their side... I haven't had any issues for a little while relating to this, so I'll close it. If I do find anything I'll reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment