Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1860694
Summary: | Build bwm-ng for EPEL8 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Pablo Greco <pablo> |
Component: | bwm-ng | Assignee: | Oliver Falk <ofalk> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel8 | CC: | i, jima, ofalk, oliver, sven, TicoTimo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | bwm-ng-0.6.2-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-08-12 01:48:16 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
Pablo Greco
2020-07-26 16:23:35 UTC
Hi! Yes, I use to be packager of bwm-ng and also recognized it's missing in EPEL-8. If the current packager team agrees, I'd be willing to take care about the EPEL-8 branch, but someone needs to add me to the maintainers (https://src.fedoraproject.org/rpms/bwm-ng) list, so I can request the epel-8 branch an build it. Pablo, in regards to your note, I don't see bwm-ng being added to RHEL-8 any time soon, but thanks for dropping the ask/question/idea! Oliver (In reply to Oliver Falk from comment #1) > Yes, I use to be packager of bwm-ng and also recognized it's missing in > EPEL-8. > If the current packager team agrees, I'd be willing to take care about the > EPEL-8 branch, but someone needs to add me to the maintainers > (https://src.fedoraproject.org/rpms/bwm-ng) list, so I can request the > epel-8 branch an build it. Feel free to. I had already requested the branch yesterday: https://pagure.io/releng/fedora-scm-requests/issue/27241 I've added you as an admin to the project. Please note that there is a new upstream release out (0.6.2) with some minor fixes. I've built it for rawhide yesterday. Hey Sven, thanks for the quick reply and adding me to the list of maintainers. Glad you already requested the EPEL-8 branch. Once it's done, I'll take care about building for EPEL-8. I guess, we can quickly get this BZ "fixed". Oliver Hi!, thanks for moving this so fast! Oliver: My comment about not being in RHEL was related to the fact that there was no conflict in adding it to EPEL, not that it could be added to RHEL, even my optimism has its limits ;) Thanks again! Pablo. Pablo, ack, thanks for pointing that out. :-) Oliver Scratch build running: https://koji.fedoraproject.org/koji/taskinfo?taskID=48004719 Build finished (https://koji.fedoraproject.org/koji/taskinfo?taskID=48004719). @Pablo, would be great if you could try it out and give feedback if everything is working as expected! Thanks, Oliver @Oliver, just tested in aarch64 and x86_64, all looks good! Thanks for doing this. Pablo. Ack. Will try to build it for the real release now, but it seems we're currently having some issues, due to the mass rebuild for F33. Oliver Oh. Now it's done. Will push Bodhi soon. FEDORA-EPEL-2020-97f73bd1ba has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-97f73bd1ba FEDORA-EPEL-2020-97f73bd1ba 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-2020-97f73bd1ba See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-97f73bd1ba has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. |