Hide Forgot
Description of problem: Please branch and build python-pathspec for epel9. Koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=80055371 I can help co-maintain this package.
As a co-maintainer, I don't mind if you do, but I am not doing it.
Hello, I just requested a new branch: https://pagure.io/releng/fedora-scm-requests/issue/39768
Opened a PR: https://src.fedoraproject.org/rpms/python-pathspec/pull-request/7
*** Bug 2041978 has been marked as a duplicate of this bug. ***
This is now finally fixed in distgit. Whoever requested the branch, now is your time to build it and ship it.
@dradez has submitted a koji build (https://koji.fedoraproject.org/koji/taskinfo?taskID=81416018). I attempted to create an update via bodhi, but I do not have commit access to the repo.
I don't think I have access either. Maybe we could get Adrien to do it. I see Miro and Adrien are the maintainers so they should have permission.
I have permission but no intention to maintain an API-stable version of pathspec for a decade. I can help this one time, but I'd rather avoid doing it not to be "the person who brought this in".
Miro, If you'd be willing for me to be a co-maintainer I can service the epel9 branch and builds for the package.
Done.
I am also interested in co-maintaining this package.
FEDORA-EPEL-2022-b1ed1bcdeb has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b1ed1bcdeb
Thanks Miro, Robby and Dan for your work here. Last month when I created the epel9 branch and updated the spec file to latest version, builds on Koji were failing. I'm glad that it works now.
FEDORA-EPEL-2022-b1ed1bcdeb 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-b1ed1bcdeb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-b1ed1bcdeb has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.