Per KDE upstream and agreement in the KDE SIG meeting today, we need to sync Plasma 5.24.1 and KF5 5.91 to all Fedora and EPEL branches.
This is a high priority item: @marcdeop will release it for F34 and F35, and @tdawson will pick those up for EPEL 8 and EPEL 9.
Metadata Update from @ngompa: - Issue tagged with: experience, need-work
F35 was done already and I just submitted an update for F34: https://bodhi.fedoraproject.org/updates/FEDORA-2022-267b54e22b
I have started the epel9 build (pulling from f35). I plan on starting epel8-next later today (pulling from f34). Both are pulling in plasma 5.24.2 and kf5 5.91
For epel8 I plan on building everything on epel8-next first and then rebuild on epel8 when RHEL 8.6 is released. This will allow me to fix any problems (going from 5.22 -> 5.24 there are a few new package and dependency changes). This will also be less of a surprise for end users having a kde update at the same time as the rest of the operating system.
@tdawson do you want me to upgrade first f35 and f34 to Plasma 5.24.3?
I think doing the 5.24.3 update would be a great idea, if you feel it is ready.
Yes, it is. I will start shortly
Due to the older wayland-protocols in RHEL 8 and 9 I am unable to do this update.
kwayland-server requires the newer wayland-protocols. No bypassing allowed, it really wants them. I tried to workaround this by using kwayland-server-5.23.5, and tweaking dependencies on other packages. But it seems that kwin wants functions from the newer kwayland-server, that needs settings in the newer wayland-protocols.
The newer wayland-protocols will not be available until RHEL 8.7 and 9.1.
On a good note, that means that we are on schedule for the epel once a year update, that was scheduled for RHEL 8.7 and 9.1.
Metadata Update from @siosm: - Issue tagged with: packaging
Metadata Update from @siosm: - Issue untagged with: packaging - Issue tagged with: updates
This was done a while ago...
Metadata Update from @ngompa: - Issue set to the milestone: None (was: Plasma 5.24)
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Login to comment on this ticket.