That's not quite right for the directory structure. While CentOS Stream reflects the content planned for the next RHEL minor version, it doesn't actually have a minor version, or more specifically for our purposes it doesn't know what minor version repo to request. We've set up epel-release with metalinks that will request just the major version on CentOS, and the major.minor on RHEL. So the directory structure actually needs to start with epel/10/ using 10.0 builds, and then later add epel/10.0/ for 10.0 builds and switch epel/10/ to using 10.1 builds. That pattern will continue through all the minor versions.

That makes sense to me - thanks, @carlwgeorge!

For some context, we currently don't have a way to generate the composes because odcs (which we used) was recently retired.
We are looking at what would be the best way to do it going forward.
More information:
https://pagure.io/fedora-infrastructure/issue/12112#comment-938325

OpenH264 2.6.0 has been released, so this is now obsolete.

Hello. :wave:

I am happy to report that we should now have a way of doing this again.

We discussed this during the releng weekly meeting.
2.6.0 came out in the meanwhile.
However, when I look at the builds in Koji [1] I can only see 2.5.0 as the highest version.
What would be the best course of action from here? We think new (2.6.0) builds for the relevant Fedora versions and EPEL are the way to go so that it can all be sent at once.

What do you think?

CC: @kalev @catanzaro

[1] https://koji.fedoraproject.org/koji/packageinfo?packageID=21431

Relevant tickets:
https://pagure.io/releng/issue/12466
https://pagure.io/releng/issue/12585

And if that's the way to go could you please create a new ticket related to 2.6.0 so we can track all of it in one ticket and close the duplicates? Thank you.

Here is a ticket for 2.6.0: https://pagure.io/releng/issue/12585

And here is another ticket for 2.6.0: https://pagure.io/releng/issue/12466

But those are Fedora tickets, and this is an EPEL ticket. Eh. I guess those two tickets are clearly duplicates, and one of them should be closed.

Anyway, the developers with commit access to this package are @kalev, but he has just left Red Hat so let's not ask him to do this work anymore, and @wtaymans. Let's talk to Wim about getting a new build.

Maybe it would be easiest to handle Fedora and EPEL builds all in one issue report?

Um, and yes there's no point in upgrading to anything other than 2.6.0 at this point. 2.6.0 is urgent due to the heap buffer overflow issue that I mentioned here.

The big tracker ticket for all Fedora and EPEL versions can be found here: https://pagure.io/releng/issue/12617