ip2k / google-api-ruby-client

Automatically exported from code.google.com/p/google-api-ruby-client
Apache License 2.0
0 stars 0 forks source link

faraday version conflict with signet 0.4 #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. try to gem install google-api-client

What is the expected output? What do you see instead?
i expect it to install, instead i get:
ERROR:  While executing gem ... (Gem::DependencyError)
    Unable to resolve dependencies: google-api-client requires faraday (~> 0.7.0); signet requires faraday (~> 0.8.1)

What version of the product are you using? On what operating system?
RVM Ruby 1.9.2-p290

Please provide any additional information below.
 google-api-client's gemspec declares signet >=0.3.4 and faraday ~> 0.7.0 but signet 0.4 requires faraday ~>0.8.1 so it won't install. I suspect changing the dependency to signet ~>0.3.4 will prevent the version conflict.

Original issue reported on code.google.com by centiped...@gmail.com on 27 Jul 2012 at 12:52

GoogleCodeExporter commented 9 years ago
Ah sorry, looks like someone beat me to this, I just misread the title of their 
issue. Delete if duplicate. Anyway by installing signet 0.3.4 first I was able 
to get google-api-client to install.

Original comment by centiped...@gmail.com on 27 Jul 2012 at 1:04

GoogleCodeExporter commented 9 years ago
No, this is a related issue, but not a duplicate issue. The temporary 
work-around is to use bundler to introduce your own dependency on signet ~> 
0.3.4. I was trying to update both libraries at the same time, but ended up 
having the release blocked by the other Launchy issue.

Original comment by bobaman@google.com on 27 Jul 2012 at 3:45

GoogleCodeExporter commented 9 years ago
when is an update due for this?

Original comment by talksens...@gmail.com on 30 Jul 2012 at 9:36

GoogleCodeExporter commented 9 years ago
Tomorrow.

Original comment by bobaman@google.com on 30 Jul 2012 at 1:04

GoogleCodeExporter commented 9 years ago
This should be fully resolved as of Signet 0.4.1.

Original comment by bobaman@google.com on 31 Jul 2012 at 12:53

GoogleCodeExporter commented 9 years ago
I tried uninstalling Faraday and got the following error:

You have requested to uninstall the gem:
    faraday-0.7.6
google-api-client-0.4.4 depends on [faraday (~> 0.7.0)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn]  y
Successfully uninstalled faraday-0.7.6

You have requested to uninstall the gem:
    faraday-0.8.1
oauth2-0.8.0 depends on [faraday (~> 0.8)]
oauth2-0.7.1 depends on [faraday (~> 0.8)]
panda-1.5.0 depends on [faraday (>= 0.7.0)]
signet-0.4.1 depends on [faraday (~> 0.8.1)]
signet-0.4.0 depends on [faraday (~> 0.8.1)]

-----

I then tried to re-install google-api-client:

sudo gem install google-api-client
ERROR:  While executing gem ... (Gem::DependencyError)
    Unable to resolve dependencies: google-api-client requires faraday (~> 0.7.0)

----

Am I doing something wrong?

Thanks,

Richard

Original comment by burto...@gmail.com on 31 Jul 2012 at 1:21

GoogleCodeExporter commented 9 years ago
Until the update is out, try installing signet version 0.3.4 first, either 
explicitly (gem install signet -v0.3.4) or adding it to your Gemfile or 
environment.rb

Original comment by centiped...@gmail.com on 31 Jul 2012 at 1:24

GoogleCodeExporter commented 9 years ago
Sorry, my bad. This issue is still in progress. The Signet project's equivalent 
issue is resolved, but this one has only been fixed in the repository. I will 
update again as soon as the release is pushed.

Original comment by bobaman@google.com on 31 Jul 2012 at 2:13

GoogleCodeExporter commented 9 years ago
Thanks very much. I really appreciate it.

Original comment by burto...@gmail.com on 31 Jul 2012 at 3:09

GoogleCodeExporter commented 9 years ago
Version 0.4.5 has been released.

There are two outstanding bugs in this release that have proven more than a 
little bit difficult to squash. One is an issue with repeated parameters and 
the other is a bug in the encoding of parameter values containing the "+" 
character. You'll want to keep an eye out for those.

Original comment by bobaman@google.com on 31 Jul 2012 at 9:46