Skip to content
This repository

Error in rubygems 1.5 `uninitialized constant Gem::SilentUI` #995

Closed
smathy opened this Issue January 31, 2011 · 14 comments

11 participants

Jason King André Arko Ryan Bigg Alan McCann J. Pablo Fernández Sasha Koss Matt Milosavljevic Theresa Anthony Herron Victor Stan Rajib Chowdhury
Jason King

bundler-1.0.9/lib/bundler/ui.rb:56: uninitialized constant Gem::SilentUI (NameError)

Jason King

Actually this is resolved in a318f91 - just waiting on a version bump in the gemspec.

André Arko
Owner

There is no Bundler release that is compatible with Rubygems 1.5 yet. We are planning on releasing 1.0.10 with those fixes tomorrow.

Ryan Bigg
Collaborator

I've just marked #996, #997 and #998 and duplicates of this ticket. Thanks for reporting it Jason!

Alan McCann

Thanks for being on top of this!

J. Pablo Fernández

Is there a workaround for this?

Ryan Bigg
Collaborator

I think 1.0.10 fixes this issue. Please try it and confirm

Sasha Koss

1.0.10 solve this problem. Confirm.

Ryan Bigg
Collaborator

Thank you kossnocorp.

Matt Milosavljevic

Seems to be working now, hilarious that this happened mere hours before I had to use bundler for the first time :)

Thanks for the quick turnaround on this issue.

Theresa

I'm actually having the same issue with Rubygems 1.5.1 and Bundler 1.0.10. Anyone else?

Jason King

I'm not seeing that update yet with update --system but I don't see how you could be seeing the same error. You sure it's exactly the same? I'm looking in rubygems/user_interaction.rb in 1.5.1 and it still defines Gem::SilentUI

Anthony Herron

Despite having bundler 1.0.10 I still had the same issues as above.

To fix this I reinstalled ruby-1.9.2-p136 in rvm after ensuring I had bundler 1.0.10 - job done.

Victor Stan

Im getting this error with ruby ruby-1.9.2-p180/

Rajib Chowdhury
rajib commented May 23, 2011

reinstall bundler gem will solve the problem

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.