Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Not sure why this was sent my way, but ifuse is already in Fedora, to make it available for CentOS Stream 8 you can request it to be added to EPEL 8 per https://docs.fedoraproject.org/en-US/epel/epel-package-request/ I'm going to turn this into an EPEL 8 request and reassign it to the ifuse maintainer.
Please branch and build ifuse in epel8. If you do not wish to maintain ifuse in epel8, or do not think you will be able to do this in a timely manner, the EPEL Packaging SIG would be happy to be a co-maintainer of the package.
I'm not interested in supporting ifuse in EPEL, thanks.
Would you be open to having the EPEL Packagers SIG co-maintain the EPEL branches? If that's ok, please add the epel-packagers-sig group as a collaborator for epel* on https://src.fedoraproject.org/rpms/ifuse/addgroup so that we may branch and build the package. Thanks!
(In reply to Davide Cavalca from comment #4) > Would you be open to having the EPEL Packagers SIG co-maintain the EPEL > branches? If that's ok, please add the epel-packagers-sig group as a > collaborator for epel* on https://src.fedoraproject.org/rpms/ifuse/addgroup > so that we may branch and build the package. Thanks! As long as I never receive bugmail about it, that's fine. Done.
Thanks! I think if you set the "bugzilla assignee" for EPEL to @epel-packagers-sig on https://src.fedoraproject.org/rpms/ifuse it'll send all EPEL-relazed bugmail to the group. I'll take this ticket and get the branches setup in the meantime.
Branches requested: - epel8: https://pagure.io/releng/fedora-scm-requests/issue/41115 - epel9: https://pagure.io/releng/fedora-scm-requests/issue/41116
(In reply to Davide Cavalca from comment #6) > Thanks! I think if you set the "bugzilla assignee" for EPEL to > @epel-packagers-sig on https://src.fedoraproject.org/rpms/ifuse it'll send > all EPEL-relazed bugmail to the group. I'll take this ticket and get the > branches setup in the meantime. Done.
FEDORA-EPEL-2022-e64f023296 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-e64f023296
FEDORA-EPEL-2022-6cdfae1be9 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6cdfae1be9
FEDORA-EPEL-2022-e64f023296 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-2022-e64f023296 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-6cdfae1be9 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6cdfae1be9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-e64f023296 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-6cdfae1be9 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.