Bug 1937416

Summary: Rebase WebKitGTK to 2.32
Product: Red Hat Enterprise Linux 8 Reporter: Michael Catanzaro <mcatanza>
Component: webkit2gtk3Assignee: Michael Catanzaro <mcatanza>
Status: CLOSED ERRATA QA Contact: Michal Odehnal <modehnal>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.5CC: erack, tpelka, tpopela
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: webkit2gtk3-2.32.3-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 19:34:12 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:

Description Michael Catanzaro 2021-03-10 15:48:32 UTC
Let's rebase to WebKitGTK 2.32. My proposal is to do a two-step rebase, like we did for 8.3 and 8.4. But because builds now have to be Verified:Tested before being added to errata, I will not build the latest stable version as it's released anymore. Instead, I'll do one early rebase to 2.32.0, and then a second build during or before ITM 21 with whatever 2.32.z is the latest version at that time. The first build is considered a risky rebase that should be completed prior to ITM 17, but I'll do it long before that. (2.32.0 should be released in less than two weeks, and I see no reason to wait.) The second build is not considered a risky rebase, allowing us to rebase a second time after ITM 17.

Comment 8 Michal Odehnal 2021-07-19 09:49:10 UTC
Executed all automated tests with full pass as a result. Switching to Verified:Tested. And from ON_QA to VERIFIED.

Comment 9 Michael Catanzaro 2021-07-23 15:43:19 UTC
Back to MODIFIED for 2.32.3.

Comment 10 Michal Odehnal 2021-07-27 14:06:07 UTC
Automation executed with full pass as a result.

Comment 13 errata-xmlrpc 2021-11-09 19:34:12 UTC
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 (Moderate: GNOME security, 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/RHSA-2021:4381