Bug 2144557
| Summary: | Rebase GStreamer stack to 1.22.1 or higher for RHEL 9.3 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Neal Gompa <ngompa13> |
| Component: | gstreamer1 | Assignee: | Wim Taymans <wtaymans> |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Prajzner <jprajzne> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | CentOS Stream | CC: | brandon.johnson, bstinson, carl, cschalle, davide, jprajzne, jwboyer, klember, michel, mkielian, ndegraef, riehecky, sbarcomb, tdawson, tpelka, wtaymans |
| Target Milestone: | rc | Keywords: | Rebase, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gstreamer1-1.22.1-2.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-07 08:31:50 UTC | Type: | Component Upgrade |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1956874, 2053295, 2179288 | ||
|
Description
Neal Gompa
2022-11-21 16:06:34 UTC
Looking at the upstream tracker for the schedule, it's currently targeting 22 December (https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/974) which means we can have a DTM of 17 or later only, so unsetting the current one. Wim, since 9.2 is an LTS release I wonder if it would make sense to target 22.2.1 instead so we've gotten an initial batch of bugfixes? That would probably also mean targeting 9.3, which might then also be a better fit for QE (although that is up to tpelka to decide) > Wim, since 9.2 is an LTS release I wonder if it would make sense to target 22.2.1 instead so we've gotten an initial batch of bugfixes? That would probably also mean targeting 9.3, which might then also be a better fit for QE (although that is up to tpelka to decide)
Fine for me and 1.22 might also be delayed, we don't know yet.
I should also elaborate that this is part of a push I'm working on to build up the multimedia capabilities of RHEL/CentOS for creative professionals to use. And RHEL 9.2 is likely the first release to see some serious adoption on that front, so it'd be nice to have it all there. GStreamer 1.22rc1 (1.21.90) released last night: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/a9ec35b1ca3193820f434fd17a71207cde19de2b Tarballs are available now. It looks like the aim is to have GStreamer 1.22.0 released by the end of this month. That would put 1.22.1 probably in early February, which should fit in the development window for RHEL 9.2. GStreamer 1.22.0 just released: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/f13c65d977b740b5955343d320dcf2061bbdf62d Having this up to date would greatly simplify my life for integration purposes. Since we're moving to RHEL 9.3 for this, could we look at GStreamer 1.24? It's supposed to arrive in June/July, which gives plenty of time to integrate it and we can also get much fuller support for AV1 (VA-API support for AV1 in GStreamer is supposed to land in 1.24). VA-API support for AV1 in GStreamer would make my life easier! If 1.24 is not too late it can be done. Hi Neal & Pat, I suggest we start with a rebase to GStreamer 1.22.1 first and to file a separate request for 1.24 later. We can't possibly commit to backporting that version until we have an actual release upstream (and ideally a .1 release to make sure we get an initial batch of bugfixes). Depending on the timing of that release, it could of course mean it gets targeted to a later RHEL 9 version, but that's fine. Worst case, if we were to try to backport GStreamer 1.24 and it has issues, we'll have no rebase of GStreamer *at all* anytime soon. That's very fair. I just worry about asking too much given how difficult this stuff has been... But yes, a GStreamer upgrade to 1.22.x is better than nothing. (In reply to Neal Gompa from comment #19) > That's very fair. I just worry about asking too much given how difficult > this stuff has been... I understand it's not easy. From my point of view, some tips I can give: * It's good to make requests early, but we can't really make any promises about anything that hasn't been released yet even upstream * Similarly, versions that haven't gone through any upstream testing (including our upstream Fedora) are less inclined to be taken in (hence why I'd like to wait for example for a .1 release) * We try to help the CentOS Stream community when we can, but CentOS Stream != RHEL. If you're targeting a use case that is important to RHEL or its customers, please make sure to write that in the BZ as that can help teams prioritize (of course, making a case why something is important for CentOS Stream can also make a difference still) * Any change within a major version of RHEL needs to be backported and validated by teams within Red Hat (unless they exceptionally agree on the contrary) which is a different model than distros like Fedora. It also means that any change needs to compete with other (possibly internal) requests/bug fixes/etc for resources, which makes that certain changes -even though they might completely make sense externally- still might not be taken in Shouldn't the various gstreamer1-* packages also be updated, or do I need to file BZes for each individual one to get that to happen too? > Shouldn't the various gstreamer1-* packages also be updated, or do I need to file BZes for each individual one to get that to happen too?
They should be updated, you don't need to file individual bz for those.
The problem is that I can't build them until the main gstreamer package is in the buildroot and I don't know how to build packages for rhel in their own buildroot, so my current plan is to wait until they pass gating...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (gstreamer1 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:6411 |