Please branch and build msedit in epel10. If you do not wish to maintain msedit 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 julicen); please add me through https://src.fedoraproject.org/rpms/msedit/adduser Reproducible: Always
Koji build task: https://koji.fedoraproject.org/koji/taskinfo?taskID=135563976
Just building the rawhide branch for epel10 won't work because the spec file currently hardcodes the libicu version. To use the same spec file for multiple platforms with different libicu versions, the libicu version must be detected at build time. Here's a pull request that implements that. https://src.fedoraproject.org/rpms/msedit/pull-request/1
Updated SPEC URL: https://download.copr.fedorainfracloud.org/results/julicen/edit/epel-10-x86_64/09365126-msedit/msedit.spec Updated SRPM URL: https://download.copr.fedorainfracloud.org/results/julicen/edit/epel-10-x86_64/09365126-msedit/msedit-1.2.0%5E1.e16b4ab-3.el10.src.rpm Koji build: https://koji.fedoraproject.org/koji/taskinfo?taskID=135596193 With the first PR to the package merged, there is no more ICU version hardcoding and can verify that this package now works in CentOS Stream 10, F43, and F42.
FYI, the Spec/SRPM URL comments are just used for the review bug, and don't have any effect (and aren't needed) for regular bugs. Also, since you're the maintainer of this package, you don't have to file a bug to yourself to add it to an EPEL version. You just need to request the branch and build it. https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/#requesting_branches
Oh ok, thanks for the info. I was just following this documentation for EPEL: https://docs.fedoraproject.org/en-US/epel/epel-package-request/#fedora_packagers
That's the process to request packages in EPEL that you're not a maintainer of. At the top of that page there is this sentence: > If you are already a Fedora contributor, for your own package use the standard procedures for requesting a new branch using fedpkg request-branch. The "standard procedures" text is a link to the maintenance guide I linked in my last comment.
FEDORA-EPEL-2025-ada6d448a3 (Introduce msedit into EPEL10, automatically look for the correct ICU version) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-ada6d448a3
FEDORA-2025-6a1d8e4bfa (Introduce msedit into EPEL10, automatically look for the correct ICU version) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6a1d8e4bfa
FEDORA-2025-6a1d8e4bfa has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6a1d8e4bfa` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6a1d8e4bfa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-ada6d448a3 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-ada6d448a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-6a1d8e4bfa (Introduce msedit into EPEL10, automatically look for the correct ICU version) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-ada6d448a3 (Introduce msedit into EPEL10, automatically look for the correct ICU version) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.