Bug 2108867
| Summary: | Please branch and build mytop in epel9 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Jonathan Wright <jonathan> |
| Component: | mytop | Assignee: | Terje Røsten <terje.rosten> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel9 | CC: | benmwebb, mmckinst, terje.rosten |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | mytop-1.7-24.b737f60.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-12 02:14:53 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: | |||
|
Description
Jonathan Wright
2022-07-19 21:42:18 UTC
Will you be able to branch and build mytop in epel9? I would be happy to be a co-maintainer if you do not wish to build it on epel9 (FAS: jonathanspw). FWIW, I rebuilt the EPEL8 mytop SRPM in a RHEL 9 mock environment, and it built successfully without needing any changes. The resulting binary also appears to work normally. So I imagine branching would be straightforward. FEDORA-EPEL-2022-e6b1a2c937 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-e6b1a2c937 FEDORA-EPEL-2022-e6b1a2c937 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-e6b1a2c937 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-e6b1a2c937 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. |