Bug 2030927

Summary: Please build lirc for EPEL 9
Product: [Fedora] Fedora EPEL Reporter: Robert Scheck <redhat-bugzilla>
Component: lircAssignee: Richard Shaw <hobbes1069>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: epel9CC: hobbes1069, jarodwilson, kwizart, leamas.alec, sean, xavier
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lirc-0.10.0-36.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-28 01:00:21 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: 2101613    
Bug Blocks: 1914423, 2110099    

Description Robert Scheck 2021-12-10 01:37:59 UTC
Description of problem:
Please build lirc for EPEL 9, because it's a dependency of the audacious-plugins package.

Version-Release number of selected component (if applicable):
lirc-0.10.0-32.fc36

Actual results:
No lirc in EPEL 9.

Expected results:
lirc-0.10.0-32.el9 - or better ;-)

Additional info:
Please let me know if you are not interested in maintaining the package on EPEL 9 branch.

Comment 1 Sean Young 2021-12-10 09:07:49 UTC
Another option would be to make audacious-plugins not depend on lirc. If audacious-plugins
is using lirc for input from remotes, then most of the functionality has been supplanted by
IR decoding in-kernel, which can be configured with ir-keytable. This can use custom decoders
using BPF IR decoding.

Comment 2 Robert Scheck 2021-12-10 09:20:46 UTC
That is indeed also an option. As audacious-plugins uses lirc at EPEL 8 and at Fedora, I didn't investigate into other options, yet. I also didn't cross-check whether there are other applications which could integrate lirc as well or whether audacious-plugins would be the only consumer.

Comment 3 Robert Scheck 2022-06-27 23:01:28 UTC
*** Bug 2082159 has been marked as a duplicate of this bug. ***

Comment 4 Robert Scheck 2022-06-28 00:02:16 UTC
Please branch and build lirc in epel9.

If you do not wish to maintain lirc in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/lirc/addgroup and grant it commit access, or collaborator access on epel* branches.

Comment 5 Robert Scheck 2022-07-09 00:13:23 UTC
Will you be able to branch and build lirc in epel9? The EPEL Packagers SIG would be happy to be a co-maintainer if you do not wish to build it on epel9.

Comment 6 Richard Shaw 2022-07-19 02:01:05 UTC
epel sig now has commit access. Is there a "person" I can assign for bugzilla?

Comment 7 Robert Scheck 2022-07-19 08:13:00 UTC
The epel-packagers-sig should be assignable.

Comment 8 Fedora Update System 2022-07-19 21:05:07 UTC
FEDORA-EPEL-2022-68e1435022 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-68e1435022

Comment 9 Fedora Update System 2022-07-20 01:54:56 UTC
FEDORA-EPEL-2022-68e1435022 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-68e1435022

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

Comment 10 Fedora Update System 2022-07-28 01:00:21 UTC
FEDORA-EPEL-2022-68e1435022 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.