!UNVBThoJtlIiVwiDjU:nixos.org

Staging

312 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.05 | Review Reports: https://malob.github.io/nix-review-tools-reports/108 Servers

Load older messages


SenderMessageTime
21 Oct 2025
@k900:0upti.meK900 @SomeoneSerge (back on matrix) any ideas what THIS is 08:15:24
@wolfgangwalther:matrix.orgWolfgang WaltherWill fix this.08:16:02
@vcunat:matrix.orgVladimír ČunátIt reads OK in English, but I fail to see the point of such code.08:16:45
@k900:0upti.meK900 This makes no sense because qt6.full is just a buildEnv with all of those modules 08:17:04
@k900:0upti.meK900(and should be deleted the fuck out of nixpkgs, which I'm going to do, like, now)08:17:13
@vcunat:matrix.orgVladimír ČunátThe left sides should always exist, too (I expect).08:17:34
@k900:0upti.meK900Yes08:17:59
@k900:0upti.meK900 @Wolfgang Walther beat you to it :P 08:27:00
@k900:0upti.meK900Also I'm pretty sure the webkit thing is ALSO a red herring08:27:25
@k900:0upti.meK900Because the webkit being pulled in is qtwebkit via qt5.full which they should not have used ANYWAY08:27:40
@k900:0upti.meK900But when I gave it qtbase it failed with a haskell type error anyway08:28:09
@k900:0upti.meK900So I'm going to just call it broken and move on08:28:18
@k900:0upti.meK900 @Wolfgang Walther sniped again 10:24:36
@k900:0upti.meK900I'll wait for the CUDA people to weigh in10:24:44
@wolfgangwalther:matrix.orgWolfgang Walther:)10:25:03
@k900:0upti.meK900I bet they have some custom overlay or something that relies on this cursed behavior10:25:20
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)the bad webkitgtk was properly removed a few days ago, qt5 webkit needs to follow soon :P10:26:49
@k900:0upti.meK900qt5webkit has been marked insecure for ages now10:27:03
@k900:0upti.meK900It's probably yeetable tbh10:27:07
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)webkitgtk was marked insecure too due to libsoup210:27:23
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)* webkitgtk_4_0 was marked insecure too due to libsoup210:27:33
@k900:0upti.meK900Honestly if you want to yeet it be my guest10:27:51
@k900:0upti.meK900I'm not sure we want to yeet qtwebengine5 yet but qtwebkit can go10:28:05
@k900:0upti.meK900 Actually never mind it doesn't even rebuild those 10:46:17
@k900:0upti.meK900I'll just merge and let CUDA people scream at me later if they want10:46:25
@hexa:lossy.networkhexawas removed in https://github.com/NixOS/nixpkgs/pull/45006511:43:29
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i know, i approved that PR and would have merged that same day if jan didn't self-merge faster11:44:06
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)* i know, i approved that PR and would have merged that same day if jan hadn't self-merged11:44:19
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)my point was, both was marked insecure, qtwebkit even for longer, so we should also remove both11:45:16
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)with the webkitgtk_4_0 the argument was backports of newer webkitgtk ABI during the 25.11 release cycle, but for qtwebkit there isn't any updates at all anymore. So it needs to go.11:46:07

Show newer messages


Back to Room ListRoom Version: 6