Rainer wrote:
>  gem -v
> 
> and found out that I was still using 1.3.1. So I typed:
> 
>  gem update --system
> 
> This was the result:
> 
> ---begin---
> Updating RubyGems
> Updating rubygems-update
> Successfully installed rubygems-update-1.3.5
> :0:Warning: Gem::SourceIndex#search support for String patterns is
> deprecated
> Updating RubyGems to 1.3.5
> Installing RubyGems 1.3.5
> c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/
> config_file.
> rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError)
>         from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/
> lib/rubygems
> /config_file.rb:39:in `<class:ConfigFile>'
>         from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/
> lib/rubygems
> /config_file.rb:12:in `<top (required)>'
>         from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/
> lib/rubygems
> /gem_runner.rb:8:in `require'
>         from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/
> lib/rubygems
> /gem_runner.rb:8:in `<top (required)>'
>         from setup.rb:25:in `require'
>         from setup.rb:25:in `<main>'
> RubyGems system software updated
> --end--
> 
> Now, when I type
> 
>   gem -v
> 
> I get this:
> 
> ---begin---
> c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/
> config_file.
> rb:39:in `new': wrong number of arguments (5 for 4) (ArgumentError)
>         from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/
> lib/rubygems
> /config_file.rb:39:in `<class:ConfigFile>'
>         from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/
> lib/rubygems
> /config_file.rb:12:in `<top (required)>'
>         from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/
> lib/rubygems
> /gem_runner.rb:8:in `require'
>         from c:/ruby/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/
> lib/rubygems
> /gem_runner.rb:8:in `<top (required)>'
>         from c:/ruby/bin/gem.bat:17:in `require'
>         from c:/ruby/bin/gem.bat:17:in `<main>'
> ---end---
> 
> Does this mean I have broken rubygems on mingw32 by typing "gem update
> --system"? Typing
> 
>   "gem search wxruby-ruby19 --remote"
> 
> or trying to install a gem - any gem - gives me the same argument
> error.
> 
> Now I'm even more confused. "Bigdemo" is still working after the
> failed rubygems upgrade, but now I'm unable to install any gems. Of
> course, I can reinstall and stay with rubygems 1.3.1, but is this an
> issue that should be reported to someone?
> 
> Kind regards,
> 
> Rainer

Hi Rainer,
Some minuts ago I had the same problem. If you try to update RubyGems to
1.3.5 on a ruby-1.9.1-p0 installation you get this issue on Windows (I'm
too lazy to compile and test with Linux at the moment). I wasn't able to
undo the update, since RubyGems seems to be broken after the update.
There were some problems with the 1.3.5 version of RubyGems on Windows a
few days ago on the mailing list, but I don't remember what exactly. I
had to reinstall my ruby-1.9.1-p0 after updating RubyGems. Maybe it's
best not to update at the moment. When the new WxRuby is released, we
will (hopefully) be able to use it with ruby-1.9.1-p243 or the like. :-)
Or try compiling it yourself against the MinGW GCC and the newest Ruby-
but I think you have WxWidgets to be installed for this.

Rainer wrote:
>Of
> course, I can reinstall and stay with rubygems 1.3.1, but is this an
> issue that should be reported to someone?
File a RubyGems bug:
http://rubyforge.org/tracker/?atid=575&group_id=126&func=browse

Marvin
-- 
Posted via http://www.ruby-forum.com/.