Unable to install highrise for Ruby 2.3.1 & Rails 5.0.0

[AdeelKamalMalik]

Hi @tapajos & Team,

I'm working on upgrading Rails App from 4.2.8 to 5.0.0. Highrise is throwing error when I run 'bundle install'. If I comment this gem, I'm good to install rest of the gems and run application successfully. Here is my GEMFILE:

`source 'https://rubygems.org'
ruby "2.3.1"

git_source(:github) do |repo_name|
repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?("/")
"https://github.com/#{repo_name}.git"
end

#-> Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '> 5.0.0'
gem 'mongoid-observers', '> 0.3.0'
gem 'rails-observers', github: 'rails/rails-observers'
gem "bson"#, '~> 3.0'
gem "moped"#, git: 'https://github.com/mongoid/moped.git'

#-> Gems used only for assets and not required
#-> in production environments by default.
gem 'coffee-rails'#, '> 4.1.0'
gem 'zurb-foundation'#, '> 2.2.0.2'
gem 'uglifier'#, '>= 1.0.3'

gem 'jquery-rails'#, '> 2.1.4'
#-> Use Redis adapter to run Action Cable in production
#-> gem 'redis', '> 3.0'

#-> To use ActiveModel has_secure_password
#-> gem 'bcrypt-ruby', '~> 3.1.7'

#-> gem 'thin'
gem 'newrelic_rpm'
gem "mongoid"
gem 'mongoid-slug'
gem 'stripe'
gem 'stripe_event'
gem 'country_select'
gem 'mandrill-api'
gem 'gibbon'
gem 'honeybadger'
gem 'chronic'
gem 'highrise'
gem 'will_paginate'

#-> Use Puma as the app server
gem 'puma'
#-> gem 'sass-rails', github: "rails/sass-rails"
gem 'responders'

group :development do
gem 'rb-fsevent'#, '> 0.9.1'
gem 'guard'
gem 'guard-rspec'
#-> gem 'guard-cucumber'
gem 'guard-spork'
gem 'forward' # use this to test https
gem 'foreman'
gem 'byebug', platforms: :mri
#-> Adds support for Capybara system testing and selenium driver
gem 'capybara', '> 2.13.0'
gem 'selenium-webdriver'
#-> gem 'capistrano-rails'
#-> Spring speeds up development by keeping your application running in the background.
#-> Read more: https://github.com/rails/spring
gem 'spring'
gem 'spring-watcher-listen', '~> 2.0.0'

#-> Access an IRB console on exception pages or by using <%= console %> anywhere in the code.
gem 'web-console', '>= 3.3.0'
gem 'listen', '>= 3.0.5', '< 3.2'
end

group :development, :test do
gem 'fabrication'
gem "factory_girl_rails"#, ">= 4.1.0"
gem 'rspec-rails'#, ">= 2.14.0"
gem 'mongoid-rspec'
gem 'spork'
gem 'fuubar'
end

#->Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]

#->gem 'canvas', path: '../canvas'
gem 'canvas', :git => "https://github.com/jfranz/canvas.git"`

When I run bundle install, I get this:

`Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Resolving dependencies..................................................................................................................................................................................................................................................................................................................................................................................................................................
Bundler could not find compatible versions for gem "activesupport":
In snapshot (Gemfile.lock):
activesupport (= 5.0.2)

In Gemfile:
highrise was resolved to 1.0.2, which depends on
activeresource (>= 2.1) was resolved to 2.1.0, which depends on
activesupport (= 2.1.0)

factory_girl_rails was resolved to 4.8.0, which depends on
  factory_girl (~> 4.8.0) was resolved to 4.8.0, which depends on
    activesupport (>= 3.0.0)

rails (~> 5.0.0) was resolved to 5.0.2, which depends on
  activejob (= 5.0.2) was resolved to 5.0.2, which depends on
    globalid (>= 0.3.6) was resolved to 0.3.7, which depends on
      activesupport (>= 4.1.0)

highrise was resolved to 1.0.2, which depends on
  activesupport (>= 2.1)

mongoid-slug was resolved to 5.3.0, which depends on
  mongoid-compatibility was resolved to 0.4.1, which depends on
    activesupport

rspec-rails was resolved to 3.5.2, which depends on
  actionpack (>= 3.0) was resolved to 5.0.2, which depends on
    rails-dom-testing (~> 2.0) was resolved to 2.0.2, which depends on
      activesupport (< 6.0, >= 4.2.0)

jquery-rails was resolved to 4.3.1, which depends on
  railties (>= 4.2.0) was resolved to 5.0.2, which depends on
    activesupport (= 5.0.2)

jquery-rails was resolved to 4.3.1, which depends on
  railties (>= 4.2.0) was resolved to 5.0.2, which depends on
    activesupport (= 5.0.2)

jquery-rails was resolved to 4.3.1, which depends on
  railties (>= 4.2.0) was resolved to 5.0.2, which depends on
    activesupport (= 5.0.2)

jquery-rails was resolved to 4.3.1, which depends on
  railties (>= 4.2.0) was resolved to 5.0.2, which depends on
    activesupport (= 5.0.2)

jquery-rails was resolved to 4.3.1, which depends on
  railties (>= 4.2.0) was resolved to 5.0.2, which depends on
    activesupport (= 5.0.2)

jquery-rails was resolved to 4.3.1, which depends on
  railties (>= 4.2.0) was resolved to 5.0.2, which depends on
    activesupport (= 5.0.2)

rspec-rails was resolved to 3.5.2, which depends on
  activesupport (>= 3.0)

spring was resolved to 2.0.1, which depends on
  activesupport (>= 4.2)

rails (~> 5.0.0) was resolved to 5.0.2, which depends on
  sprockets-rails (>= 2.0.0) was resolved to 3.2.0, which depends on
    activesupport (>= 4.0)

stripe_event was resolved to 1.6.0, which depends on
  activesupport (>= 3.1)

Running bundle update will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

I tried running bundle update as well but in vain. Please help me out as this is somewhat urgent task.

Waiting for your response.

Thanks,
Adeel

[tapajos]

I will take a look on it later tomorrow.

[tapajos]

@AdeelKamalMalik I need more time to investigate it. Sorry, today is being a busy day. will check tomorrow night.

[AdeelKamalMalik]

@tapajos Thanks for the update! Sure, take your time and let me know if you need further information from my side. Thanks!

[AdeelKamalMalik]

@tapajos It would be great if you can check it this week. I'm stuck in upgrading an app that's critical. Thanks!

[tapajos]

@AdeelKamalMalik,

The problem here is that active resource 5 is not officially released. I created an experimental branch for you.

Take a look in deb1a84

Can you test it?

Please, be aware that it wasn't tested against that version.

[AdeelKamalMalik]

@tapajos Thank you for prompt response. I'll test it and will let you know.

One question though, as active resource official version is 4.1.0, if I keep the same, which highrise version would work fine with 4.1.0?

Thanks for your help!