Bug 2030421 - Please branch and build libcec in epel9
Summary: Please branch and build libcec in epel9
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libcec
Version: epel9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Andrew Bauer
QA Contact: Fedora Extras Quality Assurance
Depends On: 2031259
TreeView+ depends on / blocked
Reported: 2021-12-08 18:06 UTC by Gary Buhrmaster
Modified: 2022-01-20 02:28 UTC (History)
3 users (show)

Fixed In Version: libcec-6.0.2-4.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-01-20 02:28:09 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Fedora Pagure releng/fedora-scm-requests issue 39334 0 None None None 2021-12-10 22:18:34 UTC

Description Gary Buhrmaster 2021-12-08 18:06:31 UTC
Please branch and build libcec in epel9.

If you do not wish to maintain libcec in epel9, 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 userid: gtb


Comment 1 Andrew Bauer 2022-01-11 17:32:11 UTC
Taking over this build request. As noted it is currently blocked by package platform. I will update this bug as soon as I have new information.

Comment 2 Fedora Update System 2022-01-12 03:28:06 UTC
FEDORA-EPEL-2022-c49b853cef has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c49b853cef

Comment 3 Fedora Update System 2022-01-13 02:03:17 UTC
FEDORA-EPEL-2022-c49b853cef 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-c49b853cef

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

Comment 4 Fedora Update System 2022-01-20 02:28:09 UTC
FEDORA-EPEL-2022-c49b853cef 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.