Bug 2021918

Summary: rubygem-puma: FTBFS with OpenSSL 3.0.0
Product: [Fedora] Fedora Reporter: Sahana Prasad <sahana>
Component: rubygem-pumaAssignee: Vít Ondruch <vondruch>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jaruga, pvalena, ruby-packagers-sig, vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-puma-4.3.6-5.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-23 13:44:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2021922    
Bug Blocks: 1825937, 1992484    

Description Sahana Prasad 2021-11-10 12:29:25 UTC
This bug is used to track the readiness of rubygem-puma with OpenSSL 3.0.0.

Currently the build fails to build with OpenSSL 3.0.0 with the following logs
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=78020237

Kindly fix them to ensure this package builds with OpenSSL 3.0.0

You can treat the deprecated warnings not as errors if you want to continue to use deprecated functions, but it is encouraged to use the new APIs, and this migration could be done sooner than later.

To not treat deprecated warnings as errors, you may use
-Wno-error=deprecated-declarations

To port to new APIs, kindly refer to the OpenSSL upstream migration guide:
https://www.openssl.org/docs/manmaster/man7/migration_guide.html

Thank you

Comment 1 Vít Ondruch 2021-11-11 11:26:07 UTC
There was different FTBFS due to RPM update. There is still issue with Puma though:

https://github.com/ruby/openssl/pull/399#issuecomment-966103794

The fix itself is in Ruby.

Comment 2 Vít Ondruch 2021-11-23 13:44:46 UTC
I have reported the issue also against Puma:

https://github.com/puma/puma/issues/2753

But ultimately, Puma was rebuilt against OpenSSL 3.x and it keeps building with Ruby 3.0 with the OpenSSL patches, so closing this issue.