Bug 2005979 - perl-Crypt-OpenSSL-RSA: FTBFS with OpenSSL 3.0.0 in Fedora Rawhide
Summary: perl-Crypt-OpenSSL-RSA: FTBFS with OpenSSL 3.0.0 in Fedora Rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Crypt-OpenSSL-RSA
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
: 2021945 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-20 15:27 UTC by Jitka Plesnikova
Modified: 2021-11-26 12:11 UTC (History)
5 users (show)

Fixed In Version: perl-Crypt-OpenSSL-RSA-0.32-3.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-26 12:11:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github toddr Crypt-OpenSSL-RSA issues 31 0 None open Crypt-OpenSSL-RSA will not compile with OpenSSL 3.0.0 due to deprecated code 2021-09-20 15:27:47 UTC

Description Jitka Plesnikova 2021-09-20 15:27:48 UTC
Description of problem:
Package perl-Crypt-OpenSSL-RSA fails to build from source with OpenSSL 3.0.0 in Fedora Rawhide.

RSA.xs: In function 'XS_Crypt__OpenSSL__RSA_use_sslv23_padding':
RSA.xs:647:22: error: 'RSA_SSLV23_PADDING' undeclared (first use in this function); did you mean 'RSA_NO_PADDING'?
  647 |     p_rsa->padding = RSA_SSLV23_PADDING;
      |                      ^~~~~~~~~~~~~~~~~~
      |                      RSA_NO_PADDING

Version-Release number of selected component (if applicable):
0.32-1.fc36

Steps to Reproduce:
koji build --scratch f36 perl-Crypt-OpenSSL-RSA-0.32-1.fc36.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/perl-Crypt-OpenSSL-RSA

Dependency changes from the last successful build:
https://koschei.fedoraproject.org/build/11184234

Comment 1 Petr Pisar 2021-11-11 11:37:44 UTC
*** Bug 2021945 has been marked as a duplicate of this bug. ***

Comment 2 Petr Pisar 2021-11-26 12:00:30 UTC
I will apply a fix proposed to the upstream.


Note You need to log in before you can comment on or make changes to this bug.