Bug 2029240 - Please build libaec for EPEL9
Summary: Please build libaec for EPEL9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libaec
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Junghans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-05 22:54 UTC by Orion Poplawski
Modified: 2021-12-15 01:35 UTC (History)
1 user (show)

Fixed In Version: libaec-1.0.6-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-15 01:35:34 UTC
Type: Bug

Attachments (Terms of Use)

Description Orion Poplawski 2021-12-05 22:54:40 UTC 
Description of problem:

Looks like libaec has been dropped from RHEL9, so we need to build it for epel9.
You can add me (orion) as an admin if you don't want to maintain it there.  Thanks.
Comment 1 Christoph Junghans 2021-12-06 02:28:48 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/38888
Comment 2 Christoph Junghans 2021-12-06 02:53:21 UTC 
Rest should be easy: https://koji.fedoraproject.org/koji/taskinfo?taskID=79627315
Comment 3 Christoph Junghans 2021-12-06 14:11:35 UTC 
Hang in there: https://koji.fedoraproject.org/koji/taskinfo?taskID=79647187
Comment 4 Fedora Update System 2021-12-06 14:43:08 UTC 
FEDORA-EPEL-2021-b6ceccf2b1 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b6ceccf2b1
Comment 5 Fedora Update System 2021-12-07 01:37:58 UTC 
FEDORA-EPEL-2021-b6ceccf2b1 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-2021-b6ceccf2b1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2021-12-15 01:35:34 UTC 
FEDORA-EPEL-2021-b6ceccf2b1 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.