Bundler under Rubygems 1.5 throws the following error:

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

Needs a patch-y, yo!

Two hours of warning is not even close to enough time for the Bundler patch+release cycle. :(

Broke my Bundler!

/Users/kevin/.rvm/gems/ruby-1.9.2-p136/gems/bundler-1.0.9/lib/bundler/ui.rb:56:in `’: uninitialized constant Gem::SilentUI (NameError)

Broke Bundler. How do I downgrade?

@Nick: https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc explains how to downgrade.

I solved this by installing older version of rubygems
rvm install rubygems 1.3.7

Thanks!

Too bad it doesn’t work:

➔ rvm install rubygems 1.3.7
Cannot switch to 1.3.7 for this interpreter.

All I can say is this on Win 7:

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.
The system cannot find the path specified.

C:\Windows\system32>gem update —system
Updating RubyGems
Updating RubyGems to 1.5.0
Installing RubyGems 1.5.0
RubyGems 1.5.0 installed
ERROR: While executing gem … (Encoding::UndefinedConversionError)
U+2018 from UTF-8 to CP852

C:\Windows\system32>gem install rubygems-update
Successfully installed rubygems-update-1.5.0
1 gem installed
Installing ri documentation for rubygems-update-1.5.0…
Installing RDoc documentation for rubygems-update-1.5.0…

C:\Windows\system32>update_rubygems
RubyGems 1.5.0 installed
ERROR: While executing gem … (Encoding::UndefinedConversionError)
U+2018 from UTF-8 to CP852

C:\Windows\system32>

Works with the brandnew bundler 1.0.10: gem install bundler

Looks like with rails 2.3.5 it’s broken

i got that:
undefined local variable or method `version_requirements’ for #

ruby -v => ruby 1.8.7 (2009-12-24 patchlevel 248) [x86_64-linux], MBARI 0×6770, Ruby Enterprise Edition 2010.01

ruby -e ‘puts $:’ =>
/usr/local/lib/ruby/site_ruby/1.8
/usr/local/lib/ruby/site_ruby/1.8/x86_64-linux
/usr/local/lib/ruby/site_ruby
/usr/local/lib/ruby/vendor_ruby/1.8
/usr/local/lib/ruby/vendor_ruby/1.8/x86_64-linux
/usr/local/lib/ruby/vendor_ruby
/usr/local/lib/ruby/1.8
/usr/local/lib/ruby/1.8/x86_64-linux

uname -a
=> Linux … 2.6.32-24-server #43-Ubuntu SMP Thu Sep 16 16:05:42 UTC 2010 x86_64 GNU/Linux

reinstalling 1.4.2 solved the problem

fixed problem in last version bundler

bundler was warned of this change two months ago but chose to reject it, and had one patch applied since the 19th. I’m sorry that wasn’t enough warning.

bundler 1.0.10 is out now, please upgrade.

My advice…

Don’t upgrade! Chances are your gems are not ready for this upgrade and downgrading will be painful.

RubyGems 1.5.0 seems to force use of the psych yaml parser if you have it in your system. If you are having trouble parsing some yaml files, or if you have yaml files which use merge keys ( http://redmine.ruby-lang.org/issues/show/4300 ), then you might need to revert to using syck instead of psych.

I have libyaml installed, rvm builds 1.9.2 with libyaml, so its part of my system. But ruby 1.9.2 doesn’t make it the default yet. All worked fine till 1.5.0, which by directly requiring ‘psych’ cause it to get loaded first and set as system yaml parser.

My workaround was to do the following early in the rails boot sequence:

require ‘yaml’
YAML::ENGINE.yamler= ‘syck’

Hello,

I’m a newbie, but I’ve been breaking my teeth on trying to get require to work. I’ve downloaded stable release of ruby 1.9.2, and installed rubygems 1.5.0. I did as root on rh linux ruby setup.rb and got "RubyGems installed the following executables:
/usr/local/bin/gem
"

Then I tried something simple:

#!/usr/local/bin/ruby

1. Module define in trig.rb file

module Trig
PI = 3.14159
def Trig.sin(s)

1. ..
   end
   def Trig.cos(x)
2. ..
   end
   end

and ran

#!/usr/local/bin/ruby

1. Module define in trig.rb file

module Trig
PI = 3.14159
def Trig.sin(s)

1. ..
   end
   def Trig.cos(x)
2. ..
   end
   end

and got: ruby example.rb
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:29:in `require’: cannot load such file — trig.rb (LoadError)
from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:29:in `require’
from example.rb:1:in `’

I get this same error if I try require from irb prompt.

Sorry this might not be the place for this newbie question, but nothing in any of the distros, readmes, forums talks/identifies what is going on or what is needed.

Thanks, Robert

I found the downgrade docs to be almost complete.

update_rubygems attempted to update to the most recently installed version. The downgrade steps that worked for me were:

gem install rubygems-update -v 1.3.7
gem uninstall rubygems-update -v 1.5.0
update_rubygems

Upgrading to rubygems-1.5.0 tonight caused the latest Passenger/REE to barf with the following error:

undefined method `load_yaml’ for Gem:Module

Could I suggest stopping 1.5.0 from being installed by “gem update —system”.

At least seek user confirmation that they are aware 1.5.0 may break their app.

- Mike

Mike, you probably forgot to restart passenger after updating RubyGems. Passenger loads part of RubyGems before forking then part of it after forking so a restart is required.

The same issue was reported to help.rubygems.org:

http://help.rubygems.org/discussions/problems/481-cant-update-to-15-on-debian-lenny

OK, so from what I can tell it ISN’T safe to upgrade if you have 1.9.2 right? There are way too many chances for it to break something and it’s really hard to figure out what and there are all sorts of dependencies that haven’t been updated to work.

Am I reading this right?

Hi,
I updated to rubygems 1.5.0 and also upgraded bundler to 1.0.10.

Unfortunately Autotest has broken and gives me
the following error:
uninitialized constant Gem::SilentUI (NameError)

I also noticed the if I ask for Gem list….I still get Bundler 1.0.0 in the list.

Any suggestions as to how to resolve this…thanks.

Hi,

I upgraded my Rubygems to 1.5 and started getting a “undefined local variable or method `version_requirements’” error.

So I downgraded to my earlier RubyGems version 1.4.2, and now I get a “Gem::Dependency#version_requirements is deprecated and will be removed on or after August 2010. Usr # requirement” error

Any ideas on how I can get rid of this warning?

Thanks,
Aloke

Mitur, no, it is perfectly safe to upgrade RubyGems on 1.9.2 per the first major enhancement in the change log.

To, autotest doesn’t use Gem::SilentUI, the problem is somewhere else. Maybe you haven’t upgrade bundler properly.

Aloke, RubyGems itself does not call #version_requirements.

This warning has been printing since RubyGems 1.3.6 nearly one year ago was released and should have been fixed over that time. You need to upgrade your software calling #version_requirements and file a bug if that does not fix it.

Eric, a lot of us are maintaining old rails 2.3.5 installs. Rubygems breaking old working rails installs is not good. It is unlikely that Rails 2.3.5 will fix this, and it is not easy to upgrade an old rails application away from that version.

Anshul, the warning existed for 20 days short of one year and had a clearly defined end of life. It will not be reverted. Either upgrade to a newer version of Rails or downgrade to RubyGems to 1.3.7.

If you wish for a rails release to address this issue you will need to take that up on the rails bug tracker.

Anshul, you can monkey-patch line 27 of rails/lib/tasks/framework.rake to workaround this. I hardcoded “2.3.11” to freeze Rails, fwiw.