#11955 Please send openh264 2.4.1 builds to Cisco
Closed: Fixed 23 days ago by patrikp. Opened 4 months ago by kalev.

Please sign etc and send the following five builds to Cisco for hosting:

openh264-2.4.1-2.fc41
openh264-2.4.1-2.fc40
openh264-2.4.1-1.fc39
openh264-2.4.1-1.fc38
openh264-2.4.1-1.el9

This is mostly needed to push out an initial openh264 .fc41 build for rawhide that is currently missing after branching. I've tested the 2.4.1 builds and they work well for me and I think they are suitable for stable branches as well.

Note that the gstreamer plugin is gone from the fc41 and fc40 builds, and this is expected. We ship it in Fedora proper instead now.


Metadata Update from @patrikp:
- Issue assigned to patrikp

4 months ago

Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

4 months ago

The 2.4.1 builds were sent to Cisco for hosting, I'll give an update here when they update their CDN. :thumbsup:
Note that EPEL9 hasn't been sent yet because of technical difficulties with generating the compose, trying to sort that out.

Quick note about EPEL9. I think the inability to generate the compose may be related to the build not being signed. However, it can't be signed manually at this time. (more details about that in the PR linked below)
I have a PR open here: https://pagure.io/fedora-infra/ansible/pull-request/1842
But it'll have to wait until the freeze is over to get merged.

Quick update: I got confirmation from Cisco this morning that they updated their CDN.
However, when I try to verify it I'm not successful.

curl -I http://ciscobinary.openh264.org/openh264-2.4.1-1.fc39.x86_64.rpm
HTTP/1.1 404 Not Found

I will give it some time and if it's not there by tomorrow I'll investigate.

@kalev Everything seems to be in order on Cisco CDN side. How would you like me to go about updating our side? Do all at once, or just some and we wait a while (as with 2.3.1)?

@patrikp Nice! I think I'd update rawhide (F41) now so that we can get the initial rawhide build out (the rawhide repo is currently empty after branching) and hold updating the stable branches until we get some testing feedback from other people. We don't go through updates-testing with this so I think it's worth testing it in rawhide first.

@kalev Still waiting on this update Fedora 41.

@romualdo Sorry, I don't think I can do anything more to help this along, I'm waiting on this too. It needs releng to update the repo metadata now.

@kalev The repo for F41 has been updated. I had mirrormanager update the codecs dir but I don't have the needed rights to force all the proxies to sync the codec content immediately, please give it a bit of time. Thanks!
CC: @romulasry

Awesome, thanks @patrikp! Let's give it two weeks and then update the rest of the branches as well if nothing comes up.

Hello @kalev :wave:
Are we all good to update the rest of the branches?

Hello @patrikp :wave:
I think we should be good to update the rest of the branches - I haven't heard of any regressions.

There is only one significant commit between these two versions, and it apparently fixes https://bugzilla.redhat.com/show_bug.cgi?id=2042003, so yes please. :)

F41, F40, F39, and F38 branches should be updated on our side now. :thumbsup:

It's been two weeks. Have we not heard back from Cisco yet?

@catanzaro I am not sure I understand what you mean. Could you please elaborate?

Cisco published the RPMs on their CDN a while ago and the composes were synced to our servers.

For example F39:
https://codecs.fedoraproject.org/openh264/39/x86_64/os/

The 2.4.1 RPM openh264-2.4.1-1.fc39.x86_64.rpm should already be available.

OK, seems I failed to check. This issue should be closed, then. Nothing left to do here, surely?

I suppose it could be closed. I am waiting to hear if there were any reported regressions.
@kalev Does everything look good?

I'm going to close this. If there are issues feel free to reopen this ticket or open a new one!

Metadata Update from @patrikp:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

23 days ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog