| 5 Feb 2026 |
 neobrain | Aw, fair enough. Do the non-flake code paths show a percentual progress? It didn't actually occur to me that flakes might be different and just used the term as a shorthand for "fetching [e.g.] nixpkgs" | 21:29:58 |
| neobrain | * Aw, fair enough. But are you implying that the non-flake code paths already do show a percentual progress? It didn't actually occur to me that flakes might be different and just used the term as a shorthand for "fetching [e.g.] nixpkgs" | 21:30:23 |
| neobrain | Redacted or Malformed Event | 21:41:35 |
| neobrain | * eh, looks like it does show the expected total size in contrast to flakes, just that the expected total size is wrong 😅
❯ nix eval --raw github:NixOS/nixpkgs/nixos-25.05#hello
[21.7 MiB/2.3 KiB DL] downloading 'https://github.com/NixOS/nixpkgs/archive/ac62194c3917d5f474c1a844b6fd6da2db95077d.tar.gz'`
| 21:42:08 |
| neobrain | Ah well, fetching via non-flake (took me a while to figure out how to do that) indeed prints the normal git clone output and by extension a percentual progress | 21:54:47 |
 delroth | I'd recommend filing a feature request anyway - it might be it's trivial to fix and someone just needs to know it needs to be fixed, Lix is in general trying to improve the UX so this kind of feedback can always be useful | 22:32:47 |
| 6 Feb 2026 |
 n3tcat | λ nix --version
nix (Lix, like Nix) 2.93.3
am I cool now | 01:17:49 |
| 13 May 2024 |
|  zrsk joined the room. | 13:37:30 |
|  dariof4 joined the room. | 14:16:05 |
|  abbe joined the room. | 14:42:22 |
 mjm | lix is now in nixos-unstable, what's the best way to use it in a NixOS config? | 15:47:41 |
 K900 | nix.package = pkgs.lix | 15:47:54 |
| K900 | Probably | 15:47:58 |
| K900 | Or just keep using the module | 15:48:02 |
 puck | you can use nix.package = pkgs.lix; if you want; but using the overlay will guarantee more updates (tho less binary cache) | 15:48:44 |
| mjm | well, the module/overlay doesn't easily support using the one from nixpkgs | 15:48:44 |
| mjm | i do want more binary cache | 15:49:21 |
| mjm | yeah i guess i'll just do nix.package then | 15:50:43 |
 raitobezarius | to have binary cache and HEAD, we will probably need to track the channels and bolt a lix on there and rebuild with our own CI then push in our binary cache | 17:33:17 |
 Charles | What's lix using as its binary cache? Attic? | 17:34:36 |
|  Arian left the room. | 17:37:44 |
 @tc424:glasgow.social | Last I heard they were using garage as the back end, and think about attic | 17:39:11 |
| @tc424:glasgow.social | I don't know if that means they're just pushing directly into garage's s3 interface for the moment | 17:39:36 |
| @tc424:glasgow.social | * Last I heard they were using garage as the back end, and thinking about attic | 17:39:57 |
| raitobezarius | In reply to @charles:computer.surgery
What's lix using as its binary cache? Attic? garage without attic | 17:41:16 |
| raitobezarius | it's homemade just nix push thingie | 17:41:24 |
| raitobezarius | and nix sign | 17:41:25 |
 Qyriad | yep | 17:44:26 |
| @tc424:glasgow.social | I've just given up on attic due to weird non-deterministic auth problems that nobody else seems to have experienced | 17:44:31 |
| @tc424:glasgow.social | Still half convinced I'm "holding it wrong" somehow | 17:44:49 |
