-
Notifications
You must be signed in to change notification settings - Fork 334
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
Is fog ~> 1.25.0 really necessary? #281
Comments
yes, couldn't you change the dependency specification from (~> 1.25.0) to (>= 1.25.0) that way I could reference 1.27.0 in my project and the knife-ec2 gem could still work for me |
This breaks it with the current chefdk which has fog 1.3.0 . |
+1 on removing this specific version pinning |
Hi, I know this already noticed by the maintainers, but this still happens on Windows: chef gem install knife-ec2 I had to uninstall the 1.3x.0 version and manually install the 1.23 version. edit: updating chefdk 0.7.0 resolved the issue. |
The latest knife-ec2 (0.11) fixes the chefdk incompatibility |
Closing this out since the latest release quiets the errors and master now using fog-aws, which avoids hard pins on the fog gem itself. |
The Fog version dependency of
~> 1.25.0
guarantees that any other Ruby gem with a dependency on Fog 1.26 or newer will be incompatible with this one (at least if both are being managed by Bundler). I don't think this is what you want.The text was updated successfully, but these errors were encountered: