Bug 2372275 (perl-Proc-ForkSafe-el10) - Please branch and build perl-Proc-ForkSafe in epel10.
Summary: Please branch and build perl-Proc-ForkSafe in epel10.
Keywords:
Status: CLOSED ERRATA
Alias: perl-Proc-ForkSafe-el10
Product: Fedora
Classification: Fedora
Component: perl-Proc-ForkSafe
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: perl-App-cpm-el10
TreeView+ depends on / blocked
 
Reported: 2025-06-11 11:22 UTC by Peter Oliver
Modified: 2025-06-21 02:40 UTC (History)
1 user (show)

Fixed In Version: perl-Proc-ForkSafe-0.001-5.el10_1
Clone Of:
Environment:
Last Closed: 2025-06-21 02:40:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Oliver 2025-06-11 11:22:33 UTC
Please branch and build perl-Proc-ForkSafe in epel10.

If you do not wish to maintain perl-Proc-ForkSafe in epel10,
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 mavit);
please add me through https://src.fedoraproject.org/rpms/perl-Proc-ForkSafe/adduser


Reproducible: Always

Comment 1 Fedora Update System 2025-06-12 08:14:51 UTC
FEDORA-EPEL-2025-7cb2ae40d0 (perl-Carton-1.0.35-9.el10_1, perl-Command-Runner-0.201-1.el10_1, and 5 more) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7cb2ae40d0

Comment 2 Fedora Update System 2025-06-13 01:57:25 UTC
FEDORA-EPEL-2025-7cb2ae40d0 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7cb2ae40d0

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

Comment 3 Fedora Update System 2025-06-21 02:40:24 UTC
FEDORA-EPEL-2025-7cb2ae40d0 (perl-App-FatPacker-0.010008-20.el10_1, perl-Carton-1.0.35-9.el10_1, and 8 more) has been pushed to the Fedora EPEL 10.1 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.