!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

190 Members
54 Servers

Load older messages


SenderMessageTime
14 Nov 2025
@k900:0upti.meK900I think the proper fix is to basically build a "cross qt" properly, with targetPlatform08:36:24
@k900:0upti.meK900 Which is very cursed 08:36:30
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) the problem is, the canExecute check is different than whatever cmake checks to detect cross, and that mismatch causes issues 08:42:53
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)sure i could build it fully cross, but i don't see the reason to. If i can execute, then i can cheat and build that part as native08:43:31
18 Nov 2025
@jopejoe1:matrix.orgjopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 (4094@39c3).20:19:03
20 Nov 2025
@user12592851:matrix.orgJohn joined the room.06:25:27
21 Nov 2025
@k900:0upti.meK900The extra thicc menus are going back to normal: https://github.com/NixOS/nixpkgs/pull/46368808:52:11
@k900:0upti.meK900 @raboof tbh I really don't fuck with these reproducibility "fixes" 13:56:35
@k900:0upti.meK900It really feels like we're masking the real issue13:56:45
@k900:0upti.meK900And someone just needs to go and dig that up instead of trying to cover every Qt application with weird bandaids13:57:12
@raboof:matrix.orgraboofyeah I agree we should prioritize upstream fixes over nixpkgs bandaids. I did nudge upstream, but sometimes it's tempting to apply a local workaround when the upstream thing looks complicated :)15:50:55
@raboof:matrix.orgraboof(but the issues just disappeared from the qt jira?? - hope it's just part of their migration)15:52:37
@gradientvera:matrix.orgVera Gradient joined the room.21:20:05
@keenanw:matrix.orgkeenanw joined the room.22:25:11
23 Nov 2025
@sandro:supersandro.deSandro 🐧

K900 whats the reason behind this https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/qt-6/modules/qtbase/default.nix#L312 ?

This makes it so, that when you do lib.getDev on qt6.qtbase , you get an output where not really the expected dev headers are

02:07:05
@sandro:supersandro.deSandro 🐧Found that while finally finishing https://github.com/NixOS/nixpkgs/pull/33849803:01:58
@k900:0upti.meK900 Not really no 03:38:19
@k900:0upti.meK900 Should be possible to drop? 03:38:35
24 Nov 2025
@grimmauld:m.grimmauld.degrimmauld (any/all) joined the room.12:45:42
25 Nov 2025
@sandro:supersandro.deSandro 🐧We probably just need to find the workarounds added for that and drop them, too16:05:58
@sandro:supersandro.deSandro 🐧but I probably don't find the time right now to fix that ...16:06:06
@sandro:supersandro.deSandro 🐧btw can you take a look at the libreoffice PR? 16:06:14
@k900:0upti.meK900Should be doable now that branch-off is over16:06:22
@k900:0upti.meK900 It looks OK to me but I don't trust that thing 16:06:41
@k900:0upti.meK900And I don't want to abyss domain expert myself into it16:06:52
@sandro:supersandro.deSandro 🐧The person that originally implemented it, is not active right now 😅16:17:24
@sandro:supersandro.deSandro 🐧Before the symlinkJoin basically force combined the dev and libs into one derivativion and now they are separate and it removes a ton of dev things from a normal system16:18:13
26 Nov 2025
@marie:marie.cologneMariehttps://blogs.kde.org/2025/11/26/going-all-in-on-a-wayland-future/14:36:40
@k900:0upti.meK900Yay14:37:07
@k900:0upti.meK900The writing was very much on the wall tbh14:37:33

There are no newer messages yet.


Back to Room ListRoom Version: 9