Bug 2308883 - Please branch and build perl-Crypt-OpenSSL-Bignum for EPEL 10
Summary: Please branch and build perl-Crypt-OpenSSL-Bignum for EPEL 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Crypt-OpenSSL-Bignum
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPEL10Tracker
TreeView+ depends on / blocked
 
Reported: 2024-09-01 13:21 UTC by Xavier Bachelot
Modified: 2024-09-04 04:13 UTC (History)
2 users (show)

Fixed In Version: perl-Crypt-OpenSSL-Bignum-0.09-28.el10_0
Clone Of:
Environment:
Last Closed: 2024-09-04 04:13:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Xavier Bachelot 2024-09-01 13:21:35 UTC
Hi,

Could you please branch and build perl-Crypt-OpenSSL-Bignum for EPEL 10 ?
I would need it to build another package.

If you don't want or have time to maintain this package in EPEL, I'd be glad
to be added to the package so I can take care of it.
Indeed, I can help with maintaining this in Fedora too.
My FAS username is xavierb.

Regards,
Xavier

Comment 2 Fedora Update System 2024-09-02 11:55:34 UTC
FEDORA-EPEL-2024-ca1d7d05ed (perl-Crypt-OpenSSL-Bignum-0.09-28.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ca1d7d05ed

Comment 3 Fedora Update System 2024-09-03 04:15:32 UTC
FEDORA-EPEL-2024-ca1d7d05ed has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ca1d7d05ed

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

Comment 4 Fedora Update System 2024-09-04 04:13:04 UTC
FEDORA-EPEL-2024-ca1d7d05ed (perl-Crypt-OpenSSL-Bignum-0.09-28.el10_0) has been pushed to the Fedora EPEL 10.0 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.