!9IQChSjwSHXPPWTa:lix.systems

Lix

1140 Members
Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms315 Servers

Load older messages


SenderMessageTime
11 Apr 2026
@raitobezarius:matrix.orgraitobezariusto keep using Lix with very old Nixpkgs that suffers from deprecated features12:00:57
@raitobezarius:matrix.orgraitobezariusI personally care about the ability to evaluate over decades but I don't want this (secondary?) goal to stand in the path of evolution, so there must be some mechanisms to achieve both things while balancing out efforts12:02:15
@blitz:chat.x86.lolblitz Yes that's sensible 12:55:57
@blitz:chat.x86.lolblitzSince most of the deprecations are just syntax, having a way to specify what nix language version you want to parse would also be cool (a bit like rust editions)12:57:09
@raitobezarius:matrix.orgraitobezariusIt's the whole topic of langver at Lix that we want to address someday12:59:32
@raitobezarius:matrix.orgraitobezarius(there's also its variants: derivation versions too)12:59:47
@lassulus:lassul.uslassuluslangver would be cool13:31:18
@kfiz:matrix.sopado.dekfiz Indeed. I think there needs to be a clear story or at least good “central” recommendations on how to approach which use cases in lix (nix). Currently it’s to confusing even for people who have been using nix for a while. 15:42:30
@raitobezarius:matrix.orgraitobezariusYep, definitely17:10:42
@lotte:chir.rsLotte (it/its)/Cinny (she/her) θΔ& is there a lix equivalent of the cppnix setting [abort-on-warn](https://nix.dev/manual/nix/2.24/command-ref/conf-file#conf-abort-on-warn)? 18:27:03
@whispers:catgirl.cloudwhispers [& it/fae] yes it's abort-on-warn (added in 2.95) 18:32:20
@whispers:catgirl.cloudwhispers [& it/fae]second item here https://docs.lix.systems/manual/lix/stable/release-notes/rl-2.95.html#features18:33:17
@lotte:chir.rsLotte (it/its)/Cinny (she/her) θΔ&oh18:39:26
@lotte:chir.rsLotte (it/its)/Cinny (she/her) θΔ&should have used .latest instead of .stable18:40:01
@lotte:chir.rsLotte (it/its)/Cinny (she/her) θΔ&thanks18:40:06
12 Apr 2026
@crystallord:matrix.orgCrystal changed their profile picture.02:15:00
@sapphoqt:matrix.orgSappho joined the room.06:32:14
@leona:leona.isleona changed their profile picture.12:15:24
13 Apr 2026
@lisanna-dettwyler:matrix.orgLisannaI might take a crack at beginning to fix this at least for nix develop, I've been doing a little bit of work on that code recently.00:25:49
@lisanna-dettwyler:matrix.orgLisannaThere're some ideas for how to fix it in https://github.com/NixOS/nix/issues/750100:26:16
@evelyn:nope.chatevelyn joined the room.03:23:12
@k900:0upti.meK900
In reply to @lisanna-dettwyler:matrix.org
I might take a crack at beginning to fix this at least for nix develop, I've been doing a little bit of work on that code recently.
This is very cross-cutting tbh
05:03:57
@k900:0upti.meK900 I think you'd have to start at nixpkgs 05:04:08
@k900:0upti.meK900 And probably structuredAttrs? 05:04:30
@blitz:chat.x86.lolblitz I almost have a prototype of attic that solves this for now by calling the Nix CLI. Will check gorgon once I have something working. One last obstacle: Is there a stable way to list the signatures of a store path without resorting to nix path-info (which has changed output formats a couple of times...) ? 07:35:48
@lisanna-dettwyler:matrix.orgLisannaOh for sure, the whole point would be to make nixpkgs do the heavy lifting here08:11:59
@blokyk:matrix.orgzoë (she/her) is there any way to see previous build logs after rebuilding a derivation? kind of like journalctl's --boot option to see previous boot logs instead of the current one. it seems like nix overwrites them now; would there be any obstacle to renaming them to foo.drv-1, foo.drv-2, etc when a new build is launched? 08:41:12
@blokyk:matrix.orgzoë (she/her) * is there any way to see previous build logs after rebuilding a derivation? kind of like journalctl's --boot option to see previous boot logs instead of the current one. it seems like current nix overwrites them; would there be any obstacle to renaming them to foo.drv-1, foo.drv-2, etc when a new build is launched? 08:41:27
@nxrth:beeper.comboop-northI did sudo -i nix upgrade-nix and now can't run commands related to nix. `nix/var/nix/profiles/default/bin exists in path09:56:08
@nxrth:beeper.comboop-north I did sudo -i nix upgrade-nix and now can't run commands related to nix. nix/var/nix/profiles/default/bin exists in path 09:56:15

Show newer messages


Back to Room ListRoom Version: 10