I was trying to upgrade my current rails 5.0.2 version to the latest rails 5.1.0 version by running bundle update rails after adding gem 'rails', '~> 5.1' on my Gemfile and I got this error message.
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
rails (~> 5.1) was resolved to 5.1.0, which depends on
activejob (= 5.1.0) was resolved to 5.1.0, which depends on
globalid (>= 0.3.6) was resolved to 0.4.0, which depends on
activesupport (>= 4.2.0)
jbuilder (~> 2.5) was resolved to 2.6.1, which depends on
activesupport (< 5.1, >= 3.0.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
activesupport (= 5.1.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
activesupport (= 5.1.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
activesupport (= 5.1.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
activesupport (= 5.1.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
activesupport (= 5.1.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
activesupport (= 5.1.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
activesupport (= 5.1.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
actionpack (= 5.1.0) was resolved to 5.1.0, which depends on
rails-dom-testing (~> 2.0) was resolved to 2.0.2, which depends on
activesupport (< 6.0, >= 4.2.0)
rails (~> 5.1) was resolved to 5.1.0, which depends on
sprockets-rails (>= 2.0.0) was resolved to 3.2.0, which depends on
activesupport (>= 4.0)
This sounds like you need to try and upgrade to a newer version of jbuilder. However, looking at RubyGems the current dependancies for Jbuilder still say:
activesupport < 5.1, >= 3.0.0
IF this is the case, JBuilder doesn't yet support the more recent Activesupport, now required by Rails 5.1 - so perhaps JBuilder isn't yet available in Rails 5.1.
If you need to get the newer Rails, then you should probably consider:
Checking to see if there is a roadmap in JBuilder for this.
Raising a JBuilder ticket requesting support for that later Rails version.
You could try an override - since it may potentially just work, and that <5.1 is just since it's not yet been tested with the more recent version - just be prepared for glitches if there are genuine compatibility issues. I'd definitely rerun the whole of your test suite after trying that.
The alternative is to wait a little bit - this is a very fresh release - give other packages a chance to catch up with it.
Deleting Gemfile.lock then running bundle worked for me
Related
I have multiple gems failing on my app. My bundler is not able to find compatible versions for all. I also do not have a 'Gemfile.lock' and it does not get created on bundle install. As follows:
Bundler could not find compatible versions for gem "actionpack":
In Gemfile:
draper was resolved to 2.1.0, which depends on
actionpack (>= 3.0)
jquery-datatables-rails (~> 3.3.0) was resolved to 3.3.0, which depends on
actionpack (>= 3.1)
rails (= 4.1.6) was resolved to 4.1.6, which depends on
actionpack (= 4.1.6)
rails-api was resolved to 0.4.1, which depends on
actionpack (>= 3.2.11)
ransack was resolved to 1.8.10, which depends on
actionpack (< 5.2, >= 3.0)
redis-rails was resolved to 5.0.2, which depends on
redis-actionpack (< 6, >= 5.0) was resolved to 5.1.0, which depends on
actionpack (< 7, >= 4.0)
Bundler could not find compatible versions for gem "activemodel":
In Gemfile:
acts_as_api (= 1.0.1) was resolved to 1.0.1, which depends on
activemodel (>= 3.0.0)
carrierwave (>= 1.0.0.beta, < 2.0) was resolved to 1.3.2, which depends on
activemodel (>= 4.0.0)
paperclip (~> 4.3.2) was resolved to 4.3.7, which depends on
activemodel (>= 3.2.0)
rails (= 4.1.6) was resolved to 4.1.6, which depends on
activemodel (= 4.1.6)
Bundler could not find compatible versions for gem "activerecord":
In Gemfile:
activerecord-postgres-hstore was resolved to 0.7.8, which depends on
activerecord (>= 3.1)
audited (~> 4.7) was resolved to 4.8.0, which depends on
activerecord (< 5.3, >= 4.0)
rails (= 4.1.6) was resolved to 4.1.6, which depends on
activerecord (= 4.1.6)
I am trying it again with the following specifications and getting the same result.
bundler: 1.16.6
rails: 4.1.6
ruby: 2.3.8
ubuntu: 18.04
I can see my gems when I do gem list but it still says bundler is not able to find anything for rails 4.1.6.
Add source in your Gemfile like below:
Gemfile
source 'https://rubygems.org'
delete everything form your Gemfile.lock and run bundle install
please help me here, I was upgrading ruby and rails and also dependent gems need upgrades.
Earlier the ruby version was 2.3.0 and rails was 4.2.x, now upgrading to 2.6.0 and rails to 6.0.4
If you see below error, actionpack is resolved to 6.0.4 and public_activity also needs actionpack >=3.0.0 which means 6.0.4 should be acceptable and obviously rails using version = 6.0.4, So why its an error. can some expert throw some knowledge on it.
Bundler could not find compatible versions for gem "actionpack":
In Gemfile:
actionpack (~> 6.0, >= 6.0.4)
public_activity (~> 1.6, >= 1.6.4) was resolved to 1.6.4, which depends on
actionpack (>= 3.0.0)
rails (= 6.0.4) was resolved to 6.0.4, which depends on
actionpack (= 6.0.4)
Bundler could not find compatible versions for gem "activemodel":
In Gemfile:
activemodel (~> 6.0, >= 6.0.4)
active_model_otp was resolved to 1.2.0, which depends on
activemodel
paperclip (~> 6.1) was resolved to 6.1.0, which depends on
activemodel (>= 4.2.0)
rails (= 6.0.4) was resolved to 6.0.4, which depends on
activemodel (= 6.0.4)
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
activesupport (~> 6.0, >= 6.0.4)
delayed_job (~> 4.1, >= 4.1.9) was resolved to 4.1.9, which depends on
activesupport (>= 3.0, < 6.2)
factory_girl_rails (= 4.2.1) was resolved to 4.2.1, which depends on
factory_girl (~> 4.2.0) was resolved to 4.2.0, which depends on
activesupport (>= 3.0.0)
jbuilder (~> 2.10) was resolved to 2.11.2, which depends on
activesupport (>= 5.0.0)
paperclip (~> 6.1) was resolved to 6.1.0, which depends on
activesupport (>= 4.2.0)
rails (= 6.0.4) was resolved to 6.0.4, which depends on
activesupport (= 6.0.4)
Bundler could not find compatible versions for gem "capybara":
In Gemfile:
capybara (= 2.1.0)
cucumber-rails (= 1.4.0) was resolved to 1.4.0, which depends on
capybara (>= 1.1.2)
Bundler could not find compatible versions for gem "rack":
In Gemfile:
rails (= 6.0.4) was resolved to 6.0.4, which depends on
actionpack (= 6.0.4) was resolved to 6.0.4, which depends on
rack (~> 2.0, >= 2.0.8)
sprockets (= 2.11.0) was resolved to 2.11.0, which depends on
rack (~> 1.0)
Bundler could not find compatible versions for gem "rails":
In Gemfile:
rails (= 6.0.4)
cucumber-rails (= 1.4.0) was resolved to 1.4.0, which depends on
rails (>= 3.0.0)
Bundler could not find compatible versions for gem "railties":
In Gemfile:
coffee-rails (~> 5.0) was resolved to 5.0.0, which depends on
railties (>= 5.2.0)
devise was resolved to 4.8.0, which depends on
railties (>= 4.1)
doorkeeper (= 4.2.5) was resolved to 4.2.5, which depends on
railties (>= 4.2)
factory_girl_rails (= 4.2.1) was resolved to 4.2.1, which depends on
railties (>= 3.0.0)
rails (= 6.0.4) was resolved to 6.0.4, which depends on
railties (= 6.0.4)
Bundler could not find compatible versions for gem "rotp":
In Gemfile:
rotp (~> 3.3.0)
active_model_otp was resolved to 1.2.0, which depends on
rotp
Bundler could not find compatible versions for gem "will_paginate":
In Gemfile:
will_paginate (= 3.0.5)
bootstrap-will_paginate (= 0.0.10) was resolved to 0.0.10, which depends on
will_paginate
I'm answering my own question, Since It got resolved after several iterations.
I removed Gemfile.lock and in Gemfile I start entering Gems one by one and then run bundle install each time, then eventually this problem did not occur.
I am working on Ruby on Rails application. I am trying to upgrade the rails version from 4.2 to 5.0
I have changed the rails dependency in engine's gemspec file.
On running bundle update in engine it is showing the following error -
Bundler could not find compatible versions for gem "actionmailer":
In Gemfile:
engine was resolved to 0.0.1, which depends on
rails (~> 5.0) was resolved to 5.2.4.4, which depends on
actionmailer (= 5.2.4.4)
simple_token_authentication was resolved to 1.17.0, which depends on
actionmailer (>= 3.2.6, < 7)
Bundler could not find compatible versions for gem "actionpack":
In Gemfile:
engine was resolved to 0.0.1, which depends on
rails (~> 5.0) was resolved to 5.2.4.4, which depends on
actionpack (= 5.2.4.4)
rspec-rails was resolved to 4.0.2, which depends on
actionpack (>= 4.2)
simple_token_authentication was resolved to 1.17.0, which depends on
actionpack (>= 3.2.6, < 7)
Bundler could not find compatible versions for gem "activerecord":
In Gemfile:
paranoia (~> 2.2) was resolved to 2.4.3, which depends on
activerecord (>= 4.0, < 6.2)
engine was resolved to 0.0.1, which depends on
rails (~> 5.0) was resolved to 5.2.4.4, which depends on
activerecord (= 5.2.4.4)
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
factory_girl_rails was resolved to 4.9.0, which depends on
factory_girl (~> 4.9.0) was resolved to 4.9.0, which depends on
activesupport (>= 3.0.0)
engine was resolved to 0.0.1, which depends on
rails (~> 5.0) was resolved to 5.2.4.4, which depends on
activesupport (= 5.2.4.4)
rspec-rails was resolved to 4.0.2, which depends on
activesupport (>= 4.2)
Bundler could not find compatible versions for gem "rails":
In Gemfile:
engine was resolved to 0.0.1, which depends on
activeadmin (= 1.0.0.pre2) was resolved to 1.0.0.pre2, which depends on
rails (>= 3.2, < 5.0)
engine was resolved to 0.0.1, which depends on
rails (~> 5.0)
Bundler could not find compatible versions for gem "railties":
In Gemfile:
factory_girl_rails was resolved to 4.9.0, which depends on
railties (>= 3.0.0)
engine was resolved to 0.0.1, which depends on
rails (~> 5.0) was resolved to 5.2.4.4, which depends on
railties (= 5.2.4.4)
rspec-rails was resolved to 4.0.2, which depends on
railties (>= 4.2)
I tried to delete gemfile.lock of engine and run command bundle install then it is showing the following error -
Bundler could not find compatible versions for gem "rails":
In Gemfile:
engine was resolved to 0.0.1, which depends on
activeadmin (= 1.0.0.pre2) was resolved to 1.0.0.pre2, which depends on
rails (>= 3.2, < 5.0)
engine1 was resolved to 0.0.1, which depends on
engine2 was resolved to 0.0.1, which depends on
rails (~> 5.0)
Do anyone have any idea how to resolve it? Please help!
Re-read the error message, it says exactly what's going on.
Bundler could not find compatible versions for gem "rails":
There is no single version of rails that satisfies all requirements. From your issue description I see that you're trying to update to 5, so lets see what is not okay with 5.
In Gemfile:
engine was resolved to 0.0.1, which depends on
activeadmin (= 1.0.0.pre2)
Engine depends on activeadmin with a fixed version
was resolved to 1.0.0.pre2, which depends on
rails (>= 3.2, < 5.0)
This version requires rails of at least 3.2 and less than 5.0. This disallows rails 5. You'll need to update activeadmin in engine before you update rails in the application using the engine.
I'm trying to use a gem spree, which depends on kaminari (~> 1.0.1). In my Gemfile.lock, I have kaminari (= 1.1.1). This satisfies the requirement for spree, since it's greater than or equal to the last digit. However, I'm getting this error when I try to bundle:
Bundler could not find compatible versions for gem "kaminari":
In snapshot (Gemfile.lock):
kaminari (= 1.1.1)
In Gemfile:
activeadmin (~> 1.3) was resolved to 1.3.0, which depends on
kaminari (>= 0.15)
rails_admin (~> 1.3) was resolved to 1.3.0, which depends on
kaminari (< 2.0, >= 0.14)
spree (~> 3.5.0) was resolved to 3.5.0, which depends on
spree_core (= 3.5.0) was resolved to 3.5.0, which depends on
kaminari (~> 1.0.1)
Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
I'm not sure why v1.1.1 doesn't satisfy the requirements for all the gems in question, since it seems to fall within the range for all gems in question. I tried running bundle update, but then I get a long list of gem incompatibilities, none of which make sense to me either, since their requirements all seem to fall within range of the version I have in my lock file. For instance,
Bundler could not find compatible versions for gem "activemodel":
In Gemfile:
carrierwave (~> 1.2) was resolved to 1.2.2, which depends on
activemodel (>= 4.0.0)
rails (~> 5.1.6) was resolved to 5.1.6, which depends on
activemodel (= 5.1.6)
web-console (>= 3.3.0) was resolved to 3.6.2, which depends on
activemodel (>= 5.0)
Bundler could not find compatible versions for gem "activerecord":
In Gemfile:
annotate (~> 2.7) was resolved to 2.7.4, which depends on
activerecord (< 6.0, >= 3.2)
friendly_id (~> 5.2) was resolved to 5.2.4, which depends on
activerecord (>= 4.0.0)
rails (~> 5.1.6) was resolved to 5.1.6, which depends on
activerecord (= 5.1.6)
activeadmin (~> 1.3) was resolved to 1.3.0, which depends on
ransack (~> 1.3) was resolved to 1.8.8, which depends on
activerecord (>= 3.0)
spree_gateway (~> 3.3) was resolved to 3.3.3, which depends on
spree_extension was resolved to 0.0.5, which depends on
activerecord (>= 4.2)
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
activeadmin (~> 1.3) was resolved to 1.3.0, which depends on
arbre (>= 1.1.1) was resolved to 1.1.1, which depends on
activesupport (>= 3.0.0)
carrierwave (~> 1.2) was resolved to 1.2.2, which depends on
activesupport (>= 4.0.0)
activeadmin (~> 1.3) was resolved to 1.3.0, which depends on
inherited_resources (>= 1.7.0) was resolved to 1.8.0, which depends on
has_scope (~> 0.6) was resolved to 0.7.2, which depends on
activesupport (>= 4.1)
jbuilder (~> 2.5) was resolved to 2.7.0, which depends on
activesupport (>= 4.2.0)
kaminari (~> 1.0.1) was resolved to 1.0.1, which depends on
activesupport (>= 4.1.0)
rails (~> 5.1.6) was resolved to 5.1.6, which depends on
activesupport (= 5.1.6)
activeadmin (~> 1.3) was resolved to 1.3.0, which depends on
ransack (~> 1.3) was resolved to 1.8.8, which depends on
activesupport (>= 3.0)
spring was resolved to 2.0.2, which depends on
activesupport (>= 4.2)
sass-rails (~> 5.0) was resolved to 5.0.7, which depends on
sprockets-rails (< 4.0, >= 2.0) was resolved to 3.2.1, which depends on
activesupport (>= 4.0)
Bundler could not find compatible versions for gem "kaminari":
In Gemfile:
kaminari (~> 1.0.1)
activeadmin (~> 1.3) was resolved to 1.3.0, which depends on
kaminari (>= 0.15)
rails_admin (~> 1.3) was resolved to 1.3.0, which depends on
kaminari (< 2.0, >= 0.14)
Bundler could not find compatible versions for gem "spree_core":
In Gemfile:
spree (~> 3.5.0) was resolved to 3.5.0, which depends on
spree_core (= 3.5.0)
spree_gateway (~> 3.3) was resolved to 3.3.3, which depends on
spree_core (< 4.0, >= 3.1.0)
These errors raise a whole new set of questions, since I don't see any conflicts in versions for any of the gems.
For activemodel, why can't it use 5.1.6? Doesn't that satisfy all the requirements?
For activerecord, why can't it use 5.1.6? Doesn't that satisfy all the requirements?
For activesupport, why can't it use 5.1.6? Doesn't that satisfy all the requirements?
For kaminari, why can't it use 1.0.1? Doesn't that satisfy all the requirements?
For spree_core, why can't it use 3.5.0? Doesn't that satisfy all the requirements?
How does one go about resolving these issues? I've tried running bundle update for all gems and for individual gems, but I get the same error message either way.
This satisfies the requirement for spree, since it's greater than or equal to the last digit.
That's not quite correct, the docs for Bundler's Gemfile state:
The specifier ~> has a special meaning, best shown by example. ~> 2.0.3 is identical to >= 2.0.3 and < 2.1.
So in your case, for kaminari, ~> 1.0.1 would mean '>= 1.0.1' and '< 1.1', which (obviously) 1.1.1 does not meet.
As for the others, everything looks to me like it'd work, though I notice a lot of the ones failing need something to do with spree or kaminari, so maybe fixing the one will help those. The others could also (maybe) be cascading errors, kind of like a missing parenthesis or comma in one place can cause syntax errors through the entire file, maybe just the one error is cascading through the rest of the bundle, I'd take care of Kaminari and then see what you're left with.
Have you verified whether the version of spree you're trying to install is compatible with the higher version of kaminari? try downgrading the kaminari gem to "~> 1.0.1" to see if that helps.
if that does not work, then another suggestion would be to run "bundle update" on your current gemset "before" you add "spree" to your Gemfile to make sure you are working with all the latest versions of your currently installed gems.
I'm trying to run an old project but I have problem. I'm using:
Ruby - 1.9.3
Rails - 3.0.20
I'm getting the following error while installing the gems. How do I install these gems?
Resolving dependencies...................................................................................................................
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
active_form was resolved to 1.0.4, which depends on
activesupport (>= 3.0.0)
active_form was resolved to 1.0.4, which depends on
activesupport (>= 3.0.0)
paper_trail (~> 3.0.1) was resolved to 3.0.9, which depends on
activesupport (< 5.0, >= 3.0)
paperclip was resolved to 4.3.1, which depends on
activesupport (>= 3.2.0)
rails (= 3.0.20) was resolved to 3.0.20, which depends on
activesupport (= 3.0.20)
rails (= 3.0.20) was resolved to 3.0.20, which depends on
activesupport (= 3.0.20)
rails (= 3.0.20) was resolved to 3.0.20, which depends on
activesupport (= 3.0.20)
rails (= 3.0.20) was resolved to 3.0.20, which depends on
activesupport (= 3.0.20)
rails (= 3.0.20) was resolved to 3.0.20, which depends on
activesupport (= 3.0.20)
rspec-rails (~> 2.14.0) was resolved to 2.14.2, which depends on
activesupport (>= 3.0)
If you carefully read the explanation, it's quite clear where the problem is.
paperclip was resolved to 4.3.1, which depends on
activesupport (>= 3.2.0)
This specific gem requires an activesupport version which is at least 3.2, but your project has Rails (and consequently activesupport) freezed at 3.0.20.
You need to use a paperclip version which is compatible with older versions of Rails. Edit your Gemfile and specify an older paperclip version.
You can check the paperclip dependencies on RubyGems and select the proper version.
You should decrease your paperclip gem version.