Bug 2071255 - [RFE: EPEL9] EPEL9 branch for log4cplus
Summary: [RFE: EPEL9] EPEL9 branch for log4cplus
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: log4cplus
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Osvald 🛹
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-02 12:10 UTC by Navneet
Modified: 2022-04-28 06:12 UTC (History)
4 users (show)

Fixed In Version: log4cplus-2.0.5-15.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-28 06:12:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Navneet 2022-04-02 12:10:55 UTC
Description of problem:


Please branch and build log4cplus in epel9.

Comment 1 Navneet 2022-04-14 19:27:44 UTC
Will you be able to branch and build log4cplus in epel9?

Comment 2 Martin Osvald 🛹 2022-04-19 10:41:06 UTC
(In reply to Navneet from comment #1)
> Will you be able to branch and build log4cplus in epel9?

On it, just created a request for the branch:

https://pagure.io/releng/fedora-scm-requests/issue/43771

Comment 3 Fedora Update System 2022-04-19 16:15:57 UTC
FEDORA-EPEL-2022-1101436c67 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1101436c67

Comment 4 Fedora Update System 2022-04-20 19:38:43 UTC
FEDORA-EPEL-2022-1101436c67 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-1101436c67

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

Comment 5 Fedora Update System 2022-04-28 06:12:01 UTC
FEDORA-EPEL-2022-1101436c67 has been pushed to the Fedora EPEL 9 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.