!UNVBThoJtlIiVwiDjU:nixos.org

Staging

316 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
7 Oct 2025
@k900:0upti.meK900I have Qt 6.10 very soon15:30:51
@k900:0upti.meK900I HOPE15:30:55
@k900:0upti.meK900And then Vulkan SDK15:30:58
@k900:0upti.meK900Python is stdenv rebuild on Darwin15:31:32
@k900:0upti.meK900So we need to do that fast15:31:37
@willi:butz.cloudWilli Butz anyone else saw the audit build failure (tests fail)? don't see open issues about that 15:32:09
@willi:butz.cloudWilli Butz (on staging-next) nix build github:nixos/nixpkgs/pull/449539/head#audit 15:32:33
@hexa:lossy.networkhexaok, will send it into staging-next15:32:51
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)will look, i am maintainer XD15:33:37
@willi:butz.cloudWilli Butznice. no idea what to make of the errors. something something shadow memory range15:34:19
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)wut15:34:28
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)you have a log? I don't have deps cached15:34:58
@willi:butz.cloudWilli Butz1sec15:35:17
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i did build audit a few days ago (while building towards the new systemd 258), and it wasn't broken then15:35:34
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)if audit is broken now, it'll block a whole bunch of stuff15:36:13
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) but so far audit has been very lenient about its builds, not such a diva as xml stuff... So i am a bit surprised 15:36:39
@k900:0upti.meK900istg pyside15:38:07
@k900:0upti.meK900I'm gonna do a violence15:38:23
@willi:butz.cloudWilli Butzhttps://gist.github.com/WilliButz/afd8ca68c45c5e6a96216f6b92658d2315:38:29
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)HUH15:38:47
@k900:0upti.meK900o7 asan15:38:54
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)nikstur ran into that too, but after disabling parallel checking it went away for him15:39:24
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i hate asan15:39:27
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)the best part: i can't repro that one on my machine15:39:57
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)like, at all15:40:00
@vcunat:matrix.orgVladimír Čunátasan has interactions with PIE, or why the regression?15:40:05
@vcunat:matrix.orgVladimír ČunátThough the log suggest that kernel is to blame 🤯15:41:21
@aloisw:julia0815.dealoisw PIE was already in the last staging-next, right? 15:41:31
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)yep15:41:41
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) tbh if asan+pie causes trouble depending on host kernel, i'd vote to just skip that check 15:42:04

Show newer messages


Back to Room ListRoom Version: 6