Bug 2063526

Summary:	Rebase wayland-protocols to 1.24 or higher for KDE Plasma in EPEL
Product:	Red Hat Enterprise Linux 8	Reporter:	Neal Gompa <ngompa13>
Component:	wayland-protocols	Assignee:	Olivier Fourdan <ofourdan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	brandon.johnson, bstinson, carl, davdunc, davide, desktop-qa-list, jwboyer, michel, nate, ndegraef, ofourdan, tdawson
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2063523	Environment:
Last Closed:	2022-08-23 09:14:53 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 Neal Gompa 2022-03-13 12:02:11 UTC

+++ This bug was initially created as a clone of Bug #2063523 +++

Description of problem:
Starting with KDE Plasma 5.25, the minimum version of the wayland-protocols was raised to 1.25. Please update to at least wayland-protocols 1.25 so we can use it for KDE Plasma in EPEL.

Version-Release number of selected component (if applicable):
1.23-1.el8

Comment 1 Niels De Graef 2022-03-22 10:13:21 UTC

We're already well into the RHEL 8 cycle (BZs are now implicitly targeting 8.7) so new features are no longer really a priority at the moment. Even if we were still supporting KDE in RHEL, we'd still keep the version fixed (like we do with GNOME); this BZ is for KDE 5.25 which isn't even released yet, so that makes justification even harder.

Combine all that with the chance of introducing regressions to our customers and the limited capacity we have in our SST (both development & QE), I don't think it makes sense to take this (or bug 2063524) on.

If you plan on still building this newer version of KDE, you can still create an EPEL-specific branch of the needed dependencies (or even create a COPR).

Comment 2 Neal Gompa 2022-03-22 11:00:18 UTC

Do upgrading the wayland and wayland-protocols packages really cause regressions? That's never been my impression in seeing how these libraries have evolved in Fedora for the past several releases.

I've been filing these requests well in advance because I'm trying to align the KDE SIG's schedules, RHEL point release release schedules, and KDE Plasma schedules (https://community.kde.org/Schedules/Plasma_5). The KDE SIG tries to do one KDE Plasma upgrade a year, because we don't have the ability to maintain a single version forever.

We can't really do EPEL packages of this because EPEL does not allow overriding base packages. As it stands, we can't even upgrade to the current Plasma LTS (5.24) because wayland-protocols is at 1.23 instead of 1.24. If you aren't willing to upgrade to wayland-protocols-1.25 and wayland-1.20, can we at *least* just get wayland-protocols-1.24?

Comment 5 Niels De Graef 2022-08-23 09:14:53 UTC

This got fixed as part of bug 2094138, since mesa needed a newer wayland-protocols version.