This is a dependency for public-inbox, that I'm trying to package for EPEL8 and 9. I'm happy to comaintain (FAS: salimma) and be set to be the POC for EPEL bugs. You can also add the epel-packagers-sig group as collaborator on epel* branches. Thanks!
Will you be able to branch and build perl-Plack-Middleware-ReverseProxy in epel8 and epel9? I would be happy to be a co-maintainer if you do not wish to build it on epel9 (FAS salimma).
I've requested an epel8 branch: https://pagure.io/releng/fedora-scm-requests/issue/41013 For EPEL9, we still need perl-Plack
(In reply to Emmanuel Seyman from comment #2) > I've requested an epel8 branch: > https://pagure.io/releng/fedora-scm-requests/issue/41013 > > For EPEL9, we still need perl-Plack thanks, looks like the branch is processed. Can we just build this for EPEL 8 first? EPEL 9 is less urgent, for my package there are other missing dependencies and those requesting EPEL are still mostly on 8 for the next few months.
Making this bug EPEL8 only, I cloned it to request EPEL9 so when the EPEL8 update is pushed it won't auto-close the EPEL9 request.
FEDORA-EPEL-2022-d343e3c1cc has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d343e3c1cc
(In reply to Michel Alexandre Salim from comment #4) > > Making this bug EPEL8 only, I cloned it to request EPEL9 so when the EPEL8 > update is pushed it won't auto-close the EPEL9 request. This wouldn't have happened since the EPEL8 update wasn't tied to this bug. Since this bug is now EPEL8-only, I've edited the update to auto-close the bug.
FEDORA-EPEL-2022-d343e3c1cc has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.