• Describe the issue

It looks like two packages that were built around the time of the F35 mass branching were left in an inconsistent state (both koji builds were started on Tue, 10 Aug 2021 around 19:00 UTC):

• rubygem-dnsruby: https://koji.fedoraproject.org/koji/buildinfo?buildID=1816812
  has an .fc35 dist tag, but koji build is only tagged with f36 and not f35

• svt-vp9: https://koji.fedoraproject.org/koji/buildinfo?buildID=1816809
  has an .fc35 dist tag, but koji build is still stuck in f36-updates-candidate
  has been submitted to bodhi for Fedora 35 (?!) but is stuck pending (probably because the build is mis-tagged): https://bodhi.fedoraproject.org/updates/FEDORA-2021-8c73bd3cf4

• When do you need this? (YYYY/MM/DD)

Before Fedora 35 final freeze goes into effect (Oct. 05, 2021) would be great.

• When is this no longer needed or useful? (YYYY/MM/DD)

After Fedora 35 EOL (November 2022?)

• If we cannot complete your request, what is the impact?

Packages are stuck in an inconsistent state for the lifetime of Fedora 35 and possibly Fedora 36.

It might be possible that more packages are impacted, but those two affect upgrade path from Fedora 34 to 35, so they were easy to find. However, looking into other koji builds that were started at the same time might yield packages with similar issues (though I don't know of an easy way to query for this).