Updating from Rails 4.0 to 4.1 Gives SASS-Rails Railties Version Conflicts

Updating from Rails 4.0 to 4.1 gives sass-rails railties version conflicts

From comments, update to:

gem 'rails', '~> 4.1.1'

sass-rails requires sprockets 2.0.0 but rails 4.1.0 requires sprockets 2.12.1

Some older versions of Bundler have a bug that can cause this failure to resolve. Updating to the latest version might help.

Run this to update:

gem install bundler

Failed to upgrade Rails from 4.20 to 5.2.3

You have to fix gems version, for example:

Bundler could not find compatible versions for gem "railties":

activeadmin was resolved to 2.5.0, which depends on
railties (< 6.1, >= 5.2)

coffee-rails (~> 4.1.0) was resolved to 4.1.0, which depends on
railties (< 5.0, >= 4.0.0)

devise was resolved to 4.2.1, which depends on
railties (< 5.1, >= 4.1.0)

activeadmin was resolved to 2.5.0, which depends on
jquery-rails (~> 4.2) was resolved to 4.3.5, which depends on
railties (>= 4.2.0)

rails (~> 5.2.3) was resolved to 5.2.4.rc1, which depends on
railties (= 5.2.4.rc1)

This tells you that coffee-rails depends on railties < 5.0, devise on railties < 5.1, and rails 5.23 depends on railties 5.2.4.rc1. So you should ask for newer versions of devise and coffee-rails in that case.

Bundler could not find compatible versions for gem "activerecord":

acts-as-taggable-on was resolved to 5.0.0, which depends on
activerecord (>= 4.2.8)

deep_cloneable was resolved to 3.0.0, which depends on
activerecord (< 7, >= 3.1.0)

oink was resolved to 0.10.1, which depends on
activerecord

rails (~> 5.2.3) was resolved to 5.2.4.rc1, which depends on
activerecord (= 5.2.4.rc1)

activeadmin was resolved to 1.4.3, which depends on
ransack (>= 1.8.7) was resolved to 1.8.10, which depends on
activerecord (< 5.2, >= 3.0)

This one tells you that you are requiring activeadmin 1.4.3 that depends on ransak >= 1.8.7 that depends on activerecord < 5.2, but rails 5.2.3 depends on activerecord 5.2.4.rc1. You need to update your activeadmin and ransack gems.

Fix the conflicts for each gem telling your gemfile which version to use for, you can check them at rubygems.

You have the gems installed on your system, but you have conflicts between other gems' dependencies.

Updating rails from 4.2.8 to 5.0.2

You might want to remove quiet_assets from your application, because even the latest version (1.1.0 at the moment), does not support Rails 5.0. Furthermore on README on GitHub tells us that the gem is deprecated.



Related Topics



Leave a reply



Submit