| 18 May 2025 |
Vassilis Palassopoulos | * I guess now that there is a 25.05 branch, all Plasma 5, frameworks 5, kde gear apps 5.x will be removed? | 23:09:21 |
| 19 May 2025 |
K900 | Some frameworks will stay | 05:46:40 |
K900 | Plasma 5 and Qt5-based versions of Gear are going | 05:46:53 |
K900 | Except the parts that have not been ported to Qt6 yet which is very few of them | 05:47:03 |
Grimmauld (any/all) | https://github.com/NixOS/nixpkgs/pull/407932 | python313Packages.shiboken2: mark broken https://github.com/NixOS/nixpkgs/issues/408671 | Some KDE applications are duplicated and use unmaintained/partially broken libsForQt5
When do we start dropping qt5 (or at least set qt6 default) on packages like this that have overrides to select qt version?
| 15:41:02 |
Grimmauld (any/all) | *
- https://github.com/NixOS/nixpkgs/pull/407932 | python313Packages.shiboken2: mark broken
- https://github.com/NixOS/nixpkgs/issues/408671 | Some KDE applications are duplicated and use unmaintained/partially broken libsForQt5
- plans to update default python to 3.13 in 25.11 (now the coming unstable)
- some packages having qt5 and qt6 support
When do we start dropping qt5 (or at least set qt6 default) on packages like this that have overrides to select qt version?
| 15:41:24 |
K900 | Generally we want to keep whatever default upstreams have | 15:43:33 |
K900 | e.g. Krita builds on Qt6 but we ship Qt5 because Qt6 has known issues | 15:43:50 |
K900 | shiboken2 is whatever, we can probably drop pyqt5 after we drop Plasma | 15:44:09 |
K900 | I started chopping off Plasma but got lost in the migraine | 15:45:07 |
K900 | If anyone wants to start, be my guest | 15:45:18 |
emily | do we have an update on the fate of Qt 5 WebEngine? | 15:45:28 |
emily | I'm worried about that. | 15:45:33 |
K900 | Basically all of Plasma 5 can go, all of Gear as well except things marked broken in kdePackages | 15:45:49 |
K900 | And then we prune the tree as far down as it'll go | 15:45:58 |
Grimmauld (any/all) | dropping pyqt5 affects some packages i genuinely care about. Notably, freecad (can be bumped to just use qt6 instead) and opensnitch-ui (i am listed maintainer and that didn't port yet...) | 15:45:59 |
K900 | In reply to @emilazy:matrix.org do we have an update on the fate of Qt 5 WebEngine? It's being maintained for the time being | 15:46:10 |
K900 | In reply to @grimmauld:grapevine.grimmauld.de dropping pyqt5 affects some packages i genuinely care about. Notably, freecad (can be bumped to just use qt6 instead) and opensnitch-ui (i am listed maintainer and that didn't port yet...) *pyside5 | 15:46:24 |
emily | by who? | 15:46:36 |
K900 | pyqt5 can exist, I don't think anything but plasma uses pyside5 | 15:46:42 |
emily | the Qt EOL is soon, right? | 15:46:42 |
K900 | In reply to @emilazy:matrix.org by who? Qt | 15:46:45 |
emily | https://www.qt.io/blog/extended-security-maintenance-for-qt-5.15-begins-may-2025 ok cool | 15:47:10 |
emily | wait no | 15:47:19 |
emily | that's commercial-only? | 15:47:21 |
emily | it looks to me like we have 7 days. | 15:47:32 |
emily | (and that's not an old post, it's from a couple months ago) | 15:47:57 |
K900 | It seems they will keep publishing patches for qtwebengine at least | 15:48:09 |
emily | do you have a source for that? 😅 | 15:48:23 |
K900 | Somewhere on the mailing lists | 15:49:04 |