search

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

Not working with Rails 2.3.5 - Rack Gem too old #35

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Using Rails 2.3.5 and just try to start the server.

What is the expected output? What do you see instead?
Starting the ruby server fails with the exception: 
Uncaught exception: can't activate rack (~> 1.1, runtime) for ["faraday-0.7.6", 
"signet-0.3.2", "google-api-client-0.4.0"], already activated rack-1.0.1 for 
["actionpack-2.3.5", "rails-2.3.5"]

What version of the product are you using? On what operating system?
Ruby 1.8.7, Rails 2.3.5, google_api_client 0.4.0, Windows 7 and Mac OS

Please provide any additional information below.
Rails 2.3.5 is using the Rack gem 1.0.1 and not works with newer versions of it.
google_api_client 0.4.0 seems to require a newer version of Rack. If multiple 
Rack versions are installed (e.g. 1.0.1 and 1.3.5) and trying to be loaded 
during the server start up, the error occurs.

Original issue reported on code.google.com by t...@meisterlabs.com on 16 Feb 2012 at 10:57

GoogleCodeExporter commented 9 years ago 
You're running a version of Rails that's over two years old. Let's be clear, 
that's the real issue here.

Beyond that, the actual Rack dependency is inside Faraday (i.e., not something 
resolvable within this project), and it only requires Rack 1.1. Rack 1.1 is 
itself two years old, so that's actually a pretty gigantic window of 
dependencies that work just fine. I would strongly recommend updating to Rails 
2.3.14.

If that doesn't work for you, I really don't know what to tell ya.

Original comment by bobaman@google.com on 16 Feb 2012 at 11:21

GoogleCodeExporter commented 9 years ago 
Thank you for your quick answer!

Actually I think I will upgrade to Rails 2.3.14 because it seems to be the 
simplest solution too.

Original comment by t...@meisterlabs.com on 16 Feb 2012 at 6:25

GoogleCodeExporter commented 9 years ago 
Great, send a quick update and let us know how it goes, since I imagine you may 
not be the only one who hits this issue.

Original comment by bobaman@google.com on 17 Feb 2012 at 11:41

GoogleCodeExporter commented 9 years ago 
After updating to Rails 2.3.14 the issue is gone! Thanks! 

Mabye you should write in the documentation of this gem, that at least Rails 
2.3.14 is required.

Original comment by t...@meisterlabs.com on 18 Feb 2012 at 9:51

GoogleCodeExporter commented 9 years ago 
I've updated the Troubleshooting wiki page to indicate this.

Original comment by bobaman@google.com on 19 Feb 2012 at 9:03

GoogleCodeExporter commented 9 years ago

Original comment by bobaman@google.com on 19 Feb 2012 at 9:03