Description of problem: fzf is a general-purpose command-line fuzzy finder. It is available in Fedora but not in CentOS 8. It would be useful to have it available in CentOS 8. Fedora package: https://src.fedoraproject.org/rpms/fzf Version-Release number of selected component (if applicable): N/A How reproducible: N/A Steps to Reproduce: N/A Actual results: N/A Expected results: N/A Additional info: This is my first bug report. Please let me know if the category is not correct.
I have no interest in EPEL. If you want it there, you'll have to become the EPEL maintainer or find someone with such interest to do so.
Are you interested in this, @miminar?
Yes, I'll take care of it next week.
PS, now that we have branch-specific assignees, should I set you as EPEL contact?
Hi Elliott, yes, you can.
Update: waiting for approval of epel8 branch's creation: https://pagure.io/releng/fedora-scm-requests/issue/32118
Hi Elliott, it looks like you need to make the request: https://pagure.io/releng/fedora-scm-requests/issue/32118
https://pagure.io/releng/fedora-scm-requests/issue/32789
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
*** Bug 2229488 has been marked as a duplicate of this bug. ***
Not sure what happened to the previous attempt to package this in EPEL 8. I'm personally not interested in EPEL 8 so marking this back and NEW and not assigned to anyone.
*** Bug 2283837 has been marked as a duplicate of this bug. ***
I worked up some changes to the spec file that would have it working from epel8 all the way to rawhide. https://src.fedoraproject.org/rpms/fzf/pull-request/6
FEDORA-EPEL-2025-7bcf0bdebb 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-2025-7bcf0bdebb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-7bcf0bdebb (fzf-0.58.0-2.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.