@kalev this looks like an issue we can fix if you could build, and we can send them to cisco for signing?

Okay, I gave this a thought - think we have to get new builds for having it in rawhide repository, this means this will go through the building it, signing them, and then sending those to cisco, & waiting to get those updated in their CDN's and finally having it here;

For now what would help, creating a repository and having redirects pointing out to it?
OR should we sign the builds with f44 keys?

The redirects can happen on mm with simple query:

mirrormanager2=# select * from repository_redirect where from_repo ILIKE '%openh264%';
 id  |              from_repo              |            to_repo             
-----+-------------------------------------+--------------------------------
 903 | fedora-cisco-openh264-rawhide       | fedora-cisco-openh264-43
 904 | fedora-cisco-openh264-debug-rawhide | fedora-cisco-openh264-debug-43
(2 rows)
mirrormanager2=# UPDATE repository_redirect
SET to_repo = regexp_replace(to_repo, '-43$', '-44')
WHERE from_repo ILIKE '%openh264%';
UPDATE 2
mirrormanager2=# select * from repository_redirect where from_repo ILIKE '%openh264%';
 id  |              from_repo              |            to_repo             
-----+-------------------------------------+--------------------------------
 903 | fedora-cisco-openh264-rawhide       | fedora-cisco-openh264-44
 904 | fedora-cisco-openh264-debug-rawhide | fedora-cisco-openh264-debug-44
(2 rows)

For now they point to 43, because I need to look into how that repo is created.

```

Okay so I think i was able to figure how to create it, so the repository is done.

koji dist-repo f44-openh264 6d9f90a6 --noinherit --with-src -a aarch64 - a x86_64

I'm not sure if the arches look right here?

But we have one here: https://kojipkgs.fedoraproject.org/repos-dist/f44-openh264/

CC: @kevin @adamwill @patrikp @kalev (I think next steps should be getting those builds, and then I thinkwe should redirect it? OR, should I redirect now on an empty repo?)

We do all our supported arches... so, add s390x and ppc64le.

Note that kalev is no longer involved in this. :)

@wtaymans is maintaining openh264 now.

So, I think we should get a empty repo in place now, ask @wtaymans to do a f44/rawhide build(s) and once we have those and they look ok, send to cisco and update...

Might be a nice test of how improved the new process is. Will it take a few days? a few weeks? a few months? I guess we will see...

Yeah, okay for starters, I fixed the dist-repo, as per the SOP. This needs love tho.
And, I fix the redirects, so now the mirrormanager openh264 points to 44

@wtaymans is maintaining openh264 now.

Requesting you to get those builds ready @wtaymans, please thank you.

 id  |              from_repo              |            to_repo             
-----+-------------------------------------+--------------------------------
 903 | fedora-cisco-openh264-rawhide       | fedora-cisco-openh264-44
 904 | fedora-cisco-openh264-debug-rawhide | fedora-cisco-openh264-debug-44
(2 rows)

dist-repo: https://kojipkgs.fedoraproject.org/repos-dist/f44-openh264/6594612/

Please don't fix mirrormanager until the repo it's going to point at at least exists, even if it's empty.

Closing this ticket, as documentation is done against it, in the infra-docs-fpo, there are no replies from the maintainers for the new builds. We can always open this if required.