I don't understand what's the problem here while installing gem. Here are the details of error log
Bundler could not find compatible versions for gem "faraday":
In snapshot (Gemfile.lock):
faraday (= 0.12.1)
In Gemfile:
faraday
mailchimp3 (= 1.3.1) was resolved to 1.3.1, which depends on
faraday (~> 0.9.1)
stripe was resolved to 2.10.0, which depends on
faraday (~> 0.9)
FYI: I'm using rails 5, ruby 2.4.1.
Related
Running bundle or bundle update could not solve the problem. I've tried removing the Gemfile.lock. Seems weird that bundler could not decide that jwt (~> 2.1) should satisfy jwt (~> 1.5).
Bundler could not find compatible versions for gem "jwt":
In Gemfile:
knock was resolved to 2.1.1, which depends on
jwt (~> 1.5)
pusher-chatkit-server (~> 1.1.0) was resolved to 1.1.0, which depends on
pusher-platform (~> 0.11.2) was resolved to 0.11.2, which depends on
jwt (~> 2.1)
Bundler could not find compatible versions for gem "pg":
In Gemfile:
pg (= 0.18.4)
multilang-hstore (= 1.0.0) was resolved to 1.0.0, which depends on
pg (>= 0.0.1)
Bundler could not find compatible versions for gem "responders":
In Gemfile:
responders (= 1.1.2)
devise (= 3.4.1) was resolved to 3.4.1, which depends on
responders
Bundler could not find compatible versions for gem "rubyzip":
In Gemfile:
axlsx (= 2.0) was resolved to 2.0.0, which depends on
rubyzip (= 0.9.9)
zip-zip was resolved to 0.3, which depends on
rubyzip (>= 1.0.0)
Have to create static pages using the same layout of rest of the spree commerce site. Spree_static_content is the gem I tried using. However, getting following error on bundle install.
Bundler could not find compatible versions for gem "spree_core":
In snapshot (Gemfile.lock):
spree_core (= 3.3.1)
In Gemfile:
spree (~> 3.3.0) was resolved to 3.3.1, which depends on
spree_core (= 3.3.1)
spree (~> 3.3.0) was resolved to 3.3.1, which depends on
spree_core (= 3.3.1)
spree (~> 3.3.0) was resolved to 3.3.1, which depends on
spree_core (= 3.3.1)
spree (~> 3.3.0) was resolved to 3.3.1, which depends on
spree_core (= 3.3.1)
spree (~> 3.3.0) was resolved to 3.3.1, which depends on
spree_core (= 3.3.1)
spree_gateway (~> 3.3) was resolved to 3.3.0, which depends on
spree_core (< 4.0, >= 3.1.0)
spree_gateway (~> 3.3) was resolved to 3.3.0, which depends on
spree_core (< 4.0, >= 3.1.0)
spree_static_content was resolved to 3.0.1, which depends on
spree_core (~> 3.0.0)
Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
Found the solution this issue is because of dependent gem globalize with Rails 5. Add the following to your Gemfile:
gem 'globalize', git: 'https://github.com/globalize/globalize'
gem 'activemodel-serializers-xml'
Next, bundle install and you will net the above-mentioned error in questions.
I'm trying to upgrade Nokogiri to version 1.7:
gem 'nokogiri', '~> 1.7'
but when I run:
bundle update --source nokogiri
I get:
Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies.............
Bundler could not find compatible versions for gem "nokogiri":
This is in my Gemfile:
nokogiri (~> 1.7)
activemerchant (~> 1.58.0) was resolved to 1.58.0, which depends on
nokogiri (~> 1.4)
activemerchant (~> 1.58.0) was resolved to 1.58.0, which depends on
nokogiri (~> 1.4)
capybara was resolved to 2.7.0, which depends on
nokogiri (>= 1.3.3)
cucumber-rails was resolved to 1.4.3, which depends on
nokogiri (~> 1.5)
haml-rails was resolved to 0.9.0, which depends on
html2haml (>= 1.0.1) was resolved to 2.0.0, which depends on
nokogiri (~> 1.6.0)
haml-rails was resolved to 0.9.0, which depends on
html2haml (>= 1.0.1) was resolved to 2.0.0, which depends on
nokogiri (~> 1.6.0)
rails (>= 4.2.6, ~> 4.2) was resolved to 4.2.6, which depends on
actionmailer (= 4.2.6) was resolved to 4.2.6, which depends on
actionview (= 4.2.6) was resolved to 4.2.6, which depends on
rails-html-sanitizer (>= 1.0.2, ~> 1.0) was resolved to 1.0.3, which depends on
loofah (~> 2.0) was resolved to 2.0.3, which depends on
nokogiri (>= 1.5.9)
roo (~> 2.4.0) was resolved to 2.4.0, which depends on
nokogiri (~> 1)
roo-xls was resolved to 1.0.0, which depends on
nokogiri
capybara was resolved to 2.7.0, which depends on
xpath (~> 2.0) was resolved to 2.0.0, which depends on
nokogiri (~> 1.3)
Does anyone have an idea why it can't find it? I see on rubygems.org that the current version is 1.7.1 as well as on github. Do I need to specify the github source?
The problem is here:
haml-rails was resolved to 0.9.0, which depends on
html2haml (>= 1.0.1) was resolved to 2.0.0, which depends on
nokogiri (~> 1.6.0)
As you can see, html2haml depends on nokogiri (~> 1.6.0), that is not 1.7. You either need to update html2haml (so it dependency becomes nokogiri (~> 1.6)) or use nokogiri, ~> 1.6.
You could try deleting your Gemfile.lock file and running bundle install again, but i will only recommend doing it if you are not yet in production.
I think other gems are depedent on Nokogiri, so
try bundle update.
bundle update will resolve a dependency tree and try and install versions that satisfy all the other gems dependencies.
I need help understanding this bundler error message:
Bundler could not find compatible versions for gem "faraday":
In Gemfile:
metainspector (= 5.4.1) was resolved to 5.4.1, which depends on
faraday-http-cache (~> 2.0) was resolved to 2.0.0, which depends on
faraday (~> 0.8)
metainspector (= 5.4.1) was resolved to 5.4.1, which depends on
faraday_middleware (~> 0.11) was resolved to 0.11.0.1, which depends on
faraday (< 1.0, >= 0.7.4)
instagram-continued (= 1.2.1) was resolved to 1.2.1, which depends on
faraday (~> 0.9.2)
metainspector (= 5.4.1) was resolved to 5.4.1, which depends on
faraday (~> 0.11)
sendgrid-ruby (= 1.1.6) was resolved to 1.1.6, which depends on
faraday (~> 0.9)
Maybe I’m not understanding it correctly, but I don’t see where the issue is with faraday. All these dependencies seem to require a faraday version greater or equal than 0.7.4 but less than 1.0. My current version is 0.9.2. I've always understood the ~> pointer to indicate greater than or equal to. Is that incorrect?
Here is the relevant portion of my Gemfile:
gem 'instagram-continued', '1.2.1', require: "instagram"
gem 'metainspector', '5.4.1'