-
Notifications
You must be signed in to change notification settings - Fork 52
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
Sahara isn't compatible anymore with Vagrant 1.1.x #18
Comments
This is a problem for me too. Since vagrant is no longer a rubygem, I'm not even sure a gem will interop OK with it. Has anyone found an alternative or is working on one? UPDATE: the ryuzee / sahara fork appears to have updated for vagrant 1.1. |
+1 for this update |
+1 👍 |
1 similar comment
+1 👍 |
Ok, good to know. But the update was not pushed to https://rubygems.org/gems/sahara . |
released a new version today, hope this helps.
|
I got the latest gem and it works now. Thank you for the version update. The issue can be closed IMHO. |
Because Sahara depends on the Vagrant Rubygem (1.0.7) it doesn't seem to be compatible anymore with newer releases of Vagrant since it's not released as a Rubygem anymore.
The text was updated successfully, but these errors were encountered: