Description of problem: I am packaging a vim plugin which requires editorconfig for Fedora (https://bugzilla.redhat.com/show_bug.cgi?id=1948777), and I intend to build it for EPEL8, which would require the editorconfig package to exist there. Version-Release number of selected component (if applicable): N/A How reproducible: Check if there is an epel8 branch. Actual results: There is none. Expected results: There is one. Additional info: No spec file changes are required to support EPEL8, but if you want a co-maintainer to take care of any EPEL issues, I would be willing to do it.
I don't really have time to maintain an EPEL 8 branch myself, but since you volunteered ... :) You should be listed as collaborator and default EPEL bug assignee here: https://src.fedoraproject.org/rpms/editorconfig I have also requested the epel8 branch: https://pagure.io/releng/fedora-scm-requests/issue/33497 As soon as that ticket has been processed, you should be able to push to the epel8 branch, and do builds for EPEL 8 as needed.
Thanks! I have built the EPEL 8 package (https://koji.fedoraproject.org/koji/buildinfo?buildID=1735733); however, collaborator status currently is not enough to let me create a Bodhi update (https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/U7GURQ6SHTDGCRSWIX4V5S2APAI6FNDF/). Would you mind upgrading me to commit access?
Ah, sorry about that. I thought that bodhi with the fix for that issue had been deployed. I've upgraded you to commit access :)
FEDORA-EPEL-2021-ef22520a02 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-ef22520a02
FEDORA-EPEL-2021-ef22520a02 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-2021-ef22520a02 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2021-ef22520a02 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.