Bug 1279241
Summary: | roxterm not available in epel9 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | ackthet |
Component: | roxterm | Assignee: | Pete Walter <walter.pete> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel7 | CC: | dan, i, michel, rosset.filipe, walter.pete |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | roxterm-3.12.1-1.el9 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-10-09 15:27:24 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
ackthet
2015-11-08 19:55:16 UTC
Pete, can you please request the branch for epel9? Thanks. Yes, of course: https://pagure.io/releng/fedora-scm-requests/issue/47750 Will you take care of the builds? I'll add you as a co-maintainer. (In reply to Pete Walter from comment #2) > Yes, of course: https://pagure.io/releng/fedora-scm-requests/issue/47750 > > Will you take care of the builds? I'll add you as a co-maintainer. sure, go ahead, thanks. Okay, the branch is now created and you are a co-maintainer. Thanks! FEDORA-EPEL-2022-e79a57674b has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-e79a57674b FEDORA-EPEL-2022-e79a57674b 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-e79a57674b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-e79a57674b has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. |