[Rubygems-developers] [ rubygems-Bugs-28237 ] gem outdated fails for gems that are outdated but have a prerelease installed

noreply at rubyforge.org noreply at rubyforge.org
Fri Nov 12 20:19:30 EST 2010


Bugs item #28237, was opened at 2010-05-23 10:58
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28237&group_id=126

Category: `gem` commands (other)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Caio Chassot (cchassot)
>Assigned to: John Barnette (jbarnette)
Summary: gem outdated fails for gems that are outdated but have a prerelease installed

Initial Comment:
    $ sudo gem1.9 outdated --backtrace
    ERROR:  While executing gem ... (NoMethodError)
        undefined method `first' for nil:NilClass
            .../rubygems/commands/outdated_command.rb:26:in `block in execute'
            .../rubygems/commands/outdated_command.rb:21:in `each'
            .../rubygems/commands/outdated_command.rb:21:in `execute'
            .../rubygems/command.rb:270:in `invoke'
            .../rubygems/command_manager.rb:134:in `process_args'
            .../rubygems/command_manager.rb:104:in `run'
            .../rubygems/gem_runner.rb:58:in `run'
            /opt/local/bin/gem1.9:21:in `<main>'

That occurs on my machine because I have rails 3.0.0.beta3 and 2.3.5 installed, but 2.3.6 is out.

I can fix this by updating Gem::Commands::OutdatedCommand to exclude prereleases when listing the outdated gems. Not sure if you'll want to somehow handle prereleases with gem outdated, tho.

----------------------------------------------------------------------

Comment By: Caio Chassot (cchassot)
Date: 2010-05-23 11:06

Message:
I made a simple patch that fixes the bug but doesn't otherwise enhance outdated 
to handle prereleases.

Eg. if a prerelease itself is outdated, I'm not sure how that would be handled. I 
think prereleases are ignored by Gem::SourceIndex.outdated. (Our bug happens 
after that, during the printing of the outdated gems.)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28237&group_id=126


More information about the Rubygems-developers mailing list