| 18 May 2025 |
 Marie | * I don't think it's that easy, since we are not only distributing MIT software | 12:11:52 |
 K900 | Nixpkgs itself is MIT | 12:16:58 |
| K900 | But what is the license of your exact NixOS config as installed | 12:17:08 |
| K900 | Who knows | 12:17:10 |
 emily | if it's "near the distribution information", I assume we are meant to put what we put in the NixOS licence file | 12:38:17 |
 outfoxxed | K900 I've got non nixos users experiencing qml cache related crashes so it might just be an upstream thing | 20:21:01 |
| K900 | Wew | 20:43:22 |
| K900 | Any idea if it's fixed in 6.9.1 | 20:43:27 |
 Vassilis Palassopoulos | I guess now that there is a 25.05 branch, all Plasma 5, frameworks 5, kde apps 5.x will be removed? | 23:07:13 |
| 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 |
