Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2132723 - Update ffmpeg for openh264 2.3.1 soname bump
Summary: Update ffmpeg for openh264 2.3.1 soname bump
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ffmpeg
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard: AcceptedFreezeException
Depends On: 2129380
Blocks: F37FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2022-10-06 13:20 UTC by Kalev Lember
Modified: 2022-10-14 12:59 UTC (History)
5 users (show)

Fixed In Version: ffmpeg-5.1.2-1.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-13 11:44:51 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Kalev Lember 2022-10-06 13:20:41 UTC 
I am filing this ticket for Fedora 37 freeze exception paperwork.

openh264 (in external fedora-cisco-openh264.repo) is getting updated from 2.3.0 to 2.3.1, with the only change being a soname bump that was missed in 2.3.0 (there was a silent ABI change in 2.3.0 and the soname bump is necessary to fix it in a correct way). It would be good to update ffmpeg in F37 in lock step so that the openh264 soname bump doesn't break ffmpeg.

See https://pagure.io/releng/issue/11059 for releng work to get openh264 updated.
Comment 1 Maxwell G 2022-10-06 20:46:55 UTC 
Why is openh264 being updated during freeze in the first place?
Comment 2 Neal Gompa 2022-10-07 08:39:43 UTC 
(In reply to Maxwell G from comment #1)
> Why is openh264 being updated during freeze in the first place?

Because OpenH264 2.3.0 had an ABI break without the soname bumped. 2.3.1 fixes the soname issue so that dlopening stops being broken.
Comment 3 František Zatloukal 2022-10-09 15:27:36 UTC 
Discussed in ticket: https://pagure.io/fedora-qa/blocker-review/issue/958

The decision to classify this bug as an FreezeException was made.
Comment 4 Fedora Update System 2022-10-12 15:47:23 UTC 
FEDORA-2022-ccb4d848fc has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ccb4d848fc
Comment 5 Fedora Update System 2022-10-12 15:47:23 UTC 
FEDORA-2022-be305c9c65 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-be305c9c65
Comment 6 Fedora Update System 2022-10-12 16:24:08 UTC 
FEDORA-2022-ccb4d848fc has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ccb4d848fc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ccb4d848fc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2022-10-12 18:15:35 UTC 
FEDORA-2022-be305c9c65 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-be305c9c65`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-be305c9c65

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2022-10-13 11:44:51 UTC 
FEDORA-2022-ccb4d848fc has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 9 Fedora Update System 2022-10-14 12:59:21 UTC 
FEDORA-2022-be305c9c65 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.