Bug 1849802

Summary: Please build qoauth for EPEL8
Product: [Fedora] Fedora EPEL Reporter: Orion Poplawski <orion>
Component: qoauthAssignee: Troy Dawson <tdawson>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: epel8CC: kde-sig, rdieter, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: qoauth-2.0.0-16.el9 qoauth-2.0.0-16.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-22 09:24:28 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:    
Bug Blocks: 1849800    

Description Orion Poplawski 2020-06-22 20:17:38 UTC
Description of problem:

Please consider building kbibtex for EPEL8.  If you are not interested in maintaining it in EPEL, please add me (FAS orion) as an admin on the package so that I can request the EPEL8 branch.  Thanks.

At the moment this is needed for kbibtex.

Looks like we have some missing deps though:
DEBUG util.py:621:  No matching package to install: 'pkgconfig(QtCore)'
DEBUG util.py:621:  No matching package to install: 'pkgconfig(QtNetwork)'
DEBUG util.py:621:  No matching package to install: 'pkgconfig(qca2)'
DEBUG util.py:621:  No matching package to install: 'qca-ossl'

Probably just need to disable Qt4 builds for EL8.

https://koji.fedoraproject.org/koji/taskinfo?taskID=45997426

Comment 1 Orion Poplawski 2023-01-15 03:46:22 UTC
Please branch and build qoauth in epel9.

If you do not wish to maintain qoauth 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/qoauth/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: qoauth).

(optionally, if there's not a separate Bugzilla assignee for EPEL)
I can be the primary contact for EPEL (FAS: qoauth).

Comment 2 Orion Poplawski 2023-01-22 19:06:37 UTC
Will you be able to branch and build qoauth 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 3 Troy Dawson 2023-02-10 16:51:50 UTC
I'll get it.
For some reason this never showed up in my email.

Comment 4 Fedora Update System 2023-02-13 17:41:18 UTC
FEDORA-EPEL-2023-18f99fb1b7 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-18f99fb1b7

Comment 5 Fedora Update System 2023-02-13 17:41:57 UTC
FEDORA-EPEL-2023-5a48b42788 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5a48b42788

Comment 6 Fedora Update System 2023-02-14 00:23:28 UTC
FEDORA-EPEL-2023-18f99fb1b7 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-18f99fb1b7

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

Comment 7 Fedora Update System 2023-02-14 02:42:44 UTC
FEDORA-EPEL-2023-5a48b42788 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-2023-5a48b42788

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

Comment 8 Fedora Update System 2023-02-22 09:24:28 UTC
FEDORA-EPEL-2023-5a48b42788 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2023-02-22 10:02:11 UTC
FEDORA-EPEL-2023-18f99fb1b7 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.