Bug 2031751

Summary: perl-Apache-Session for EPEL 9
Product: [Fedora] Fedora EPEL Reporter: Xavier Bachelot <xavier>
Component: perl-Apache-SessionAssignee: Paul Howarth <paul>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: paul, perl-devel, steve
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-Apache-Session-1.94-5.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-20 01:59:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2030601    
Bug Blocks:    

Description Xavier Bachelot 2021-12-13 11:50:51 UTC
Hi,

Could you please branch and build perl-Apache-Session for EPEL 9 ?

Regards,
Xavier

Comment 1 Paul Howarth 2021-12-13 13:47:10 UTC
Xavier, can you please do perl-Linux-Pid, which will be needed by mod_perl, which is a dependency of this package?

Comment 2 Xavier Bachelot 2021-12-13 14:00:54 UTC
perl-Linux-Pid branch requested:
https://pagure.io/releng/fedora-scm-requests/issue/39451

Comment 4 Fedora Update System 2022-01-07 18:27:35 UTC
FEDORA-EPEL-2022-4c978716b8 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4c978716b8

Comment 5 Fedora Update System 2022-01-08 01:27:20 UTC
FEDORA-EPEL-2022-4c978716b8 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4c978716b8

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

Comment 6 Fedora Update System 2022-01-20 01:59:09 UTC
FEDORA-EPEL-2022-4c978716b8 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.