!UNVBThoJtlIiVwiDjU:nixos.org

Staging

348 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/115 Servers

Load older messages


SenderMessageTime
19 Feb 2026
@emilazy:matrix.orgemily right now every channel setup will try to rebuild the world once -next merges 🫠 15:53:44
@vcunat:matrix.orgVladimír Čunát* We also have some broken NixOS tests, even -small channel blockers.15:53:51
@emilazy:matrix.orgemilyare those the installer tests?15:53:59
@emilazy:matrix.orgemilybecause this would also plausibly break those15:54:02
@emilazy:matrix.orgemilybecause how you get your Nixpkgs becomes a cache buster15:54:10
@vcunat:matrix.orgVladimír ČunátOh right, maybe this PR will fix them.15:54:17
@vcunat:matrix.orgVladimír ČunátMakes sense.15:54:21
@emilazy:matrix.orgemily I'm not sure if lib.trivial.version even matches between the -next and master Hydra jobs, so there's a funny scenario where we still get a world rebuild on master… 15:55:21
@emilazy:matrix.orgemily * I'm not sure if lib.trivial.version even matches between the -next and master Hydra jobsets, so there's a funny scenario where we still get a world rebuild on master… 15:55:31
@emilazy:matrix.orgemily (but worst case we can just hardcode "26.11pre-git" for now) 15:55:33
@vcunat:matrix.orgVladimír Čunát It fixed nixosTests.containers-imperative apparently. 16:03:48
@vcunat:matrix.orgVladimír ČunátSo maybe it's all fine now.16:03:55
@vcunat:matrix.orgVladimír Čunát(I've fixed rsyslog build in the meantime.)16:04:04
@vcunat:matrix.orgVladimír Čunát* So maybe it's all fine now, at least after we merge that PR.16:04:35
@k900:0upti.meK900FYI: https://github.com/NixOS/nixpkgs/pull/49215716:16:37
@k900:0upti.meK900Will merge once I'm sure it's 0 rebuilds16:16:48
@k900:0upti.meK900Also libphonenumber is busted with boost 1.8916:19:00
@k900:0upti.meK900But 1.88 works16:19:02
@k900:0upti.meK900Will pin unless anyone wants to dig into it16:19:07
@emilazy:matrix.orgemily is there actually a formal distinction between dynamic attributes in rec and any use of with, btw? (not that I wouldn't be happy to see both rec and with purged from the language) 16:22:28
@k900:0upti.meK900Formal, no16:23:22
@k900:0upti.meK900 But it gets REALLY funny with rec 16:23:32
@emilazy:matrix.orgemily rec { ${if cond then "ambiguous" else null} = …; test = ambiguous; }.test seems indistinguishable from with { ${if cond then "ambiguous" else null} = … }; ambiguous 16:23:43
@emilazy:matrix.orgemily hmm, except the former always complains about ambiguous not being bound 16:26:17
@emilazy:matrix.orgemily which, yeah exposes ${"ambiguous"} being treated specially 16:26:34
@emilazy:matrix.orgemily since rec { ${"ambiguous"} = 123; test = ambiguous; }.test does work 16:26:56
@k900:0upti.meK900 Yes, try ${"a" + "mbiguous"} 16:27:10
@emilazy:matrix.orgemily arguably rec with conditional attributes should let you refer to them and just turn off scope checking like with does 🙃 16:27:15
@k900:0upti.meK900To bypass that optimization16:27:14
@emilazy:matrix.orgemily right, in which case it just complains that ambiguous is unbound 16:28:15

Show newer messages


Back to Room ListRoom Version: 6