Inconsistent evaluation of "~>" depending on whether it is a binding constraint or has slack

[hedgehog]

With Chef 0.9.14 installed this Gemfile has cucumber introduced into it:

gem 'chef', "~>0.9.14"
gem "cucumber", ">= 0"

and is processed by bundle update and you'll see the correct error:

Bundler could not find compatible versions for gem "json":
  In Gemfile:
    chef (~> 0.9.14) depends on
      json (<= 1.4.6, >= 1.4.4)

    aruba (~> 0.3.5) depends on
      json (1.5.1)

However, if you update the Gemfile in the following way:

gem 'chef', "~>0.9.12"
gem "cucumber", ">= 0"

then you can side step the json gem restriction and bundle update runs with out complaint - bug.

[indirect]

Your two example Gemfiles are identical, perhaps the description has a typo?

[hedgehog]

No they are not identical. My mistake was assuming everyone knows what binding and slack constraints are. The critical difference is that the change of value to 0.9.12 means the constraint ~>0.9.12 has slack when the latest is 0.9.14. When the the constraint value is 0.9.14 it is binding. Hope that explains better what is going on?

HTH?

[mscottford]

I'm having trouble reproducing this. https://gist.github.com/4689100 @hedgehog Do you know of a Gemfile that will reproduce this issue?