Bug 2046034
Summary: | Please build copr-rpmbuild in EPEL 9 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Pavel Raiskup <praiskup> |
Component: | copr-rpmbuild | Assignee: | Pavel Raiskup <praiskup> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel9 | CC: | clime7, copr-team, jkadlcik, pasik, praiskup, turecek.dominik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | copr-rpmbuild-0.61-1.el9 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-06-11 01:00:48 UTC | Type: | --- |
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: | 2031940, 2046035, 2046036 | ||
Bug Blocks: |
Description
Pavel Raiskup
2022-01-26 08:39:04 UTC
Do we want to build it for EPEL9 though? We don't even build it for EPEL8. Or do we want to build it for both of them from now on? I don't think we have to build it - but I would prefer it. This is a low-priority bug. We at least _test_ the package against EPEL 8: https://copr.fedorainfracloud.org/coprs/g/copr/copr-dev/monitor/ FEDORA-EPEL-2023-55060595c1 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-55060595c1 FEDORA-EPEL-2023-55060595c1 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-55060595c1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-55060595c1 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. |