| 20 Dec 2025 |
 goldstein | nix-repl> builtins.flakeRefToString { type = "indirect"; id = "lol"; ref = "lol/9bdfd23e28ffc1fb5a6e52e43dad4288701bb05d"; }
"flake:lol/lol/9bdfd23e28ffc1fb5a6e52e43dad4288701bb05d"
nix-repl> builtins.flakeRefToString { type = "indirect"; id = "lol"; ref = "lol"; rev = "9bdfd23e28ffc1fb5a6e52e43dad4288701bb05d"; }
"flake:lol/lol/9bdfd23e28ffc1fb5a6e52e43dad4288701bb05d
no question here, I just want to share my pain đź«
why are flakerefs so ambiguous | 18:54:59 |
| goldstein | I knew that parse(serialize(flakeref)) is not noop because of HTTP query params, but I didn’t know that indirect flakerefs are also ambigous | 18:59:00 |
| goldstein | and getFlake only takes string flakerefs, so some getFlake invocations are quite literally inexpressible | 18:59:37 |
| goldstein | nix-repl> builtins.parseFlakeRef (builtins.flakeRefToString { type = "indirect"; id = "nixpkgs"; ref = "refs/heads/master"; })
error:
… while calling the 'parseFlakeRef' builtin
at «string»:1:1:
1| builtins.parseFlakeRef (builtins.flakeRefToString { type = "indirect"; id = "nixpkgs"; ref = "refs/heads/master"; })
| ^
error: GitHub URL 'flake:nixpkgs/refs/heads/master' is invalid
that one is probably a bug though? no way it’s a github url | 19:06:51 |
 Sofie 🏳️‍⚧️ (she/her) | also, rootless install through nixsa would be nice to have! | 19:48:40 |
 bandithedoge | real | 19:49:12 |
| 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 |
| Charles | Yeah I experienced lots of jank with attic | 17:44:56 |
