Bug 1744782 - (RFE) EPEL8 branch of perl-Crypt-SSLeay
Summary: (RFE) EPEL8 branch of perl-Crypt-SSLeay
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Crypt-SSLeay
Version: rawhide
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-22 21:25 UTC by Pat Riehecky
Modified: 2021-12-25 00:40 UTC (History)
4 users (show)

Fixed In Version: perl-Crypt-SSLeay-0.72-32.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-25 00:40:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pat Riehecky 2019-08-22 21:25:50 UTC
Description of problem:

It would be helpful if this module was packaged for EPEL8.  I don't show it in RHEL8 itself.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

There are two AppStream modules for perl in RHEL8 right now.  I'm not sure what the EPEL plan is for multi-perl....

Comment 1 Jitka Plesnikova 2019-08-28 07:59:45 UTC
Do you really need perl-Crypt-SSLeay? Or is it possible to use perl-Net-SSLeay for your purpose? 

perl-Crypt-SSLeay as an old binding to OpenSSL was obsoleted by perl-Net-SSLeay. perl-Net-SSLeay is in RHEL 8.

Btw, I am not able to build to the package for EPEL 8, because there are missing dependencies perl-ExtUtils-PkgConfig and perl-Path-Class, which I don't own.

Comment 2 Pat Riehecky 2019-08-28 13:29:23 UTC
Hello,

I'm trying to get OCS Inventory built up for RHEL8.  It has a hard dependency on perl-Crypt-SSLeay.  Do you know what is required to switch between the two?

Comment 3 Jitka Plesnikova 2019-08-28 15:49:00 UTC
Hi,

what do you use as a source for OCS Inventory? 

I looked at https://github.com/OCSInventory-NG/UnixAgent and there is written following:

To get SSL communications working (for packages deployment or HTTPS communications to OCS server), you need these modules:
  - Crypt::SSLeay if you use LWP prior to version 6
  - LWP::Protocol::https if you use LWP version 6 or more

RHEL 8 provides perl(LWP) = 6.34, so you should requires per(LWP::Protocol::https) which is part of RHEL 8.

I checked the code and Crypt::SSLeay is used only with LWP < 5.83. No changes in this code are needed.

Comment 4 Pat Riehecky 2019-08-28 17:17:31 UTC
In that case I'll migrate up to that version.

Comment 5 Paul Howarth 2019-10-24 14:20:08 UTC
Perhaps this ticket can be closed now?

Comment 6 Jitka Plesnikova 2019-10-25 07:32:54 UTC
Nobody else requires the package, so I close the BZ.

Comment 7 Saad 2021-12-12 12:06:04 UTC
Hi Jitka,
We need perl-Crypt-SSLeay module for our product. If it can be moved to EPEL 8, that would be great. We do not yet use LWP::Protocol::https and it might take time to migrate to use this module instead of Net::SSL.
I have tried building Crypt::SSLeay on RHEL 8.4. The build goes fine. The version is used is this one. https://cpan.metacpan.org/authors/id/N/NA/NANIS/Crypt-SSLeay-0.73_06.tar.gz.

Comment 8 Jitka Plesnikova 2021-12-15 13:31:13 UTC
The scratch build passed against EPEL 8, so I requested the branch.

https://pagure.io/releng/fedora-scm-requests/issue/39615

Comment 9 Fedora Update System 2021-12-16 08:07:15 UTC
FEDORA-EPEL-2021-9d7cecbfcd has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9d7cecbfcd

Comment 10 Fedora Update System 2021-12-17 01:33:57 UTC
FEDORA-EPEL-2021-9d7cecbfcd has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9d7cecbfcd

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2021-12-25 00:40:19 UTC
FEDORA-EPEL-2021-9d7cecbfcd has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


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