!UNVBThoJtlIiVwiDjU:nixos.org

Staging

354 Members
Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen115 Servers

Load older messages


SenderMessageTime
19 Feb 2026
@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
@emilazy:matrix.orgemily so yeah, rec is weird in a way that with isn't 16:28:26
@emilazy:matrix.orgemily well, or with is weird in a different way at least 16:28:33
@emilazy:matrix.orgemily

"we have rec at home":

nix-repl> let self = with self; { ${if true then "ambiguous" else null} = 123; test = ambiguous; }; in self.test
123
16:28:49
@k900:0upti.meK900 Pinned 16:35:23
@mana-byte:matrix.orgmana-byte changed their display name from Manaiki to mana-byte.16:36:27
@tom:pub.solartomlate to the party but there's https://github.com/google/libphonenumber/pull/3903, should we vendor that instead? happy to make a PR17:50:00
@tom:pub.solartom set a profile picture.20:44:23
20 Feb 2026
@sandro:supersandro.deSandroyep, unmerged PRs should be vendored02:29:55
@tom:pub.solartom yup, I'm aware of that. My question was: Should we vendor that patch instead of pinning boost? 07:11:43
@qyliss:fairydust.spaceAlyssa Rosssounds more friendly to cleanup. patches will be noticed when upgrading to a version that in includes it, but pins are rarely cleaned up08:46:50
@qyliss:fairydust.spaceAlyssa Rossas long as you're confident in the patch08:47:04
@tom:pub.solartomyeah, the patch is pretty straightforward and what boost recommends in their 1.89 release notes → opened https://github.com/NixOS/nixpkgs/pull/49241309:41:06
21 Feb 2026
@vcunat:matrix.orgVladimír Čunát I think of merging staging-next within hours. 07:00:17
@k900:0upti.meK900Are we out of blockers then?08:24:17
@vcunat:matrix.orgVladimír Čunát-small is green now: https://hydra.nixos.org/eval/182305208:31:52
@vcunat:matrix.orgVladimír Čunát mariadb.x86_64-darwin would block nixpkgs-unstable though 08:32:13
@vcunat:matrix.orgVladimír Čunát(noticed since my last post)08:32:26
@vcunat:matrix.orgVladimír ČunátBut it looks like just some missing includes.08:33:13
@vcunat:matrix.orgVladimír Čunát* But it looks like just some missing C #includes.08:33:33
@vcunat:matrix.orgVladimír Čunát* But it looks like just some missing C #include.08:33:35

Show newer messages


Back to Room ListRoom Version: 6