Originally created by @michaelachrisco on GitHub (Apr 3, 2015).
I have a legacy app that I thought might work with this gem, but I get this bundle error:
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
crono (>= 0) ruby depends on
activejob (~> 4.0) ruby depends on
activesupport (= 4.2.0) ruby
jbuilder (~> 2.0) ruby depends on
activesupport (4.1.0)
Originally created by @michaelachrisco on GitHub (Apr 3, 2015).
I have a legacy app that I thought might work with this gem, but I get this bundle error:
```
Bundler could not find compatible versions for gem "activesupport":
In Gemfile:
crono (>= 0) ruby depends on
activejob (~> 4.0) ruby depends on
activesupport (= 4.2.0) ruby
jbuilder (~> 2.0) ruby depends on
activesupport (4.1.0)
```
Pull request into its own branch on the main repo or I can let it live on my forked repo? Your choice. Either way, for anyone having the same issue I was having:
@michaelachrisco commented on GitHub (Apr 3, 2015):
Ok I wa able to get an crono working with an old version of activesupport here: https://github.com/michaelachrisco/crono/tree/old_activesupport
Pull request into its own branch on the main repo or I can let it live on my forked repo? Your choice. Either way, for anyone having the same issue I was having:
``` Ruby
gem 'crono' ,
:git => 'https://github.com/michaelachrisco/crono.git',
:branch => 'old_activesupport'
```
Thanks for the gem BTW :+1:
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @michaelachrisco on GitHub (Apr 3, 2015).
I have a legacy app that I thought might work with this gem, but I get this bundle error:
@michaelachrisco commented on GitHub (Apr 3, 2015):
Ok I wa able to get an crono working with an old version of activesupport here: https://github.com/michaelachrisco/crono/tree/old_activesupport
Pull request into its own branch on the main repo or I can let it live on my forked repo? Your choice. Either way, for anyone having the same issue I was having:
Thanks for the gem BTW 👍
@michaelachrisco commented on GitHub (Apr 5, 2015):
Closing issue as this is related to legacy gems.