Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Current KDE Plasma releases require Qt 5.15 (the last version of Qt5 and an LTS version). The Fedora KDE SIG would appreciate having Qt5 upgraded in RHEL 8.4 to 5.15.2 to unblock being able to upgrade Plasma in EPEL.
Qt5 releases offer very strong API and ABI backwards compatibility, so upgrading from Qt 5.12.5 to 5.15.2 should be quite safe.
Version-Release number of selected component (if applicable):
5.12.5-3.el8
I agree with Tom. Neal it's too late for anything this big for 8.4. We might see whether we will have time to do this in 8.5 or 8.6 and we will have a discussion about it inside our subsystem.
It would be appreciated to do it sooner rather than later, because Qt5 being so old is increasingly a problem for updating and maintaining Qt5 applications in EPEL.
I don't have any specific security issues on hand, but I figured that given the relatively low dependency web for Qt5 in RHEL outside of the Qt5 libraries themselves, I figured it'd be straightforward to upgrade.
If you *absolutely* cannot do it in 8.4, *please* do it ASAP for RHEL 8.5.
Hi Neal, during the yesterday's subsystem meeting, we have decided that Honza will do the rebase for 8.5. Honza, please do it early in the 8.5.0 development cycle, so QE has some extra time to verify it.
(In reply to Tomas Popela from comment #4)
> Hi Neal, during the yesterday's subsystem meeting, we have decided that
> Honza will do the rebase for 8.5. Honza, please do it early in the 8.5.0
> development cycle, so QE has some extra time to verify it.
Thank you!
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: qt5 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:4172