how to resolve this type of errors
In Gemfile:
appdirect (>= 0) ruby depends on
nori (~> 2.4) ruby
google-adwords-api (>= 0) ruby depends on
google-ads-common (~> 0.9.8) ruby depends on
savon (~> 1.2.0) ruby depends on
nori (1.1.5)
Please tell. I tried updating google-adword-api gem but its not working.
Unfortunately, google-ads-common gem is sticked to old version of savon, here's what gem author says:
Savon 2 does not support the complex AdWords API wsdls. I would love to upgrade and put this to rest, but it isn't feasible at the moment. We are looking into alternatives.
In this sad situation you need to choose between conflicting gems, you can't have both at once.
I have edited appdirect to use compitable version of nori.
Here is the link to the gem
https://github.com/aditya01933/appdirect
Related
In our rails application, we are using two gems (urbanairship and nylas) that's requiring rest-client. One wants ~> 1.6.7 and the other wants ~> 1.7.1.
The usual bundle udpate and rm Gemfile.lock; bundle install doesn't work.
When Bundler is resolving dependencies, we are getting this:
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies............................................................................................................................................
Bundler could not find compatible versions for gem "rest-client":
In Gemfile:
urbanairship (~> 3.0.1) ruby depends on
unirest (>= 1.1.2, ~> 1.1) ruby depends on
rest-client (~> 1.6.7) ruby
nylas (>= 0) ruby depends on
rest-client (~> 1.7) ruby
We can't use unfortunately a different version of either nylas or urbanairship. The only solution we are seing is forking one of the two and editing the .gemspec to accept the same version of rest-client.
Is there any easier solution?
Finally, ended up following Chris advice.
Forked nylas
https://github.com/hartator/nylas-ruby/
Relaxed Gemfile requirements for rest-client. (was 1.7)
gem 'rest-client', '~> 1.6'
Relaxed nylas.gemspec requirements for rest-client. (was 1.7)
s.add_dependency(%q<rest-client>, ["~> 1.6"])
Relaxed nylas.gemspec runtime requirements for rest-client. (was 1.7)
s.add_runtime_dependency(%q<rest-client>, ["~> 1.6"])
Ran specs, everything was still passing.
Added the altered gem to my application Gemfile
gem 'nylas', git: 'git#github.com:hartator/nylas-ruby.git'
Everything is working. Still wondering if there is a cleaner solution out there.
Ref: https://github.com/hartator/nylas-ruby/commit/f7ff4076e96d8a31e223ca0f12d35811d6e9d811
I have some dependency conflict since I try to add mandrill-api.
I've added the gem in my gemfile, but when I want to bundle install I've got this error :
Bundler could not find compatible versions for gem "excon":
In Gemfile:
mandrill-api (>= 0) ruby depends on
excon (~> 0.15.4) ruby
heroku-api (>= 0) ruby depends on
excon (0.13.4)
I've tried so many things to fix this, but impossible.
Even if I delete the heroku gems, I still get an error with fog.
Anyone has an idea? thanks !
Looking back it appears you must be using an older version of the mandrill-api gem (more recent ones have a much looser excon requirement). I think if you update to the latest mandrill-gem it should be less problematic and better cooperate with excon/heroku-api/fog. Do let me know if that isn't the case though and I can certainly dig deeper.
First, I apologize ahead of time for any confusion / lack of clarity, this is my first stackoverflow post.
I built a custom engine for my refinery app with the typical:
rails generate refinery:engine web_users first_name:string last_name:string...
Running this puts a gem in the gemfile like so:
gem 'refinerycms-web_users', :path => 'vendor/extensions'
However, I also have 'refinerycms-acts-as-indexed', '~> 1.0.0' in my gemfile for foundation as my front-end framework (specifically for mobile menu navigation).
When running bundle update I get the following error:
refinerycms (~> 2.1.2) ruby depends on
refinerycms-core (= 2.1.2) ruby
refinerycms-web_users (>= 0) ruby depends on
refinerycms-core (2.0.10)
Is there either a solution for downgrading acts-as-index to play nice with refinerycms-core (2.0.10) or to bump up the dependency of a custom engine to refinerycms 2.1.2?
Thanks errrrybody!
Sorry, realize I didn't put the error with acts-as-indexed with refinerycms core 2.1.0:
refinerycms-acts-as-indexed (~> 1.0.0) ruby depends on
refinerycms-core (~> 2.1.0) ruby
You'll need to upgrade your extension to depend on refinerycms-core ~> 2.1.0 which you can do by opening (something like) vendor/extensions/refinerycms-web_users/refinerycms-web_users.gemspec and specifying the updated dependency version in place of what is already specified. You'll then want to ensure that it works properly with the updated version of refinerycms-core.
I was going through my Gemfile updating to the latest releases when I got this error:
Bundler could not find compatible versions for gem "mime-types":
In Gemfile:
rails (= 4.0.2) ruby depends on
mime-types (~> 1.16) ruby
mechanize (= 2.7.3) ruby depends on
mime-types (2.0)
Is it true that Rails 4.0.2 is depending on a much older version of mime-types than a lot of gems that are out there or is there something wrong with my local configuration?
P.S. I tried updating the dependencies with ´bundle update´, but I just got the same error again.
rails requires mime-types with a version of 1.16 or greater, but smaller than 2.0. However, mechanize requires mime-types with a version of 2.0 or greater.
I suggest you drop the mechanize-version to 2.7.2:
gem 'mechanize', '2.7.2'
This will resolve your conflict.
I am using two gems ie squeel and activeadmin and running bundler gives me issue ie:
Bundler could not find compatible versions for gem "polyamorous":
In Gemfile:
activeadmin (>= 0) ruby depends on
polyamorous (~> 0.5.0) ruby
squeel (>= 0) ruby depends on
polyamorous (0.6.4)
Bundler could not find compatible versions for gem "activerecord":
In Gemfile:
activeadmin (>= 0) ruby depends on
activerecord (~> 3.0.0.rc2) ruby
delayed_job_active_record (>= 0) ruby depends on
activerecord (3.2.13)
How can I handle this? Any idea?
That's being caused by Metasearch:
Metasearch is no longer being maintained, so we're working on moving to Ransack, its successor. We aren't quite finished, so there hasn't yet been an official release. If you want to go ahead and give it a try:
gem 'activeadmin', github: 'gregbell/active_admin'