!VRULIdgoKmKPzJZzjj:nixos.org

Nix Hackers

871 Members
For people hacking on the Nix package manager itself188 Servers

Load older messages


SenderMessageTime
1 Nov 2025
@dramforever:matrix.orgdramforeveron nix hydra or nixpkgs hydra?20:52:23
@emilazy:matrix.orgemilylatter, but if they differ I assume only due to former's Nixpkgs lagging behind20:53:09
@dramforever:matrix.orgdramforeverhmm... that's not really worse than the nixos.org/nix/install installer, right?20:54:02
@emilazy:matrix.orgemilyno, I'm just speaking to my impression of the static build's maintenance state20:56:20
@dramforever:matrix.orgdramforeverright, so i guess at least for now it's not a great thing to be shipping to users20:57:08
@emilazy:matrix.orgemily the failures have not always been due to regressions in other packages IIRC, but it's been a while since I checked. just know my last nixpkgs-review failed to build it 20:57:18
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)
In reply to @dramforever:matrix.org
i've never been quite sure - what's the support status of statically linked nix? it's something i've found genuinely incredibly convenient... but the only way i know to download one is to dig from hydra which seems not ideal
Generally it’s the dependencies that are broken in nixpkgs. Nix’s jobset from a release branch (e.g. 2.32-maintenance) is a well supported as the regular dynamically linked nix.
21:58:59
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Since nix’s nixpkgs flake input is from a stable release for the better part of the nixpkgs release cycle it tends to get fixed.21:59:52
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)
In reply to @dramforever:matrix.org
right, so i guess at least for now it's not a great thing to be shipping to users
I don’t understand how you get that conclusion tho. It’s not nix that is poorly maintained, but the dependencies that spontaneously explode in nixpkgs. As always though it’s not a great idea to use the ‘masterjobset for anything other than dogfooding. Using anything from*-maintenance` is perfectly fine and supported
22:02:42
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)
In reply to @dramforever:matrix.org
right, so i guess at least for now it's not a great thing to be shipping to users
* I don’t understand how you get that conclusion tho. It’s not nix that is poorly maintained, but the dependencies that spontaneously explode in nixpkgs. As always though it’s not a great idea to use the master jobset for anything other than dogfooding. Using anything from*-maintenance` is perfectly fine and supported
22:02:59
@emilazy:matrix.orgemilyit's definitely not just failing deps, e.g. https://hydra.nixos.org/job/nixpkgs/trunk/nixStatic.aarch64-darwin/all and https://hydra.nixos.org/job/nixpkgs/trunk/nixStatic.x86_64-linux/all both have direct failures that persisted for quite some time22:12:20
@emilazy:matrix.orgemily (and some of the dep issues I've seen regress nixStatic have been e.g. on Nix version updates pulling in new ones, which is an in-between case I suppose) 22:12:40
@xokdvium:matrix.orgSergei Zimmerman (xokdvium) Well, dramforever s question was about the nix jobset - not the nixpkgs one. 22:13:44
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)It’s always been Jörg that fixed static build issues on master nixpkgs, but that seems to be a never-ending battle. The less troublesome way seems to be keeping the static build in a working shape in all nix jobsets and fix nixpkgs master around the branch off when nix switches the nixpkgs input around22:16:54
2 Nov 2025
@connorbaker:matrix.orgconnor (burnt/out) (UTC-8) changed their display name from connor (burnt/out) (UTC-7) to connor (burnt/out) (UTC-8).08:13:02
@mjoerg:nixos.devMartin Joerg joined the room.12:14:51
@fzakaria:one.ems.hostfzakariapre-commit finally built on aarch6416:25:26
@fzakaria:one.ems.hostfzakariahttps://hydra.nixos.org/build/31023308116:25:27
@fzakaria:one.ems.hostfzakariacan someone try to re-merge https://github.com/NixOS/nix/pull/14345 ?18:47:07
@amadaluzia:unredacted.orgamadaluzia joined the room.21:40:50
3 Nov 2025
@joerg:thalheim.ioMic92 maralorn: I wonder what we could do to mitigate this situation: https://github.com/NixOS/nix/pull/14364#issuecomment-3479674426 09:50:08
@maralorn:maralorn.demaralornI opened https://github.com/maralorn/nix-output-monitor/issues/20610:06:39
@zimbatm:numtide.comJonas Chevalier joined the room.12:50:28
@lovesegfault:matrix.orglovesegfaultI'm running ~10min late to the meeting but coming!17:12:16
@joerg:thalheim.ioMic92https://jitsi.lassul.us/nix-maintainers monday meeting.17:37:05
@joerg:thalheim.ioMic92 Sergei Zimmerman (xokdvium): https://github.com/NixOS/nixpkgs/pull/458072#issuecomment-3481595336 which pr was it again, where you restored performance? 17:57:27
@joerg:thalheim.ioMic92 * Sergei Zimmerman (xokdvium): https://github.com/NixOS/nixpkgs/pull/458072#issuecomment-3481595336 what pr was it again, where you restored performance? 17:57:42
@joerg:thalheim.ioMic92nix 2.3217:57:49
@joerg:thalheim.ioMic92 lovesegfault: https://github.com/GNOME/mutter/blob/fae3d35366831e089e42570ca73ad60d62b08d4b/.gitlab-ci/coverity-model.c#L4 18:17:40
@lovesegfault:matrix.orglovesegfault

fzakaria:

[39/483] Generating src/kaitai-struct-checks/kaitai-generated-sources with a custom command
../src/kaitai-struct-checks/nar.ksy: /types/padded_str/seq/1/encoding:
        warning: use canonical encoding name `ASCII` instead of `ascii` (see https://doc.kaitai.io/ksy_style_guide.html#encoding-name)
19:54:20

Show newer messages


Back to Room ListRoom Version: 6