We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I just updated chefdk to: chefdk-2.3.4-1.el7.x86_64.rpm
Recipe: s3_file::dependencies * chef_gem[rest-client] action install (up to date) [...] Unable to activate rest-client-1.7.3, because mime-types-3.1 conflicts with mime-types (< 3.0, >= 1.16)
Works fine when a revert back to: chefdk-0.13.21-1.el7.x86_64.rpm
s3_file is at version 2.8.5
I'm running into this conflict and can't figure out how to resolve it. Anything obvious that I can try? Is this compatible with that version of chef?
I have done clean installs and/or deleted .chef, .chefdk folders between attempts
The text was updated successfully, but these errors were encountered:
Looks like the conflict is with rest-client 1.7.3 having mime-types bound: https://github.com/rest-client/rest-client/blob/988d5a81ff3081c1c6a3ab267e81a9fff94bd9e4/rest-client.gemspec#L25 while chef has moved on:https://github.com/chef/chef-dk/blob/master/Gemfile.lock
rest-client allows the new mime-types in 2.0+ rest-client/rest-client@d401bba
Sorry, something went wrong.
Seems like the fix would be to support rest-client >= 2.0 via https://github.com/adamsb6/s3_file/blob/b413c39538f5efb5411005a9754a6af39c1cc9bb/attributes/default.rb and fix #107
No branches or pull requests
I just updated chefdk to: chefdk-2.3.4-1.el7.x86_64.rpm
Works fine when a revert back to: chefdk-0.13.21-1.el7.x86_64.rpm
s3_file is at version 2.8.5
I'm running into this conflict and can't figure out how to resolve it. Anything obvious that I can try?
Is this compatible with that version of chef?
I have done clean installs and/or deleted .chef, .chefdk folders between attempts
The text was updated successfully, but these errors were encountered: