I would also be interested in seeing this package available in EPEL 10.

The current tip of rawhide builds and installs cleanly without changes: https://koji.fedoraproject.org/koji/taskinfo?taskID=140775304

If testing and/or maintenance is a blocker, please consider adding me (FAS cottsay) as an EPEL-only co-maintainer.

Hello Giovanni and Scott, sorry for the delay. I just `fedpkg request-branch epel10`, built the package on Koji, and submitted the update: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-751ad3cf7a

Hi Adrien, thanks for building and releasing the package in EPEL 10. At present, the `epel10` branch builds for EPEL 10.2, which will be the next minor release of RHEL 10.

Would you mind branching into the `epel10.1` branch as well so that we can use this package before the 10.2 release?

Hello Scott,

Sure, I just `fedpkg request-branch epel10.1` and it succeeded.

However there are 2 problems.

1. Building yamllint-1.37.1-1.el10_1 fails with:

       GenericError: Repo request no longer active

   I tried 3 times within one hour, see latest Koji build:
   https://koji.fedoraproject.org/koji/taskinfo?taskID=141684100

2. A few weeks ago, I couldn't build latest yamllint version (1.38.0) for EPEL 10, and I assume it will be the same for EPEL 10.1.

   Indeed, yamllint 1.38 depends on a recent version of python-pathspec (≥ 1.0.0), which I could successfully update for EPEL 9, Fedora 42, Fedora 43 and rawhide… But not for EPEL 10 / 10.1, because there does not seem to exist an epel10 or epel10.1 branch:

       $ fedpkg clone python-pathspec
       $ cd python-pathspec
       $ fedpkg switch-branch epel10.1
       $ fedpkg switch-branch epel10.1
       Could not execute switch_branch: Unknown remote branch origin/epel10.1

       $ fedpkg request-branch epel10.1
       Could not execute request_branch: This package is already an EL package, therefore it cannot be in EPEL. If this is a mistake or you have an exception, please contact the Release Engineering team.

       $ git branch -a
         remotes/origin/epel7
         remotes/origin/epel8
         remotes/origin/epel8-playground
         remotes/origin/epel9
         remotes/origin/f25
         remotes/origin/f26
         …
         remotes/origin/f42
         remotes/origin/f43
         remotes/origin/main
         remotes/origin/rawhide

I'm not an expert about EPEL packaging, so if you know what to do, feel free to share and/or co-maintain yamllint for EPEL.

Thanks Adrien, it looks like the branch request for EPEL 10.1 indeed went through.

The python-pathspec package is part of RHEL 10 itself (via the CRB repo), so it isn't maintained by Fedora or EPEL.

I was able to `fedpkg scratch-build` from the EPEL 10.1 branch of `yamllint` successfully: https://koji.fedoraproject.org/koji/taskinfo?taskID=141834060

Maybe this was an infrastructure hiccup. Can you build successfully now?

Also, note that the `epel10.1` branch appears to be 1 commit behind `epel10`. You may wish to fast-forward it even with `epel10` prior to building.

Hello Scott, please excuse the delay.

Indeed it was an infrastructure hiccup: I just `fedpkg build` again and it succeeded!
I submitted the update for EPEL 10.1 on Bodhi.

I don't know much about CRB and non-free Red Hat repositories, but it looks like python-pathspec ≥ 1.0.0 is not packaged there. For this reason, the commit you mention (the latest commit on branch `epel10`) wouldn't build: it updates to yamllint version 1.38, but yamllint 1.38 needs python-pathspec ≥ 1.0.0.
So on EPEL 10 / EPEL 10.2, we should either rollback to yamllint 1.37, or wait for Red Hat to package python-pathspec ≥ 1.0.0.

I don't know what to do here. Maybe it would be better if python-pathspec was still community-maintained in EPEL 10?