Comments
music
I think I will proceed by removing the PySide2 support just as I have done in F39 and F40/Rawhide. That configuration should be supportable for the remaining life of EPEL9.
Updated as described.
@tis, thanks for your feedback. I was aware that PySide2 is incompatible with Python 3.12, which is why qtsass’s PySide2 support is disabled in F39+. The package is still useful there for supporting Spyder and a couple of other packages that use QDarkStyleSheet with PyQt5.
I was not aware that PySide2 was about to be broken in EPEL9. That’s unpleasant, and I’m glad you told me!
I think I will proceed by removing the PySide2 support just as I have done in F39 and F40/Rawhide. That configuration should be supportable for the remaining life of EPEL9.
Still fixes FTBFS in python-Rtree due to Python 3.12 ctypes regression.
Since FEDORA-2023-4543b659d6 reached F39 stable first with a rebuilt fastnetmon for capnproto, I needed to rebuild fastnetmon again. Unfortunately, that means karma and time in testing for this update have been reset.
Fixes FTBFS in python-Rtree due to Python 3.12 ctypes regression.
I have waived the frr gating test failure, which appears to be due to an exit-code discrepancy (both nonzero) and almost certainly not caused by the update. Reported against the frr package at https://bugzilla.redhat.com/show_bug.cgi?id=2237860.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
I guess packaging an alpha of pylint 3 was the only way to get acceptable Python 3.12 support? It’s unfortunate that according to https://pylint.pycqa.org/en/latest/whatsnew/3/3.0/index.html there will be further breaking changes before 3.0.0 final, and they can be expected to break people’s configuration files.