Bug 2125827

Summary: request adding log4c to epel 9
Product: [Fedora] Fedora EPEL Reporter: Conor Lennon <conorlennon222>
Component: log4cAssignee: Steve Traylen <steve.traylen>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: steve.traylen, valtri
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: log4c-1.2.4-25.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-28 10:40:18 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:

Description Conor Lennon 2022-09-10 21:53:50 UTC
Description of problem:
log4c missing from epel9

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

log4c is present at
https://mirror.serverion.com/epel/8/Everything/x86_64/Packages/l/
but not at 
https://mirror.serverion.com/epel/9/Everything/x86_64/Packages/l/

Comment 2 Fedora Update System 2022-10-21 06:02:57 UTC
FEDORA-EPEL-2022-c14b138be5 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c14b138be5

Comment 3 Fedora Update System 2022-10-21 10:04:38 UTC
FEDORA-EPEL-2022-c14b138be5 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-c14b138be5

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

Comment 4 Conor Lennon 2022-10-21 13:08:25 UTC
I've enabled the epel-testing repo, tested installing log4c and log4c-devel packages, and verified that I can use it.
All works

Comment 5 Fedora Update System 2022-10-28 10:40:18 UTC
FEDORA-EPEL-2022-c14b138be5 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.