Please branch and build joe in epel10. If you do not wish to maintain joe in epel10, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS ondrejj); please add me through https://src.fedoraproject.org/rpms/joe/adduser
Yes please.
FEDORA-EPEL-2025-810405f461 (joe-4.6-22.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-810405f461
FEDORA-EPEL-2025-810405f461 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-810405f461 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Works for me. Thank you
FEDORA-EPEL-2025-810405f461 (joe-4.6-22.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.
Can you please rebuild for epel10.0 branch? It is present in epel10, but not available in currently used epel10.0. :-(
(In reply to Jan ONDREJ from comment #6) > Can you please rebuild for epel10.0 branch? It is present in epel10, but not > available in currently used epel10.0. :-( What do you mean by currently used? Anyway, done.
FEDORA-EPEL-2025-b26709297a (joe-4.6-22.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b26709297a
Currently "yum install joe" installs from epel-10z, which is epel-10.0. With 10.0 branch we can use it in default installations before RHEL 10.1 release.
FEDORA-EPEL-2025-b26709297a 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-b26709297a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-b26709297a (joe-4.6-22.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.