From: Eric Hodel <drbrain@...7.net>
Date: 2006-12-19T18:53:43+09:00
Subject: Re: Please help fixing gems on OSX

On Dec 18, 2006, at 23:43, Dan Uznanski wrote:

> Over the past few months, several people have posted on various  
> mailing lists, including this one, that their rubygems install on  
> OSX fails with the following error:
>
> /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:52:in  
> `initialize': uninitialized constant  
> Gem::CommandManager::HelpCommand (NameError)
> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb: 
> 46:in `new'
> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb: 
> 46:in `instance'
> from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:25:in  
> `run'
> from /usr/local/bin/gem:23
>
> I have discovered the cause of this error, at least on my machine,  
> but not the final underlying cause.
>
> in $LIBDIR/ruby/site_ruby/1.8/rubygems/, there is a file named  
> gem_commands.rb ; on my machine, this file was empty.  However,  
> there was also gem_commands.1.rb , which contained the original  
> content of gem_commands.rb .  To fix the error, simply move  
> gem_commands.1.rb onto gem_commands.rb .

I'd like to know how this happens because I certainly haven't been  
able to reproduce it.  I suspect something happened before install,  
not after.

I'd especially like to see `ls -l lib/rubygems` from the unpacked  
tarball that produced this install, and I'd like to see the md5 hash  
of the downloaded tarball.

-- 
Eric Hodel - drbrain@segment7.net - http://blog.segment7.net

I LIT YOUR GEM ON FIRE!