Trying to publish without changing version creates undefined method satisfied_by? error

[thenickcox]

I tried to publish a version of my gem, but I forgot to change the version in version.rb. It gave me this error, which made sense.

Pushing to rubygems.org...
gem push dronestream-0.1.1.gem
Pushing gem to https://rubygems.org...
Repushing of gem versions is not allowed.
Please use `gem yank` to remove bad gem releases.

So I changed the version from 0.1.1 to 0.2.0. It successfully registered the gem, but when I ran gem update dronestream, I got this:

Updating installed gems
Updating dronestream
ERROR:  While executing gem ... (NoMethodError)
    undefined method `satisfied_by?' for #<Gem::Version "0.2.0">

[thenickcox]

Uninstalling and reinstalling the gem worked for me, but will other users who try to run gem update dronestream get that cryptic satisfied_by? error?

[drbrain]

Can you show a backtrace for the error or describe how to reproduce it without needing to push gems to rubygems.org?

[lolmaus]

I have just experienced a this problem while updating my own gem.

I've updated the version number of my gem from 1.1 to 1.2: diff, gemspec.

After pushing the gem and updating local gems, i have received the same error. Here's the stacktrace:

$ gem update --system
...
$ gem update -V --backtrace
...
Updating breakpoint-slicer
ERROR:  While executing gem ... (NoMethodError)
    undefined method `satisfied_by?' for #<Gem::Version "1.2">
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/source_local.rb:60:in `block in find_gem'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/source_local.rb:56:in `each'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/source_local.rb:56:in `find_gem'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/dependency_installer.rb:285:in `find_spec_by_name_and_version'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/dependency_installer.rb:110:in `available_set_for'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/dependency_installer.rb:322:in `install'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/commands/update_command.rb:97:in `update_gem'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/commands/update_command.rb:111:in `block in update_gems'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/commands/update_command.rb:110:in `each'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/commands/update_command.rb:110:in `update_gems'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/commands/update_command.rb:79:in `execute'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/command.rb:305:in `invoke_with_build_args'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/command_manager.rb:170:in `process_args'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/command_manager.rb:130:in `run'
        c:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/gem_runner.rb:60:in `run'
        c:/Ruby200-x64/bin/gem:21:in `<main>'

[drbrain]

I was unable to reproduce the issue with the information you gave me, but I was able to fix it from the backtrace. Can you double check with RubyGems master?

You should be able to run ruby -Ilib bin/gem update on a checkout and have it work without problem.

Also, do you have .gem files in the directory you're running gem update from?

[lolmaus]

I worked around my issue by uninstalling my gem and then installing it again manually.

As i don't know how to reproduce it, i can't test your solution.

But it looks solid anyway, thank you for your kind effort.