-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rails 5.1 #147
Comments
I've just got same error on rails 5.1.1 Bundler could not find compatible versions for gem "cloudinary":
|
+1 |
This gem needs updated to match cloudinary's most recent version - judging by the activity around it I assume this gem is no longer in development? |
I patched the attachinary gem dependencies so it could be used with
Rails 5; you could use that. I'm not bright enough to do a pull request
that would update the gem itself. It's so very easy to use attachinary
and it would be a shame to lose it.
Tom Connolly
…On 09/01/2017 11:14 AM, Dylan Pierce wrote:
This gem needs updated to match cloudinary's most recent version -
judging by the activity around it I assume this gem is no longer in
development?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#147 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABJyJfERB-dJCkom6g7ZYdNhkNkVc2s7ks5seB9fgaJpZM4NPpv3>.
|
Thanks Tom - I assume this is your patch? https://github.com/ThomasConnolly/attachinary I use Rails 4.1 |
Yes, that's the one. Can you make it a pull request so it becomes the norm? |
For all having the same problem: The quick fix is to use @ThomasConnolly ´s version right now. Just include it in your gem file as follows:
|
Has this been officially fixed now by now? |
Updating a project from Rails 4 to 5, and still an issue for me with Rails 5.1. |
Bundler could not find compatible versions for gem "cloudinary":
In Gemfile:
cloudinary (~> 1.8)
Bundler could not find compatible versions for gem "rails":
In Gemfile:
rails (~> 5.1)
The text was updated successfully, but these errors were encountered: