On Sun, 31 Oct 2004 14:06:35 +0900, Patrick May <patrick / hexane.org> wrote:
> 
> On Wednesday, October 13, 2004, at 10:43  AM, jim / freeze.org wrote:
> 
> > Hi
> >
> > I just installed gems and after it 'successfully' installed,
> > it burped. Below are the stats:
> 
> I got this problem too.  I think I found the fix.  I dug around in the
> rubygems libraries.  This is the line where the error comes from:
> 
>    lib/rubygems/specification.rb, line 474
>      result << "  s.#{name} = #{ruby_code(current_value)}\n" unless
> current_value == default
> 
> You can either setup a default:
> 
>    lib/rubygems/specification.rb, line 189
>      required_attribute :version, Version.create('0.0.0')
> 
> Or you can make version's compare nicely to nihilism:
> 
>    lib/rubygems/version.rb, line 122
>      def <=>(other)
>        return 1 unless other  # I figure something is always more than
> nothing
> 
> Either way, things worked for me.  I've already forwarded this fix to
> the rubygems-developers mailing list.
> 
> Cheers,
> 
> Patrick
> 
> 

Thanks, Patrick!  It's applied.

-- 

Chad Fowler
http://chadfowler.com
http://rubycentral.org 
http://rubygarden.org 
http://rubygems.rubyforge.org (over 20,000 gems served!)