New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<internal:gem_prelude>:344:in `method_missing': undefined method `user_home' for Gem:Module (NoMethodError) #442

Closed
johnf opened this Issue Jul 8, 2010 · 11 comments

Comments

Projects
None yet
6 participants
@johnf

johnf commented Jul 8, 2010

I get this when running any bundle command. The culprit seems to be in
lib/bundler/rubygems_ext.rb

If I comment out the following lines

if defined?(Gem::QuickLoader)
  # Gem Prelude makes me a sad panda :'(
  Gem::QuickLoader.load_full_rubygems_library
end

then everything works fine. This is with ruby 1.9.1

@indirect

This comment has been minimized.

Show comment
Hide comment
@indirect

indirect Jul 8, 2010

Member

How about Ruby 1.9.2? We are not officially supporting bundler on 1.9.1, due to a pretty long list of crazy bugs.

Member

indirect commented Jul 8, 2010

How about Ruby 1.9.2? We are not officially supporting bundler on 1.9.1, due to a pretty long list of crazy bugs.

@josei

This comment has been minimized.

Show comment
Hide comment
@josei

josei Aug 20, 2010

I have the same issue using ruby 1.9.2p0 (2010-08-18 revision 29036) [i386-darwin9.8.0]. It is solved by commenting out the same lines.

josei commented Aug 20, 2010

I have the same issue using ruby 1.9.2p0 (2010-08-18 revision 29036) [i386-darwin9.8.0]. It is solved by commenting out the same lines.

@jzinn

This comment has been minimized.

Show comment
Hide comment
@jzinn

jzinn Aug 25, 2010

I also ran into this problem around July 27 with Bundler 1.0.0.rc.1 on Ruby 1.9.1-p376 (and Chef 0.9.6) and gave up.

Since Rails 3.0.0.rc2 just came out, I tried again with Bundler 1.0.0.rc.6, and the user_home problem does not occur for either Ruby 1.9.1-p376 or Ruby 1.9.2-p0 (and Chef 0.9.6 and 0.9.8). Yay!

My use case is on an Ubuntu 10.04 EC2 instance, logged in as ubuntu, running sudo chef-solo on a recipe that runs bundle install as the user my app runs as.

When logged in as the ubuntu user, if i do a sudo -s and then echo $HOME, the value is /home/ubuntu, instead of /root, so maybe that's it. Sudo -i sets home correctly.

I wonder how this got fixed.

jzinn commented Aug 25, 2010

I also ran into this problem around July 27 with Bundler 1.0.0.rc.1 on Ruby 1.9.1-p376 (and Chef 0.9.6) and gave up.

Since Rails 3.0.0.rc2 just came out, I tried again with Bundler 1.0.0.rc.6, and the user_home problem does not occur for either Ruby 1.9.1-p376 or Ruby 1.9.2-p0 (and Chef 0.9.6 and 0.9.8). Yay!

My use case is on an Ubuntu 10.04 EC2 instance, logged in as ubuntu, running sudo chef-solo on a recipe that runs bundle install as the user my app runs as.

When logged in as the ubuntu user, if i do a sudo -s and then echo $HOME, the value is /home/ubuntu, instead of /root, so maybe that's it. Sudo -i sets home correctly.

I wonder how this got fixed.

@ari

This comment has been minimized.

Show comment
Hide comment
@ari

ari Sep 4, 2010

I can confirm that the bug still exists with:

ruby 1.9.1p376 (2009-12-07 revision 26041) [amd64-freebsd8]
bundler 1.0 (final)

ari commented Sep 4, 2010

I can confirm that the bug still exists with:

ruby 1.9.1p376 (2009-12-07 revision 26041) [amd64-freebsd8]
bundler 1.0 (final)

@indirect

This comment has been minimized.

Show comment
Hide comment
@indirect

indirect Sep 4, 2010

Member

Please upgrade to Ruby 1.9.2 now that the final is out. 1.9.1 has many terrible bugs.

Member

indirect commented Sep 4, 2010

Please upgrade to Ruby 1.9.2 now that the final is out. 1.9.1 has many terrible bugs.

@ari

This comment has been minimized.

Show comment
Hide comment
@ari

ari Sep 4, 2010

Not yet ported to FreeBSD, so I'll need to wait a bit longer. Please note above though that one person had the same problem with 1.9.2

ari commented Sep 4, 2010

Not yet ported to FreeBSD, so I'll need to wait a bit longer. Please note above though that one person had the same problem with 1.9.2

@indirect

This comment has been minimized.

Show comment
Hide comment
@indirect

indirect Sep 4, 2010

Member

You should just be able to compile it on FreeBSD -- IIRC, it doesn't need porting. And yes, I believe the person with 1.9.2 above encountered a different bug that is now fixed.

Member

indirect commented Sep 4, 2010

You should just be able to compile it on FreeBSD -- IIRC, it doesn't need porting. And yes, I believe the person with 1.9.2 above encountered a different bug that is now fixed.

@jzinn

This comment has been minimized.

Show comment
Hide comment
@jzinn

jzinn Sep 10, 2010

I spoke too soon. I get the user_home method missing error when using Ubuntu's ruby1.9.1-full package. When using the ruby-full package or compiling Ruby 1.9.1 from source, this error does not happen.

jzinn commented Sep 10, 2010

I spoke too soon. I get the user_home method missing error when using Ubuntu's ruby1.9.1-full package. When using the ruby-full package or compiling Ruby 1.9.1 from source, this error does not happen.

@indirect

This comment has been minimized.

Show comment
Hide comment
@indirect

indirect Sep 10, 2010

Member

@jzinn, 1.9.1 has too many bugs -- please try it with 1.9.2? Thanks.

Member

indirect commented Sep 10, 2010

@jzinn, 1.9.1 has too many bugs -- please try it with 1.9.2? Thanks.

@paranormal

This comment has been minimized.

Show comment
Hide comment
@paranormal

paranormal Sep 13, 2010

Hi, nice people.
For freebsd use this patch: http://pastebin.com/zzVgnfAm

I'm 30 min hard debug bundler for search this.

paranormal commented Sep 13, 2010

Hi, nice people.
For freebsd use this patch: http://pastebin.com/zzVgnfAm

I'm 30 min hard debug bundler for search this.

@indirect

This comment has been minimized.

Show comment
Hide comment
@indirect

indirect Dec 21, 2010

Member

ponny: I closed it because no one reported the error was still present in 1.9.2. I cannot, in fact, reproduce this issue on 1.9.2. Can you give me the information from ISSUES and explain how I can reproduce the problem you're seeing?

Member

indirect commented Dec 21, 2010

ponny: I closed it because no one reported the error was still present in 1.9.2. I cannot, in fact, reproduce this issue on 1.9.2. Can you give me the information from ISSUES and explain how I can reproduce the problem you're seeing?

This issue was closed.

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