If I use gem 'rally_api' it will use version 0.9.8, which will failed to login rally with api_key
If I use gem 'rally_api', '~> 1.2', '>= 1.2.1' to install latest version 1.2.1(I mannully install in my local machine), the rake task can work, but I'll get compatible version error:
Bundler could not find compatible versions for gem "httpclient":
In Gemfile:
berkshelf (~> 4.3.5) was resolved to 4.3.5, which depends on
httpclient (~> 2.7)
rally_api (>= 1.2.1, ~> 1.2) was resolved to 1.2.1, which depends on
httpclient (= 2.6.0.1)
Related
I'm getting this error after bundle install. How can I fix it?
Bundler could not find compatible versions for gem "excon":
In Gemfile:
locomotive-heroku (~> 0.0.2) ruby depends on
excon (~> 0.9.4) ruby
excon (0.20.0)
Uninstall the latest version of the gem: gem uninstall excon -v=0.20.0. Then bundle install again to see if it resolved the problem.
i fixed it by putting the locations for the current repos for locomotive/engine and locomotive/heroku. I.e gem 'locomotive-heroku', git: 'repolocation', require: 'locomotive/heroku' This is also what eventually got me a working installation of locomotivecms on heroku. I did need to set it to compile assets in the production environment.
I have rails 3.017, and clearance 1.0.0.rc2 and trying to install gem 'jquery-rails', '~> 2.1'
Do I need an older version of jquery-rails? If so, how can I figure this out?
thanks
Joel
Bundler could not find compatible versions for gem "railties":
In Gemfile:
jquery-rails (~> 2.1) ruby depends on
railties (< 5.0, >= 3.1.0) ruby
clearance (= 1.0.0.rc2) ruby depends on
railties (3.0.17)
Yes, you need an older version of this gem. If you don't specify a certain version of jquery-rails in your Gemfile, Bundler will find the matching version for you, if you run bundle install.
You can find out the dependencies of a gem with the gem manager:
$ gem dependency jquery-rails -v 2.1.3
How to solve this dependency problem.
I`m using sorcery to administration and I dont need oauth2(0.4.1).
Bundler could not find compatible versions for gem "oauth2":
In Gemfile:
omniauth-facebook (>= 0) ruby depends on
oauth2 (~> 0.5.0) ruby
sorcery (>= 0) ruby depends on
oauth2 (0.4.1)
This is my Gemfile
gem 'sorcery'
gem 'omniauth-facebook'
gem 'omniauth-google-oauth2'
You should fork the sorcery gem and change this line to be this:
gem.add_runtime_dependency 'oauth2', '~> 0.5.0'
Then make a commit, push it to GitHub and then reference it in your application like this:
gem 'sorcery', :git => "git://github.com/regedarek/sorcery.git"
For bonus points, submit that patch as a pull request to the original sorcery repository.
When I run bundle install after adding the omnisocial gem to my gem file, I get this when I have in fact already installed the latest version of the oa-core gem:
Bundler could not find compatible versions for gem "oa-core":
In Gemfile:
omnisocial depends on
oa-core (~> 0.1.2)
omniauth depends on
oa-core (0.2.6)
...
gem install oa-core
Successfully installed oa-core-0.2.6
1 gem installed
Installing ri documentation for oa-core-0.2.6...
Installing RDoc documentation for oa-core-0.2.6...
Do I need to update my version of rails?
The problem is that the omnisocial gem's dependencies have not been updated to match the latest oa-core release. Bundler will attempt to resolve all the dependencies for all the gems.
In this situation, omnisocial says it is quite happy with any of the 0.1.x releases (as long as it's the 0.1.2 release or one after that) of oa-core (this is what the ~> operator means) but omniauth says it must have 0.2.6. Obviously, 0.2.6 is not a part of the 0.1.x set of releases and so you are getting this error.
omnisocial's gem dependencies must be upgraded to match the latest oa-core version. That is the problem.
Alternatively, you could use omniauth which is designed to work with this latest version of the oauth suite, rather than using omnisocial.
When adding devise_invitable to my Gemfile, I get this error when doing bundle install.
$ bundle install
Fetching source index for http://rubygems.org/
Bundler could not find compatible versions for gem "rails":
In Gemfile:
devise_invitable (~> 0.4.0) depends on
rails (~> 3.0.0)
rails (3.1.0)
In your Gemfile, update devise_invitable to use a newer version (current is 0.5.4) instead of 0.4.0; 0.5.4 supports Rails 3.1.