Google API dependency clash with DataMapper

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to run example (google calendar example in my case)
2. bundle install gems
3. run $ ruby my_google_calendar_test.rb

What is the expected output? What do you see instead?
Authorization and calendar data

What version of the product are you using? On what operating system?
The most current ruby gem for 'google/api_client'. I am on OSX, using RVM, ruby 
1.9.3

Please provide any additional information below.

result of running bundle update

Using addressable (2.3.2) 
Using extlib (0.9.15) 
Using multi_json (1.3.6) 
Using autoparse (0.3.2) 
Using daemons (1.1.9) 
Using data_objects (0.10.10) 
Using dm-core (1.0.2) 
Using dm-do-adapter (1.0.2) 
Using dm-migrations (1.0.2) 
Using do_postgres (0.10.10) 
Using dm-postgres-adapter (1.0.2) 
Using dm-validations (1.0.2) 
Using dm-rspec (0.2.3) 
Using fastercsv (1.5.5) 
Using json_pure (1.7.5) 
Using dm-serializer (1.0.2) 
Using do_sqlite3 (0.10.10) 
Using dm-sqlite-adapter (1.0.2) 
Using eventmachine (1.0.0) 
Using multipart-post (1.1.5) 
Using faraday (0.8.4) 
Using launchy (2.1.2) 
Using jwt (0.1.5) 
Using signet (0.4.3) 
Using uuidtools (2.1.3) 
Using google-api-client (0.4.7) 
Using haml (3.1.7) 
Using rack (1.4.1) 
Using rack-protection (1.2.0) 
Using shotgun (0.9) 
Using tilt (1.3.3) 
Using sinatra (1.3.3) 
Using thin (1.5.0) 
Using bundler (1.2.1) 

and the error I get:

/Users/me/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/specific
ation.rb:1637:in `raise_if_conflicts': Unable to activate autoparse-0.3.2, 
because addressable-2.2.8 conflicts with addressable (>= 2.3.1) (Gem::LoadError)

Original issue reported on code.google.com by jonros...@gmail.com on 15 Oct 2012 at 6:43

[GoogleCodeExporter]

This is an issue with an overly restrictive dependency requirement in dm-core. 
They've set "~> 2.2.6", but it should be "~> 2.2" or "~> 2.3". Unfortunately 
there's nothing that can be done from our side. The API client needs the 
functionality present only in >= 2.3.2.

Original comment by bobaman@google.com on 16 Oct 2012 at 9:17

• Changed state: Invalid

[GoogleCodeExporter]

This was just fixed in the most recent release of DataMapper 1.2.0. Using this 
version fixed the issue. Thanks for the reply

Original comment by jonros...@gmail.com on 18 Oct 2012 at 2:48