Update dependency conflict

Question

Update dependency conflict

pencilcheck opened this issue 11 years ago · 17 comments

Update dependency conflict:

Bundler could not find compatible versions for gem
"activesupport":
  In Gemfile:
    rails (= 4.2.0) ruby depends on
      activerecord (= 4.2.0) ruby depends on
        activesupport (= 4.2.0) ruby

    rails (= 4.2.0) ruby depends on
      actionmailer (= 4.2.0) ruby depends on
        rails-dom-testing (>= 1.0.5, ~> 1.0) ruby depends on
          activesupport (4.2.0.beta1)

Caused by this commit: 9b5d8e9

Answer 1 · 2015-01-25T11:28:08.000Z

The version constraint should be flexible enough to handle that scenario already.

Have you tried either bundle update activesupport or bundle update rails-dom-testing?

Kasper

Den 25/01/2015 kl. 11.22 skrev Penn Su notifications@github.com:

Update dependency conflict:

Bundler could not find compatible versions for gem
"activesupport":
In Gemfile:
rails (= 4.2.0) ruby depends on
activerecord (= 4.2.0) ruby depends on
activesupport (= 4.2.0) ruby
rails (= 4.2.0) ruby depends on
  actionmailer (= 4.2.0) ruby depends on
    rails-dom-testing (>= 1.0.5, ~> 1.0) ruby depends on
      activesupport (4.2.0.beta1)
Caused by this commit: 9b5d8e9

—
Reply to this email directly or view it on GitHub.

Answer 2 · 2015-01-25T18:23:31.000Z

rails-dom-testing is not in Gemfile, so bundle update rails-dom-testing does not work.
And the other does not help the situation. Same problems.

Answer 3 · 2015-01-26T20:45:28.000Z

Yeah, this is more a rubygems/bundler problem that an issue in the way we define the dependency. Just bundle update rails would work.

Answer 4 · 2015-01-26T23:25:51.000Z

It just doesn't work. I of course did that. And it just leads back to rails-dom-testing with the errors above.

Answer 5 · 2015-01-27T00:01:57.000Z

I don't know if this is a Rubygems issue or bundler issue, but it is definitely in one of those.

Answer 6 · 2015-01-27T00:21:07.000Z

So you are saying you are able to upgrade to rails 4.2 from 4.1.x etc without seeing this errors? can you explain your steps?

Answer 7 · 2015-01-27T00:27:26.000Z

Yes. Just change Rails version at gemfile and bundle update rails worked fine to me.

Answer 8 · 2015-01-27T01:02:17.000Z

What's your ruby version?

Answer 9 · 2015-01-27T01:03:47.000Z

$ bundle update rails
Fetching source index from https://rails-assets.org/
Fetching source index from https://rubygems.org/
Resolving dependencies....
Bundler could not find compatible versions for gem
"activesupport":
  In Gemfile:
    rails (= 4.2.0) ruby depends on
      activesupport (= 4.2.0) ruby

    rails (= 4.2.0) ruby depends on
      actionmailer (= 4.2.0) ruby depends on
        rails-dom-testing (>= 1.0.5, ~> 1.0) ruby depends on
          activesupport (4.2.0.beta1)

Answer 10 · 2015-01-27T01:04:40.000Z

Also, what's the harm of changing just one line? It would save so many unnecessary time and debate and github issue tracker.

Answer 11 · 2015-01-27T01:14:55.000Z

It is not just one line problem, it is a problem in one of the important
tools of the Ruby ecosystem. I can change that line but the bug will still
there and I really believe this bug need to be fixed on those libraries or
we can't work with pre versions when programming in Ruby.

On Mon, Jan 26, 2015, 23:04 Penn Su notifications@github.com wrote:

Also, what's the harm of changing just one line? It would save so many
unnecessary time and debate and github issue tracker.

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

Answer 12 · 2015-01-27T03:45:39.000Z

Well, it's not helping out anyone here with your speech here. Maybe submit a issue upstream and change the version then at least people with similar problems can upgrade to 4.2 without getting stuck.

Answer 13 · 2015-01-27T04:20:08.000Z

Yeah, agree.

We need to investigate the cause to report upstream. Just changing the
dependency will not help with this and since I couldn't reproduce this
problem I thought you could find a way to reproduce and submit the issue
upstream.

On Tue, Jan 27, 2015, 01:45 Penn Su notifications@github.com wrote:

Well, it's not helping out anyone here with your speech here. Maybe submit
a issue upstream and change the version then at least people with similar
problems can upgrade to 4.2 without getting stuck.

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

Answer 14 · 2015-01-27T04:25:53.000Z

About releasing yeah, I think it is better to do it. I just want to have
the original issue mapped and reported before we could move on.

Just be aware that this is not the only gem that you will find this
problem. Almost every gem Rails uses is pointing to pre releases and will
need to be changed, and that is a lot of work.

On Tue, Jan 27, 2015, 01:45 Penn Su notifications@github.com wrote:

Well, it's not helping out anyone here with your speech here. Maybe submit
a issue upstream and change the version then at least people with similar
problems can upgrade to 4.2 without getting stuck.

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

Answer 15 · 2015-01-27T04:41:42.000Z

I'm using ruby 2.1.3, I wonder what's your ruby version is. I am pretty sure I am using the latest bundler (1.7.12)

I don't know how to provide the environment in which the issue can be reproduced though. And where should I report to? bundler?

Answer 16 · 2015-01-27T04:45:18.000Z

I'm using 2.1.5 and same bundler version. Which is your Rubygems version?
Maybe the problem is also there.

On Tue, Jan 27, 2015, 02:41 Penn Su notifications@github.com wrote:

I'm using ruby 2.1.3, I wonder what's your ruby version is. I am pretty
sure I am using the latest bundler (1.7.12)

I don't know how to provide the environment in which the issue can be
reproduced though. And where should I report to? bundler?

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

Answer 17 · 2015-01-27T04:45:49.000Z

My rubygem version is 2.4.5