koschei tracks packages in EPEL 9 NEXT that don't even have an epel9-next branch

[decathorpe]

For example: https://koschei.fedoraproject.org/package/rust-dav1d-sys?collection=epel9-next

The package does not have an epel9-next branch at all: https://src.fedoraproject.org/rpms/rust-dav1d-sys/branches?branchname=rawhide

Not sure how this can happen.

[decathorpe]

Other examples:

https://koschei.fedoraproject.org/package/rust-allocator-api2?collection=epel9-next https://koschei.fedoraproject.org/package/rust-minidom0.12?collection=epel9-next

[mizdebsk]

After investigation I think that's not an issue in Koschei. In my opinion this is Koji misconfiguration (Koji tag inheritance should be fixed).

rust-dav1d-sys package is allowed for Koji tag epel9-next-build. This is inherited from tag epel9. See:

$ koji list-pkgs --tag epel9-next-build --package rust-dav1d-sys
Package                 Tag                     Extra Arches     Owner          
----------------------- ----------------------- ---------------- ---------------
rust-dav1d-sys          epel9                                    decathorpe     

Even if epel9-next branch does not exist it is still possible to build the package, for example from an arbitrary branch.

[decathorpe]

Thanks for investigating, I've filed a releng ticket: https://pagure.io/releng/issue/11540