!UNVBThoJtlIiVwiDjU:nixos.org

Staging

309 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/106 Servers

Load older messages


SenderMessageTime
28 Oct 2025
@emilazy:matrix.orgemilythere was discussion about whether to go through a warning cycle for the ones without them or throw immediately17:45:41
@emilazy:matrix.orgemilywe could still backtrack and attach warnings to those ones17:45:56
@wolfgangwalther:matrix.orgWolfgang WaltherYeah, I'd say we could do that on a case-by-case basis, if there is reason for a specific case.17:46:27
@wolfgangwalther:matrix.orgWolfgang WaltherWas the argument that this should actually persist forever? If so, we'll just need to mark the alias as such instead.17:46:53
@emilazy:matrix.orgemilyin practice unstable changes in ways that produce throws all the time I think, in this case it's at least a way that you can handle downstream without breaking compat with any supported release17:46:55
@emilazy:matrix.orgemilywhich AIUI has been the sticking point historically17:47:01
@emilazy:matrix.orgemily(anyway, this is just trying to prep for structured aliases which will automatically do silent β†’ warning β†’ throw β†’ removed without all the manual work and eval issues wrangling this stuff manually causes right now :/ )17:47:30
@hexa:lossy.networkhexait's not even in 25.05, it was probably removed earlier than that. no everything should be subject to a deprecation cycle IMO.17:47:39
@emilazy:matrix.orgemilyto be clear, no Nixpkgs core decision on this17:47:50
@emilazy:matrix.orgemily anyway, putting a warning on runCommandNoCC seems reasonable enough to me 17:48:21
@hexa:lossy.networkhexaoh, it was utillinux πŸ˜„ 17:48:47
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/19287017:48:59
@emilazy:matrix.orgemilyoh, gah17:49:18
@hexa:lossy.networkhexadue to the node2nix abandonware17:49:20
@emilazy:matrix.orgemily I specifically dropped that one because I saw that node2nix was "handling it" since 2020 17:49:29
@emilazy:matrix.orgemilyand forgot this particular nuance of how it "handles it"17:49:34
@emilazy:matrix.orgemily in practice nodePackages is almost gone and IIRC node2nix doesn't even work with new Node versions anyway? so meh… 17:49:55
@hexa:lossy.networkhexaso, thanks for pruning aliases17:51:14
@pyrox:pyrox.devdish [Fox/It/She] wouldn't say almost gone at this point, still well over 100 packages in the set and the file is still 2+ MB >.> 17:52:42
@pyrox:pyrox.devdish [Fox/It/She]sadly17:52:49
@emilazy:matrix.orgemily we could also attach warnings to the top-level system/hostPlatform/buildPlatform/targetPlatform which I think Artturin wanted to kill off 17:54:26
@emilazy:matrix.orgemily(they were added to the aliases file many years ago)17:54:32
@emilazy:matrix.orgemilybut I opted for being conservative about that since it's post-freeze17:54:39
@artturin:matrix.orgArtturinOh yeah we still have those aliases, yeah we should make them warns17:55:58
@emilazy:matrix.orgemily they're still used in pkgs/test even πŸ™ƒ 17:56:13
@emilazy:matrix.orgemily can we make stdenv.isFoo warn as well? πŸ˜† 17:56:16
@emilazy:matrix.orgemilymaybe something for early 26.0517:56:21
@emilazy:matrix.orgemily looking at the diff, runCommandNoCC, runCommandNoCCLocal, and maybe utillinux seem like the main things worth turning into warnings instead of throws 18:00:22
@artturin:matrix.orgArtturinYou sure?18:00:30
@emilazy:matrix.orgemily might also be good to adjust the python throw error message 18:00:47

Show newer messages


Back to Room ListRoom Version: 6