Bundler incorrectly resolves release candidate dependencies #2156

Closed
jakobbuis opened this Issue Nov 11, 2012 · 3 comments

Comments

Projects
None yet
3 participants

I work on a Rails-project using version 3.2.8 that uses formtastic (it's old, I know). Relevant dependencies are:

rails
    actionmailer = 3.2.8
    actionpack = 3.2.8
    activerecord = 3.2.8
    activeresource = 3.2.8
    activesupport = 3.2.8
    bundler ~> 1.0
    railties = 3.2.8
formtastic
    actionpack >= 3.0.0beta3
    activesupport >= 3.0.0beta3

Running bundle update displays the following error:

Bundler could not find compatible versions for gem "actionpack":
  In Gemfile:
    rails (= 3.2.8) ruby depends on
      actionpack (= 3.2.8) ruby

    formtastic-rails3 (~> 0.9.10.1) ruby depends on
      actionpack (3.2.9.rc3)

Bundler seems hell-bent on using the latest and greatest version of Rails, while using 3.2.8 would satisfy formtastic just fine.

Contributor

rohit commented Nov 12, 2012

Correct if I'm wrong but won't the following FORCE 3.2.8 to be used?

rails
    actionmailer = 3.2.8
    actionpack = 3.2.8
    activerecord = 3.2.8
    activeresource = 3.2.8
    activesupport = 3.2.8
    bundler ~> 1.0
    railties = 3.2.8

Note the = 3.2.8

If I'm write please close the issue, if I'm wrong please ignore this. :)

It should! If bundler would just select rails 3.2.8, it wouldn't have any problem satisfying the dependencies. But for some strange reason, it wants to select 3.2.9.rc3 to satisfy formtastic-rails3.

I suspect the problem is that formtastic-rails3 specifies a earlier beta-version of Rails (>=3.0.0.beta3) causing bundler to conclude that using prerelease-versions is acceptable.

Contributor

rohit commented Nov 22, 2012

I don't know how to reproduce this. I tried the following Gemfile

source :rubygems

gem 'rails', '= 3.2.8'
gem 'formtastic-rails3'

Both bundle install and bundle update are working fine. I'm guessing there is more to this. Can you please follow https://github.com/carlhuda/bundler/blob/master/ISSUES.md and lastly follow the Reporting unresolved problems in the same guide and report back? Thanks!

@xaviershay xaviershay closed this Aug 18, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment