I listed the below
gem in my gemfile and after running "bundle install" i get the below
error.
Can someone tell me what to do, where to list or edit the correct
gems/dependencies
gem file :
gem 'rails', '~> 5.0.2'
gem 'shopify_app'
===========================
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
shopify_app x64-mingw32 was resolved to 7.0.10, which depends on
shopify_api (~> 4.2) x64-mingw32 was resolved to 4.2.0, which
depends on
activeresource x64-mingw32 was resolved to 2.0.1, which depends
on
activesupport (= 2.0.1) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
activejob (= 5.0.2) x64-mingw32 was resolved to 5.0.2, which
depends on
globalid (>= 0.3.6) x64-mingw32 was resolved to 0.4.0, which
depends on
activesupport (>= 4.2.0) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
activesupport (= 5.0.2) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
activesupport (= 5.0.2) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
activesupport (= 5.0.2) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
activesupport (= 5.0.2) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
activesupport (= 5.0.2) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
activesupport (= 5.0.2) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
activesupport (= 5.0.2) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
actionpack (= 5.0.2) x64-mingw32 was resolved to 5.0.2, which
depends on
rails-dom-testing (~> 2.0) x64-mingw32 was resolved to 2.0.2, which
depends on
activesupport (< 6.0, >= 4.2.0) x64-mingw32
rails (~> 5.0.2) x64-mingw32 was resolved to 5.0.2, which depends on
sprockets-rails (>= 2.0.0) x64-mingw32 was resolved to 3.2.0, which
depends on
activesupport (>= 4.0) x64-mingw32
Bundler could not find compatible versions for gem "rails":
In Gemfile:
rails (~> 5.0.2) x64-mingw32
shopify_app x64-mingw32 was resolved to 0.1.0, which depends on
rails (~> 3) x64-mingw32
D:\Ruby On Rails\firstRailsProject>rails s
Could not find gem 'shopify_app x64-mingw32' in any of the gem sources
listed in
your Gemfile.
Run bundle install to install missing gems.
if you read carefuly the github readme for shopify_app, you'll find that there are some issues between ruby R versions:
so, you must do:
gem 'shopify_app'
gem 'activeresource', github: 'rails/activeresource'
for more info -> github shoopy
Related
I'm upgrading rails from 4.2 to 5.0, and I'm getting some mean dependency issues.
When I run bundle update i get the following output.
The thing is that when i look through the messages, it looks like the gems should be able to install just fine when looking at the version requirements.
I also tried to delete my Gemfile.lock, that didn't help.
Any suggestions would be appreciated.
Bundler could not find compatible versions for gem "actionpack":
In Gemfile:
activeadmin (~> 1.1.0) was resolved to 1.1.0, which depends on
inherited_resources (~> 1.7) was resolved to 1.10.0, which depends on
actionpack (< 6.0, >= 5.0)
rails (= 5.0.0) was resolved to 5.0.0, which depends on
actionpack (= 5.0.0)
ransack (= 1.8.10) was resolved to 1.8.10, which depends on
actionpack (< 5.2, >= 3.0)
route_translator (= 5.0.0) was resolved to 5.0.0, which depends on
actionpack (< 5.1, >= 5.0.0)
simple_form (= 3.5.0) was resolved to 3.5.0, which depends on
actionpack (< 5.2, > 4)
slim-rails (~> 3.2.0) was resolved to 3.2.0, which depends on
actionpack (>= 3.1)
Bundler could not find compatible versions for gem "activeadmin":
In Gemfile:
activeadmin (~> 1.1.0)
activeadmin_quill_editor (= 0.2.0) was resolved to 0.2.0, which depends on
activeadmin (>= 1.0)
Bundler could not find compatible versions for gem "activemodel":
In Gemfile:
openid_connect (~> 1.2.0) was resolved to 1.2.0, which depends on
activemodel
paperclip (= 5.2.1) was resolved to 5.2.1, which depends on
activemodel (>= 4.2.0)
rails (= 5.0.0) was resolved to 5.0.0, which depends on
activemodel (= 5.0.0)
simple_form (= 3.5.0) was resolved to 3.5.0, which depends on
activemodel (< 5.2, > 4)
Bundler could not find compatible versions for gem "activerecord":
In Gemfile:
friendly_id (= 5.0.5) was resolved to 5.0.5, which depends on
activerecord (>= 4.0.0)
rails (= 5.0.0) was resolved to 5.0.0, which depends on
activerecord (= 5.0.0)
ransack (= 1.8.10) was resolved to 1.8.10, which depends on
activerecord (< 5.2, >= 3.0)
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
paperclip (= 5.2.1) was resolved to 5.2.1, which depends on
activesupport (>= 4.2.0)
rails (= 5.0.0) was resolved to 5.0.0, which depends on
activesupport (= 5.0.0)
ransack (= 1.8.10) was resolved to 1.8.10, which depends on
activesupport (< 5.2, >= 3.0)
route_translator (= 5.0.0) was resolved to 5.0.0, which depends on
activesupport (< 5.1, >= 5.0.0)
Bundler could not find compatible versions for gem "autoprefixer-rails":
In Gemfile:
autoprefixer-rails (~> 9.7.4)
bootstrap (~> 4.4.1) was resolved to 4.4.1, which depends on
autoprefixer-rails (>= 9.1.0)
Bundler could not find compatible versions for gem "devise":
In Gemfile:
devise (= 4.0.0)
devise-token_authenticatable (~> 0.5.3) was resolved to 0.5.3, which depends on
devise (< 4.4.0, >= 4.0.0)
Bundler could not find compatible versions for gem "execjs":
In Gemfile:
execjs (= 1.4.0)
autoprefixer-rails (~> 9.7.4) was resolved to 9.7.6, which depends on
execjs
uglifier (~> 3.0) was resolved to 3.2.0, which depends on
execjs (< 3, >= 0.3.0)
Bundler could not find compatible versions for gem "inherited_resources":
In Gemfile:
inherited_resources
activeadmin (~> 1.1.0) was resolved to 1.1.0, which depends on
inherited_resources (~> 1.7)
Bundler could not find compatible versions for gem "jquery-rails":
In Gemfile:
jquery-rails (= 4.0.0)
activeadmin (~> 1.1.0) was resolved to 1.1.0, which depends on
jquery-rails
Bundler could not find compatible versions for gem "mimemagic":
In Gemfile:
mimemagic
paperclip (= 5.2.1) was resolved to 5.2.1, which depends on
mimemagic (~> 0.3.0)
Bundler could not find compatible versions for gem "nokogiri":
In Gemfile:
nokogiri (= 1.8.2)
paperclip (= 5.2.1) was resolved to 5.2.1, which depends on
mimemagic (~> 0.3.0) was resolved to 0.3.10, which depends on
nokogiri (~> 1)
savon (~> 2.12.1) was resolved to 2.12.1, which depends on
nokogiri (>= 1.8.1)
Bundler could not find compatible versions for gem "paperclip":
In Gemfile:
paperclip (= 5.2.1)
paperclip-compression (~> 1.1) was resolved to 1.1.1, which depends on
paperclip (>= 5.2.1)
Bundler could not find compatible versions for gem "railties":
In Gemfile:
coffee-rails (= 5.0.0) was resolved to 5.0.0, which depends on
railties (>= 5.2.0)
rails (= 5.0.0) was resolved to 5.0.0, which depends on
railties (= 5.0.0)
Bundler could not find compatible versions for gem "rake":
In Gemfile:
rake (= 10.4.2)
paperclip (= 5.2.1) was resolved to 5.2.1, which depends on
mimemagic (~> 0.3.0) was resolved to 0.3.10, which depends on
rake
rails (= 5.0.0) was resolved to 5.0.0, which depends on
railties (= 5.0.0) was resolved to 5.0.0, which depends on
rake (>= 0.8.7)
Bundler could not find compatible versions for gem "responders":
In Gemfile:
responders (~> 2.3.0)
devise (= 4.0.0) was resolved to 4.0.0, which depends on
responders
activeadmin (~> 1.1.0) was resolved to 1.1.0, which depends on
inherited_resources (~> 1.7) was resolved to 1.10.0, which depends on
responders (~> 2.0)
Most likely you have some strong constraints on some particular gems in your Gemfile that's it's blocking bundle from updating a dependency.
I'm working on an old Rails 4 project and I'm having problem when running bundle install and bundle update command.
Here are the logs:
Resolving dependencies..................................................
Bundler could not find compatible versions for gem "actionpack":
In Gemfile:
active_link_to was resolved to 1.0.5, which depends on
actionpack
jquery-datatables-rails (~> 3.4) was resolved to 3.4.0, which depends on
actionpack (>= 3.1)
rails (= 4.2.8) was resolved to 4.2.8, which depends on
actionpack (= 4.2.8)
rspec-rails (~> 3.5, >= 3.5.2) was resolved to 3.9.1, which depends on
actionpack (>= 3.0)
Bundler could not find compatible versions for gem "activemodel":
In Gemfile:
carrierwave (~> 0.11.2) was resolved to 0.11.2, which depends on
activemodel (>= 3.2.0)
rails (= 4.2.8) was resolved to 4.2.8, which depends on
activemodel (= 4.2.8)
validate_url was resolved to 1.0.8, which depends on
activemodel (>= 3.0.0)
Bundler could not find compatible versions for gem "activerecord":
In Gemfile:
active_median (~> 0.1.3) was resolved to 0.1.4, which depends on
activerecord
activerecord-nulldb-adapter was resolved to 0.4.0, which depends on
activerecord (>= 2.0.0)
rails (= 4.2.8) was resolved to 4.2.8, which depends on
activerecord (= 4.2.8)
rails-erd was resolved to 1.6.0, which depends on
activerecord (>= 4.2)
seed_dump was resolved to 3.3.1, which depends on
activerecord (>= 4)
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
activesupport-json_encoder (~> 1.1) was resolved to 1.1.0, which depends on
activesupport (>= 4.1.0, < 5.0)
carrierwave (~> 0.11.2) was resolved to 0.11.2, which depends on
activesupport (>= 3.2.0)
intercom-rails was resolved to 0.4.1, which depends on
activesupport (> 3.0)
jbuilder (~> 2.0) was resolved to 2.9.1, which depends on
activesupport (>= 4.2.0)
mailjet was resolved to 1.5.4, which depends on
activesupport (>= 3.1.0)
rails (= 4.2.8) was resolved to 4.2.8, which depends on
activesupport (= 4.2.8)
rspec-rails (~> 3.5, >= 3.5.2) was resolved to 3.9.1, which depends on
activesupport (>= 3.0)
seed_dump was resolved to 3.3.1, which depends on
activesupport (>= 4)
Bundler could not find compatible versions for gem "carrierwave":
In Gemfile:
carrierwave (~> 0.11.2)
carrierwave-base64 (~> 2.3) was resolved to 2.8.1, which depends on
carrierwave (>= 0.8.0)
Bundler could not find compatible versions for gem "i18n":
In Gemfile:
rails (= 4.2.8) was resolved to 4.2.8, which depends on
activesupport (= 4.2.8) was resolved to 4.2.8, which depends on
i18n (~> 0.7)
faker was resolved to 2.11.0, which depends on
i18n (>= 1.6, < 2)
Bundler could not find compatible versions for gem "rails":
In Gemfile:
rails (= 4.2.8)
secondbase (~> 2.1.0) was resolved to 2.1.6, which depends on
rails (>= 4.0)
two_factor_authentication (~> 2.0, >= 2.0.1) was resolved to 2.2.0, which depends on
rails (>= 3.1.1)
Bundler could not find compatible versions for gem "railties":
In Gemfile:
coffee-rails was resolved to 4.2.2, which depends on
railties (>= 4.0.0)
two_factor_authentication (~> 2.0, >= 2.0.1) was resolved to 2.2.0, which depends on
devise was resolved to 4.7.1, which depends on
railties (>= 4.1.0)
font-awesome-rails was resolved to 4.7.0.5, which depends on
railties (>= 3.2, < 6.1)
jquery-datatables-rails (~> 3.4) was resolved to 3.4.0, which depends on
jquery-rails was resolved to 4.3.5, which depends on
railties (>= 4.2.0)
momentjs-rails (~> 2.15, >= 2.15.1) was resolved to 2.20.1, which depends on
railties (>= 3.1)
quiet_assets was resolved to 1.1.0, which depends on
railties (>= 3.1, < 5.0)
rails (= 4.2.8) was resolved to 4.2.8, which depends on
railties (= 4.2.8)
rspec-rails (~> 3.5, >= 3.5.2) was resolved to 3.9.1, which depends on
railties (>= 3.0)
Bundler could not find compatible versions for gem "rake":
In Gemfile:
rake (~> 12.0)
capistrano-figaro was resolved to 1.0.0.0, which depends on
capistrano (~> 3.1) was resolved to 3.13.0, which depends on
rake (>= 10.0.0)
rails (= 4.2.8) was resolved to 4.2.8, which depends on
railties (= 4.2.8) was resolved to 4.2.8, which depends on
rake (>= 0.8.7)
Bundler could not find compatible versions for gem "ruby":
In Gemfile:
ruby (~> 2.4.1.0)
sidekiq was resolved to 6.0.7, which depends on
ruby (>= 2.5.0)
And, this is my RVM env (I'm on OSX 10.12.6):
rvm env
export PATH="/Users/zulhilmi/.rvm/gems/ruby-2.4.1/bin:/Users/zulhilmi/.rvm/gems/ruby-2.4.1#global/bin:/Users/zulhilmi/.rvm/rubies/ruby-2.4.1/bin:$PATH"
export GEM_HOME='/Users/zulhilmi/.rvm/gems/ruby-2.4.1'
export GEM_PATH='/Users/zulhilmi/.rvm/gems/ruby-2.4.1:/Users/zulhilmi/.rvm/gems/ruby-2.4.1#global'
export MY_RUBY_HOME='/Users/zulhilmi/.rvm/rubies/ruby-2.4.1'
export IRBRC='/Users/zulhilmi/.rvm/rubies/ruby-2.4.1/.irbrc'
unset MAGLEV_HOME
unset RBXOPT
export RUBY_VERSION='ruby-2.4.1'
And, this is my bundle env output.
How to read these logs and what I should do to fix them? Any tips?
In Gemfile:
protected_attributes x86-mingw32 was resolved to 1.0.0, which depends on
activemodel (< 5.0, >= 4.0.0.beta) x86-mingw32
rails (~> 5.0.4) x86-mingw32 was resolved to 5.0.4, which depends on
activemodel (= 5.0.4) x86-mingw32
rails (~> 5.0.4) x86-mingw32 was resolved to 5.0.4, which depends on
activemodel (= 5.0.4) x86-mingw32
web-console (>= 3.3.0) x86-mingw32 was resolved to 3.5.1, which depends on
activemodel (>= 5.0) x86-mingw32
I already tried to do bundle, bundle install and bundle update but it doesnt work.
I made some research and turns out that the gem protected_attributes does not work with Rails 5, but the community made another that does work, this gem is protected_attributes_continued, so i just changed the gem in the Gemfile
When trying to install a rails gem that ships the twitter-bootstrap-rails into my application, I got the following issue:
C:\workinrails\mytrelloapp>bundle install
Bundler could not find compatible versions for gem "railties":
In snapshot (Gemfile.lock):
railties (= 4.2.5.1)
In Gemfile:
coffee-rails (~> 4.1.0) x86-mingw32 was resolved to 4.1.1, which depends on
railties (< 5.1.x, >= 4.0.0) x86-mingw32
jquery-rails x86-mingw32 was resolved to 4.2.2, which depends on
railties (>= 4.2.0) x86-mingw32
rails (= 4.2.5.1) x86-mingw32 was resolved to 4.2.5.1, which depends on
railties (= 4.2.5.1) x86-mingw32
sass-rails (~> 5.0) x86-mingw32 was resolved to 5.0.6, which depends on
railties (< 6, >= 4.0.0) x86-mingw32
twitter-bootstrap-rails x86-mingw32 was resolved to 4.0.0, which depends on
railties (>= 5.0.1, ~> 5.0) x86-mingw32
web-console (~> 2.0) x86-mingw32 was resolved to 2.3.0, which depends on
railties (>= 4.0) x86-mingw32
After getting this "Running bundle update will rebuild your snapshot from scratch, using only the gems in your Gemfile, which may resolve the conflict." message, I got a new issue telling me that Bundler could not find compatible versions for gem "actionpack"
To summarize, I just did these steps:
Step 1 - Pasted gem 'twitter-bootstrap-rails', :git => 'git://github.com/seyhunak/twitter-bootstrap-rails.git' to my gemfile.
Step 2 - Bundle install
And I was hoping to arrive to Step 3 - rails generate bootstrap:install static
What's the issue?
I am attempting to use dryml views for my rails project without using hobo. My version of ruby is 2.0.0 and the version of rails I am using is 4.2.3. I was following the instructions on this page: https://github.com/Hobo/hobo/blob/master/dryml/README
I attempted to follow them through but instead got this error when updating the bundler:
Bundler could not find compatible versions for gem "actionpack":
In snapshot (Gemfile.lock):
actionpack (= 4.2.3)
In Gemfile:
rails (= 4.2.3) x64-mingw32 depends on
actionmailer (= 4.2.3) x64-mingw32 depends on
actionpack (= 4.2.3) x64-mingw32
rails (= 4.2.3) x64-mingw32 depends on
actionmailer (= 4.2.3) x64-mingw32 depends on
actionpack (= 4.2.3) x64-mingw32
sass-rails (~> 5.0) x64-mingw32 depends on
sprockets-rails (< 4.0, >= 2.0) x64-mingw32 depends on
actionpack (>= 3.0) x64-mingw32
rails (= 4.2.3) x64-mingw32 depends on
actionmailer (= 4.2.3) x64-mingw32 depends on
actionpack (= 4.2.3) x64-mingw32
dryml (>= 0) x64-mingw32 depends on
actionpack (< 3.0.0, >= 2.2.2) x64-mingw32
dryml (>= 0) x64-mingw32 depends on
actionpack (< 3.0.0, >= 2.2.2) x64-mingw32
I am using Windows 8 if that makes any difference.
It looks like the latest version of dryml locks you into Rails 4.0.x (see actionpack dependency). You won't be able to use it with Rails 4.2 unless you fork the gem and loosen the gemspec dependency yourself.
However it looks like there is already an open issue on that project about some issues with Rails 4.2 so you probably don't want to do that. You could help out on that issue by making the needed fixes or helping test them after someone else does.