Hi, Could you please branch and build linuxconsoletools for EPEL 10 ? It is needed to build another package. Regards, Xavier
Could you please build it in the epel10.0-build-side-102942 side tag, so I can push everything gpm related at once ?
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
Hi, Is linuxconsoletools going to be branched and built for EPEL 10 ? This is blocking gpm. Regards, Xavier
FEDORA-EPEL-2025-55370eeb05 (linuxconsoletools-1.8.1-9.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-55370eeb05
Hi, please also request branch epel10.0 like it was done for other recent packages, for example: https://pagure.io/releng/fedora-scm-requests/issue/72788 https://pagure.io/releng/fedora-scm-requests/issue/72787
To be clear, it's not required to add new packages to EPEL 10.0 at this point. We're after the branching point, so similar to Fedora it is better to focus on bugfixes in the branched release (epel10.0) and limit new features and new packages to the main branch (epel10). The origin of this bug is the gpm dependency on linuxconsoletools, and we can easily unpush the gpm-1.20.7-48.el10_0 update and only promote the gpm-1.20.7-48.el10_1 update to stable.
but gpm will be available when RHEL10 is announced ? or only on RHEL10 update 1 ?
While it's maybe not required to add new packages to EPEL 10.0 at this point, I still would like to see gpm in EPEL 10.0, because from my understanding only EPEL 10.0 targets RHEL 10 GA. Might be that Red Hat only thinks about RHEL 10.1 internally, but I can't wait until RHEL 10.1 in November/December for having a working gpm on a RHEL system for the first time…
> but gpm will be available when RHEL10 is announced ? or only on RHEL10 update 1 ? It depends on what happens to each of those bodhi updates. EPEL 10.0 and EPEL 10.1 are separate repos, corresponding to the minor version of RHEL 10. Decisions can be made for them independently. A package that is only in EPEL 10.1 will not be available to RHEL users until RHEL 10.1 is released.
Right , that is the reason why I think is better request branch epel10.0
> While it's maybe not required to add new packages to EPEL 10.0 at this point, I still would like to see gpm in EPEL 10.0, because from my understanding only EPEL 10.0 targets RHEL 10 GA. That's fine, you can want a package in EPEL 10.0, but it is up to the maintainer to agree or decline, which is all I was clarifying. It's the same scenario if a package was added to Rawhide and you would like to also see it in Fedora 42. Or if you file a support case to add a package to RHEL, and it's approved for the next minor release, not the current one. > Might be that Red Hat only thinks about RHEL 10.1 internally, You know this isn't true, so I don't know why you would even bother with such a flippant accusation. I've literally spent the majority of my day today planning the EPEL 10.0 and RHEL 10.0 integration. Many other Red Hatters are incredibly busy getting RHEL 10.0 itself ready. > but I can't wait until RHEL 10.1 in November/December for having a working gpm on a RHEL system for the first time… I'll remind you that EPEL packages are maintained by volunteers, and it isn't appropriate to make demands in this way. We've been talking about the EPEL 10 plan for over two years now, and from the very beginning we have described the intent to enable maintainers to focus their work on the epel10 branch and defer most changes to the next RHEL minor version. If you wanted to ensure gpm was available in EPEL 10.0, then you should have started working on it and its dependencies sooner.
(In reply to Carl George 🤠 from comment #11) > I'll remind you that EPEL packages are maintained by volunteers […] Thank you for pointing out that I only volunteered for gpm, but somehow forgot for linuxconsoletools. Vasiliy, feel free to add me as co-maintainer (FAS name: robert).
FEDORA-EPEL-2025-55370eeb05 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-55370eeb05 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
(In reply to Robert Scheck from comment #12) > (In reply to Carl George 🤠 from comment #11) > > I'll remind you that EPEL packages are maintained by volunteers […] > > Thank you for pointing out that I only volunteered for gpm, but somehow > forgot for linuxconsoletools. > > Vasiliy, feel free to add me as co-maintainer (FAS name: robert). Done
FEDORA-EPEL-2025-a6ddd42bd7 (linuxconsoletools-1.8.1-9.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6ddd42bd7
FEDORA-EPEL-2025-a6ddd42bd7 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6ddd42bd7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-55370eeb05 (linuxconsoletools-1.8.1-9.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-a6ddd42bd7 (linuxconsoletools-1.8.1-9.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.