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.

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

chef 12/13: gem_package: support the --no-document flag needed for Ruby 2.6 / rubygems 3 #8416

Closed
poloka opened this issue Apr 25, 2019 · 3 comments

Comments

@poloka
Copy link

poloka commented Apr 25, 2019

Describe the Enhancement:

Trying to upgrade my services to utilize ruby 2.6, but because gem_package constructs the gem install command with --no-rdoc --no-ri, my installation utilizing chef 12.19.36 fails indicating

STDERR: ERROR:  While executing gem ... (OptionParser::InvalidOption)
  invalid option: --no-rdoc

Would like the fix #7994 added to chef-14 to be patched to 12 and 13.

Describe the Need:

This would continue to allow older enterprise solutions to support updates in services to eliminate security vulnerabilities.

Current Alternative

There is no alternative other than forcing an upgrade to 14.8.12 or higher.

Can We Help You Implement This?:

What branch for 12 and 13 is their latest releases that I could submit a PR against? What is the timeframe for releasing the change once merged to branch?

@poloka poloka added the Status: Untriaged An issue that has yet to be triaged. label Apr 25, 2019
@bastien-jove-cbp
Copy link
Contributor

Chef 12 is no longer supported and 13 will be end of life with the release of 15(which should be soon) so it's unlikely any of them will be patched.

What you can do as an alternative is taking #7994 state of file lib/chef/provider/package/rubygems.rb and save it in a cookbook's libraries directory to "monkey patch" the provider if you can't update Chef client right now.

@lamont-granquist
Copy link
Contributor

yeah, there are no future chef-13 releases planned.

@lock
Copy link

lock bot commented May 16, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 16, 2019
@lamont-granquist lamont-granquist removed the Status: Untriaged An issue that has yet to be triaged. label Jun 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants