[CentOS-devel] CentOS Stream 8 and 9 - KDE un-updateable for a week

Wed May 11 15:16:10 UTC 2022
Troy Dawson <tdawson at redhat.com>

On Wed, May 4, 2022 at 8:01 AM Troy Dawson <tdawson at redhat.com> wrote:

>
> On Wed, Apr 27, 2022 at 9:31 AM Troy Dawson <tdawson at redhat.com> wrote:
>
>> During the past week qt5 was updated on CentOS Stream 8 and 9 to version
>> 5.15.3.  This caused updates to break for KDE users running CentOS Stream 8
>> and 9.  The epel 8 and 9 packages affected are being rebuilt at this time.
>> We expect everything rebuilt and through testing next week.
>>
>> Question: Does this affect my RHEL/Alma/Rocky 8/9 install?
>> Answer: Not at this time.  This qt5 update isn't going to be released
>> until RHEL 8.7 and 9.1.
>>
>> Question: What is being rebuilt?
>> Answer:
>> epel8 - We believe about 30 packages.  That includes all of the qt5
>> packages in epel8, as well as several plasma and kf5 packages that have
>> tight version dependencies on qt5.
>>
>> epel9 - The entire KDE Plasma Desktop stack. (about 380 packages).  There
>> recently has been an update to wayland-protocols in Stream 9.  It didn't
>> break anything, but it had been an update that was needed to update to the
>> latest kf5 and plasma releases.  Since we knew that the qt5 update was
>> coming, we held off rebuilding everything until qt5 came out.  Now that it
>> is out, we are updating everything.
>>
>> Troy Dawson
>>
>
> Latest update on this.
>
> EPEL9 - Everything is in epel-next-testing.  To do your update do
>   dnf --enablerepo=epel-next-testing update
>
> Reminder, this is a complete KDE Plasma Desktop update to plasma 5.24.4,
> kf5 5.93, qt5 5.15.3
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-a6c0f04770
>
> EPEL8 - Some packages are rebuilt and available, but qt5-qtwebengine, and
> everything that depends on it, has not been rebuilt.
> This is due to a complex module bug in CentOS Stream 8 affecting the
> epel8-next buildroot.  It may, or may not, get fixed this week.
>
> Thank you all for your patience.
> Troy
>

Latest update (May 11)

EPEL9 on CentOS Stream 9 (epel9-next)
The complete KDE Plasma Desktop update is now in stable and on the mirrors.
There are two bugs found and the fixes are in testing.
- selinux and plasma-workspace.
-- This only affects a new install of KDE Plasma Desktop, it doesn't affect
updates.  You will know when you hit this.  Lot's of pop-up screens telling
you of this bug.
-- https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-9984d71297
--- Give it some karma so we don't have to wait a week.
- kf5-kapidox does not install
-- https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-88f6f718b8

Note: again, a reminder, RHEL 9.0 will have the slightly older KDE Plasma
Desktop.  This *updated* KDE Plasma Desktop will not be available for RHEL
9.0 GA, it will be available for RHEL 9.1.

EPEL8 on CentOS Stream 8 (epel8-next)
We have rebuilt as many packages as we can.  We still cannot build
qt5-qtwebengine, and thus any packages that depend on it.
- qt5-qtwebengine
-- The python27 module has been fixed, and you can now build packages that
require python2 on epel8-next.
-- qt5-qtwebengine builds fine on x86_64, but failed on aarch64
--- Any help would be appreciated.
--- https://kojipkgs.fedoraproject.org//work/tasks/6819/86886819/build.log
--- We tried rebuilding the older qt5-qtwebengine, same errors.
--- We tried the older gcc, again, same errors.
--- Still working on it, but if you recognize the errors in the buildlog,
let us (me) know.
- sddm and kscreenlocker not working.
-- We have found that it is indeed a RHEL 8 kernel issue.
-- https://bugzilla.redhat.com/show_bug.cgi?id=2043771
-- kernel issues take a while to make it through RHEL.  So if anyone finds
any type of workarounds.  Let us know.
--- sddm workaround
---- dnf install gdm ; systemctl enable gdm -f
--- kscreenlocker workaround - unknown

Again, thank you for your patience and words of encouragement.
Troy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20220511/63213acd/attachment-0003.html>