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.

Sign up for GitHub

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

Jump to bottom

Slop conflicts #4

Open
bbbco opened this issue Dec 10, 2015 · 3 comments
Open

Slop conflicts #4

bbbco opened this issue Dec 10, 2015 · 3 comments

Comments

@bbbco
Copy link

bbbco commented Dec 10, 2015

I'm getting this error when trying to require magic_cloud.

/home/bbbco/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/specification.rb:2112:in `raise_if_conflicts': Unable to activate magic_cloud-0.0.3, because slop-3.6.0 conflicts with slop (~> 3.0.0) (Gem::ConflictError)
@zverok
Copy link
Owner

zverok commented Dec 10, 2015

Do you use slop in your project? Or is it just magic cloud conflicting with itself somehow?..

@bbbco
Copy link
Author

bbbco commented Dec 17, 2015

I am not intentionally using slop, I believe it is a Gem conflict. I had to change the gemfile dependency to use the later version.

@anvox
Copy link
Contributor

anvox commented Feb 8, 2017

pry or pry-rails uses different slop version. I'm working on a fork which less dependency.
IMO, slop should be optional

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bbbco @zverok @anvox