Bug 2488310 - Please branch and build perl-Digest-SHA3 in epel8
Summary: Please branch and build perl-Digest-SHA3 in epel8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Digest-SHA3
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-12 10:36 UTC by Paul Howarth
Modified: 2026-06-24 00:55 UTC (History)
2 users (show)

Fixed In Version: perl-Digest-SHA3-1.05-12.el8
Clone Of:
Environment:
Last Closed: 2026-06-24 00:55:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Paul Howarth 2026-06-12 10:36:33 UTC 
Please branch and build perl-Digest-SHA3 in epel8.

If you do not wish to maintain perl-Digest-SHA3 in epel8,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS pghmcfc);
please add me through https://src.fedoraproject.org/rpms/perl-Digest-SHA3/adduser

The current Rawhide package builds successfully in epel8.

The package is needed for a security update for perl-Crypt-PBKDF2.
Comment 1 Fedora Update System 2026-06-15 13:47:48 UTC 
FEDORA-EPEL-2026-6bccebf2f6 (perl-Digest-SHA3-1.05-12.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-6bccebf2f6
Comment 2 Fedora Update System 2026-06-16 01:29:01 UTC 
FEDORA-EPEL-2026-6bccebf2f6 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-2026-6bccebf2f6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2026-06-24 00:55:53 UTC 
FEDORA-EPEL-2026-6bccebf2f6 (perl-Digest-SHA3-1.05-12.el8) 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.