Bug 2124260
| Summary: | Cannot build kronosnet-epel for epel9 until libqb-devel is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Davide Cavalca <davide> |
| Component: | kronosnet-epel | Assignee: | Davide Cavalca <davide> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel9 | CC: | davide |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-10-14 13:09:48 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: | 2121845 | ||
| Bug Blocks: | 2121777 | ||
|
Description
Davide Cavalca
2022-09-05 13:03:09 UTC
For now I'm working around this by building libqb-epel to provide the missing subpackage. If/when this is added to CRB I will retire it. Package request: $ fedpkg request-repo --exception libqb-epel https://pagure.io/releng/fedora-scm-requests/issue/48199 $ fedpkg request-branch --repo libqb-epel epel9 https://pagure.io/releng/fedora-scm-requests/issue/48200 FEDORA-EPEL-NEXT-2022-e58e072f55 has been submitted as an update to Fedora EPEL 9 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-e58e072f55 FEDORA-EPEL-2022-22fa6cf82b has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-22fa6cf82b FEDORA-EPEL-2022-22fa6cf82b has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-NEXT-2022-e58e072f55 has been pushed to the Fedora EPEL 9 Next stable repository. If problem still persists, please make note of it in this bug report. |