Skip to content
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

Open
ThomasConnolly opened this issue May 3, 2017 · 9 comments
Open

Rails 5.1 #147

ThomasConnolly opened this issue May 3, 2017 · 9 comments

Comments

@ThomasConnolly
Copy link

Bundler could not find compatible versions for gem "cloudinary":
In Gemfile:
cloudinary (~> 1.8)

attachinary was resolved to 1.3.0, which depends on
  cloudinary (~> 1.0.69)

Bundler could not find compatible versions for gem "rails":
In Gemfile:
rails (~> 5.1)

attachinary was resolved to 0.0.1, which depends on
  rails (~> 3.2)
@webdev1014
Copy link

webdev1014 commented May 24, 2017

I've just got same error on rails 5.1.1

Bundler could not find compatible versions for gem "cloudinary":
In Gemfile:
cloudinary (~> 1.7.0)

attachinary (>= 1.3.1, ~> 1.3) was resolved to 1.3.1, which depends on
  cloudinary (~> 1.1.0)

@ghost
Copy link

ghost commented Jun 2, 2017

+1

@ctrlaltdylan
Copy link

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?

@ThomasConnolly
Copy link
Author

ThomasConnolly commented Sep 1, 2017 via email

@ctrlaltdylan
Copy link

Thanks Tom - I assume this is your patch?

https://github.com/ThomasConnolly/attachinary

I use Rails 4.1

@ThomasConnolly
Copy link
Author

Yes, that's the one. Can you make it a pull request so it becomes the norm?

@mklb
Copy link

mklb commented Nov 27, 2017

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:

gem 'attachinary', :git => 'git://github.com/ThomasConnolly/attachinary.git'

@tbsvttr
Copy link

tbsvttr commented Mar 14, 2018

Has this been officially fixed now by now?

@firecall
Copy link

Updating a project from Rails 4 to 5, and still an issue for me with Rails 5.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants