It appears that the automation that files these epel2rhel tickets has problems.
I got this ticket today: https://bugzilla.redhat.com/show_bug.cgi?id=2305965
There are no Rust packages built for EPEL 10 yet at all. rust-sequoia-sq is only in EPEL 9 so far.
Metadata Update from @carlwgeorge: - Issue tagged with: meeting
The workflow for adding a package to RHEL requires an epel repo to point to. For RHEL 10, it was decided that it would be easier to put the epel checking in place from the beginning rather than add it later. Since they needed a repo to point to, they pointed to the epel9 repo, but the step was marked as Optional. (I think that's the term). Internally I have been assuring maintainers that they can really skip/waive that step for now. But it looks like someone went ahead and filed the optional bug. I'm actually surprised it hasn't happened before. Maybe someone heard that epel10 was available and thought it was doing a real check.
Anyway, as soon as we have an epel10 repo on the mirrors, no matter how small, I will work with the team to get things switched over to point to the epel10 repo for RHEL10 package additions.
I'll leave this issue open to track it, and will close it when they've got the new procedure in place.
Metadata Update from @carlwgeorge: - Issue untagged with: meeting
This has been fixed for several months. Closing.
Metadata Update from @tdawson: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/epel/steering/issues/291
Please continue any further discussion there.