!UNVBThoJtlIiVwiDjU:nixos.org

Staging

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

Load older messages


SenderMessageTime
30 Jun 2026
@k900:0upti.meK900Because we will reattempt all failed builds before the end of the cycle11:08:29
@csanthiago:matrix.orgcSanthiagogot it11:15:50
@emilazy:matrix.orgemilyI know what's up with the Darwin linking issues12:07:35
@emilazy:matrix.orgemilycan try to submit a PR later today but if anyone wants to beat me to it they can copy https://github.com/NixOS/nixpkgs/pull/53636312:08:23
@emilazy:matrix.orgemilymight be a little whack a mole until next cycle unfortunately, sorry for the overzealous cleanup12:08:48
@sempiternal-aurora:matrix.orgMyriaI'm just testing pango and tk rn12:21:11
@k900:0upti.meK900In case anyone is wondering, the paperless bisect is still going on iteration 113:10:12
@k900:0upti.meK900I've built a Rust and now I need to build an X server13:10:29
@k900:0upti.meK900At least it doesn't seem to have browser engines in the closure?13:10:42
@juliusfreudenberger:jfreudenberger.dejuliusfreudenbergerI can imagine Rust, but an X Server?!13:11:58
@k900:0upti.meK900Something something xvfb tests13:12:11
@flashonfire:lithium.ovhguillaume i should have let mine going then, it was way faster ahaha 13:39:30
@flashonfire:lithium.ovhguillaume* i should have let mine runnng then, it was way faster ahaha13:41:34
@flashonfire:lithium.ovhguillaume* i should have let mine running then, it was way faster ahaha13:41:42
@flashonfire:lithium.ovhguillaume* i should have let mine running then, it seemed to be way faster ahaha13:45:16
@flashonfire:lithium.ovhguillaume* oh i should have let mine running then, it seemed to be faster14:01:51
@k900:0upti.meK900Welp14:38:24
@k900:0upti.meK900Another similarly sized build incoming14:38:30
@elvishjerricco:matrix.orgElvishJerricco Why is this bad? What does bootctl have to do if we don't think we need an update? And why would using varlink fix things? 15:09:57
@k900:0upti.meK900 Because bootctl already has a code path for "update only if necessary" 15:10:20
@k900:0upti.meK900 And that's something it knows how to do better than us 15:10:32
@elvishjerricco:matrix.orgElvishJerriccoright but it exits with failure if that happens15:10:38
@k900:0upti.meK900 And varlink is seemingly the only way for an outside observer to differentiate "failed to do a thing" and "didn't need to do anything" 15:10:56
@elvishjerricco:matrix.orgElvishJerriccoooooh I see15:11:10
@k900:0upti.meK900 Because via varlink it returns the right exit code for the latter 15:11:13
@elvishjerricco:matrix.orgElvishJerricco I was just going to patch systemd to add a bootctl check command 15:11:34
@k900:0upti.meK900 Unfortunately, it only works when there is a varlink 15:11:38
@elvishjerricco:matrix.orgElvishJerriccobecause that should exist15:11:41
@k900:0upti.meK900
In reply to @elvishjerricco:matrix.org
I was just going to patch systemd to add a bootctl check command
You can patch it to instead return a better exit code
15:11:49
@k900:0upti.meK900 For update 15:11:51

Show newer messages


Back to Room ListRoom Version: 6