!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

202 Members
56 Servers

Load older messages


SenderMessageTime
18 May 2025
@k900:0upti.meK900Who knows12:17:10
@emilazy:matrix.orgemilyif it's "near the distribution information", I assume we are meant to put what we put in the NixOS licence file12:38:17
@outfoxxed:outfoxxed.meoutfoxxed K900 I've got non nixos users experiencing qml cache related crashes so it might just be an upstream thing 20:21:01
@k900:0upti.meK900Wew20:43:22
@k900:0upti.meK900Any idea if it's fixed in 6.9.120:43:27
@palasso:matrix.orgVassilis PalassopoulosI guess now that there is a 25.05 branch, all Plasma 5, frameworks 5, kde apps 5.x will be removed?23:07:13
@palasso:matrix.orgVassilis 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:0upti.meK900 Some frameworks will stay 05:46:40
@k900:0upti.meK900Plasma 5 and Qt5-based versions of Gear are going05:46:53
@k900:0upti.meK900Except the parts that have not been ported to Qt6 yet which is very few of them05:47:03
@grimmauld:grapevine.grimmauld.deGrimmauld (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:grapevine.grimmauld.deGrimmauld (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:0upti.meK900Generally we want to keep whatever default upstreams have 15:43:33
@k900:0upti.meK900e.g. Krita builds on Qt6 but we ship Qt5 because Qt6 has known issues15:43:50
@k900:0upti.meK900shiboken2 is whatever, we can probably drop pyqt5 after we drop Plasma 15:44:09
@k900:0upti.meK900I started chopping off Plasma but got lost in the migraine 15:45:07
@k900:0upti.meK900If anyone wants to start, be my guest 15:45:18
@emilazy:matrix.orgemilydo we have an update on the fate of Qt 5 WebEngine?15:45:28
@emilazy:matrix.orgemilyI'm worried about that.15:45:33
@k900:0upti.meK900Basically all of Plasma 5 can go, all of Gear as well except things marked broken in kdePackages15:45:49
@k900:0upti.meK900And then we prune the tree as far down as it'll go 15:45:58
@grimmauld:grapevine.grimmauld.deGrimmauld (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:0upti.meK900
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:0upti.meK900
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
@emilazy:matrix.orgemilyby who?15:46:36
@k900:0upti.meK900pyqt5 can exist, I don't think anything but plasma uses pyside515:46:42
@emilazy:matrix.orgemilythe Qt EOL is soon, right?15:46:42
@k900:0upti.meK900
In reply to @emilazy:matrix.org
by who?
Qt
15:46:45
@emilazy:matrix.orgemilyhttps://www.qt.io/blog/extended-security-maintenance-for-qt-5.15-begins-may-2025 ok cool15:47:10
@emilazy:matrix.orgemilywait no15:47:19

Show newer messages


Back to Room ListRoom Version: 9