-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Unable to resolve dependencies since 1.6.0 #3059
Comments
@Who828 hey, look, an actual resolver bug! :) |
I'm having an issue that may be related... Here's my output:
grape 0.9.0 actually requires hashie >= 2.1.0 (see http://rubygems.org/gems/grape). So, although hashie 3.3.1 is a valid version for grape, I would expect bundler to use hashie >= 2.1.0, < 3.0.0 since foursquare2 requires hashie < 3.0.0. |
So this seems like a bug at first, because warden-github depends on
Addressable version requirements ~> 2.3.5 and ~> 2.2.0 are explicitly conflicting, and can never be resolved to agree. So how is that happening? :P |
Currently Bundler tries different versions of current gem and than it's parents and finally existing gems. However, when trying different versions of current gem will cause it to conflict with existing gem version and sometimes it will be unable to resolve the dependency tree correctly. Now, we will try to resolve current gems parent first then current gem and then finally the exisiting gems.
I have fixed this issue (hopefully) in this branch, https://github.com/bundler/bundler/tree/resolver_bug_fix Can you please try it once to ensure things are fixed at your end? Meanwhile I will do some regression testing before we push out a pre release version. |
Should be fixed in v1.7.9. |
@dentarg just reported the issue atmos/warden-github#39. The issue is that running
bundle
on atmos/warden-github@dae6b8e fails with the following error:I verified that this fails with all versions >= 1.6.0 of bundler but does work with 1.5.3, the last version prior to 1.6.0. Using the latest commit be3c166 also doesn't work.
The output when running bundler v1.5.3 on the repo mentioned above is:
This is what my environment looks like:
The text was updated successfully, but these errors were encountered: