!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

204 Members
57 Servers

Load older messages


SenderMessageTime
12 Dec 2025
@aktaboot:tchncs.deaktaboot (nvidia, 🖕 u)yeah I'll see when everything hits nixos-unstable!12:07:10
@k900:0upti.meK900Ughhhhh12:07:28
@k900:0upti.meK900I think this is that one thing12:07:31
@k900:0upti.meK900That's in staging12:07:48
@aktaboot:tchncs.deaktaboot (nvidia, 🖕 u)you mean fixed in upstream staging?12:08:12
@k900:0upti.meK900Fixed in Qt 6.10.2 and cherry-picked to our staging12:09:13
@k900:0upti.meK900Either give it like two weeks12:09:33
@k900:0upti.meK900Or try https://github.com/NixOS/nixpkgs/commit/8ae30516b638d364cbc121fe307e841a9f22f73712:09:35
@k900:0upti.meK900(it'll be a kitchen sink rebuild though)12:09:42
@aktaboot:tchncs.deaktaboot (nvidia, 🖕 u)and i'd preferrably set all my system to that branch for testing right12:10:56
@k900:0upti.meK900Well12:11:25
@k900:0upti.meK900You can overlay qtdeclarative with just that patch12:11:30
@k900:0upti.meK900It'll be fine12:11:33
@k900:0upti.meK900But you'd still have to rebuild all of Qt basically12:11:49
@k900:0upti.meK900Including qtwebengine which is a chromium12:11:54
@aktaboot:tchncs.deaktaboot (nvidia, 🖕 u)okay might not try that then :>12:12:10
@aktaboot:tchncs.deaktaboot (nvidia, 🖕 u)two weeks is fine12:12:37
@k900:0upti.meK900Yeah I think this is going to be like12:12:40
@k900:0upti.meK900Double digit hours on reasonable hardware12:12:49
@k900:0upti.meK900Or like 3-4 hours of Big Computer12:13:10
@aktaboot:tchncs.deaktaboot (nvidia, 🖕 u)and triple digits on a laptop :D12:13:27
@k900:0upti.meK900Nah12:13:34
@k900:0upti.meK900Definitely not that bad12:13:38
@aktaboot:tchncs.deaktaboot (nvidia, 🖕 u)yeah im jokin12:13:40
@k900:0upti.meK900qtwebengine is like a 6 hour build on a normal Hydra build slot and those are both tiny and overcommitted to hell12:14:05
@k900:0upti.meK900 @raboof so wait does this mean there's no inherent issue 12:23:42
@k900:0upti.meK900And it's just a link order thing12:23:45
@raboof:matrix.orgraboofno it's not just link ordering: when dependencies are not explicit, cmake will kick off the qml code generation for the 'dependent' before processing the 'dependee' has finished, causing it to nondeterministically miss generating code that should come in via the 'dependee'. I'm not sure why that doesn't seem to cause more actually-observed issues, though.12:27:36
@k900:0upti.meK900Wew12:27:48
@k900:0upti.meK900So it is ordering12:27:52

Show newer messages


Back to Room ListRoom Version: 9