randombits
randombits

Reputation: 48490

Conflict updating to Rails 3.1.10

I am currently running one of my Rails applications on version 3.1.3. My gemfile always listed:

gem 'rails', '3.1.3'

This worked just fine. In an effort to move to 3.1.10, I changed my Gemfile to the following:

gem 'rails', '~> 3.1.10'

Surprisingly, things break when I run bundle update rails after that change:

Bundler could not find compatible versions for gem "multi_json":
  In Gemfile:
    twitter (>= 0) ruby depends on
      multi_json (~> 1.3) ruby

    fnordmetric (>= 0) ruby depends on
      multi_json (1.2.0)

Just as a test, I tried changing the gem version to '>= 3.1.0' and that installed without any quims, albeit it went to 3.2, which I'm not ready for just yet on this particular application.

Any suggestions for getting this thing running on 3.1.10 which was released today to address a security vulnerability?

Also an update:

I am having absolutely no trouble stashing Gemfile.lock away and starting from Rails 3.1.4. As soon as I try to go to 3.1.5+, this is where all the trouble begins.

Upvotes: 2

Views: 452

Answers (2)

Richard
Richard

Reputation: 276

Make the change in your Gemfile to

gem 'rails', '3.1.10'

Then try running

bundle update

instead of

bundle install

I can't see your Gemfile but this should will allow the bundler to try and find compatible Gem matches. If you have hard code a Gem revision you might have to relax it and repeat the update. Good luck!

Upvotes: 2

Spain Train
Spain Train

Reputation: 6006

Looking at the gems, it appears that oauth2 lists "multi_json ~> 1.0" and ActiveSupport 3.1.10 lists "multi_json < 1.3, >= 1.0" as the dependencies, so that should resolve. I've run into strangeness like this and fixed it by running

gem uninstall <relevant gems>

then running bundle install again. So maybe try

gem uninstall oauth2 multi_json activesupport

then bundle install

Edit

gem uninstall twitter multi_json fnordmetric

Upvotes: 0

Related Questions