-
Notifications
You must be signed in to change notification settings - Fork 86
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
Unable to install codesake-dawn gem #61
Comments
@lohithmv019 this is very specific issue you're experiencing due to your current gemset configuration I can't solve. You can try to use a fresh gemset to install dawn. |
@thesp0nge I am using fresh install of ruby(ruby 2.1) just to install this gem.All the gems I mentioned above are used by your gem only(I am not using them for any purpose.).Let me know if I am missing anything here. |
I am experiencing this same issue while trying to evaluate dawn. I am using Kali Linux, with very few gems installed. Additionally, the claim is backed by the Gemnasium dependencies linked to in the readme. codesake-dawn (https://gemnasium.com/codesake/codesake-dawn)
The problem appears to be that codesake-dawn depends on the grit library, which is unmaintained and has old dependencies. https://github.com/mojombo/grit says "Grit is no longer maintained. Check out libgit2/rugged" |
It's the The long term solution is probably to switch to |
I am not able to install codesake-dawn gem because of the dependency on multiple versions of "mime-types" gem.
grit requires mime-types (
> 1.15)(mime type 2 will not work)> 2.0)rest-client requires mime-types (>= 1.16)
mechanize requires mime-types (
I tried installing both version of the "mime-types" gem (1.25 and 2.2) then gem installed successfully but i am unable to run dawn,when try to run dawn I am getting following error
" `raise_if_conflicts': Unable to activate grit-2.5.0, because mime-types-2.2 conflicts with mime-types (~> 1.15) (Gem::LoadError)"
I am running ubuntu 13.10 and RVM with ruby 1.9.3 and ruby 2.1
Please let me know if there is any work around for this ?
The text was updated successfully, but these errors were encountered: