| 11 Dec 2024 |
 Capypara | I'm not entirely sure that derivation is causing this though. | 13:24:36 |
| Capypara | But most of my config is just from nixpkgs. | 13:24:54 |
| Capypara | In reply to @capypara:matrix.org
I'm not entirely sure that derivation is causing this though. (actually it's multiple) | 13:25:13 |
 Yureka (she/her) | is it actually failling to build something, or just printing some warning messages? | 13:25:25 |
| Capypara | Just warnings | 13:25:31 |
 K900 | I think the actual issue here is that those warnings are impossible to attribute | 13:25:42 |
| K900 | And we can absolutely provide more context | 13:25:51 |
 jakra | Good call, switching to 24.11 fixed it! Thanks :) | 13:56:08 |
|  @dminca:matrix.org left the room. | 14:19:26 |
| Capypara | Does Lix not support distributed builds? I switched to Lix and now my derivations don't seem to be built on the remote server anymore. It also seems that my binary cache isn't picked up. Is the config via the nix NixOS module not supported?
| 14:33:21 |
| Capypara | I should maybe add that I did not switch to Lix voluntarily, only because Nix is somehow broken for me at the moment. I'm running it on my Steam Deck, and compiling an entire Linux kernel on my Deck isn't a good idea haha | 14:34:16 |
 raitobezarius | I do use distributed builds with my Lix | 14:42:03 |
| Capypara | thanks! then I'll try and debug why it isn't working | 14:44:32 |
 Lily Foster | In reply to @capypara:matrix.org
Does Lix not support distributed builds? I switched to Lix and now my derivations don't seem to be built on the remote server anymore. It also seems that my binary cache isn't picked up. Is the config via the nix NixOS module not supported?
the nix settings from nixos module should be sufficient. you can see what config is picked up via nix show-config | 15:31:59 |
| Capypara | Thanks! | 15:34:39 |
| Capypara | I can see my cache server being configured but I don't see the distributed build settings. | 15:34:53 |
| Capypara | Oh but hang on, I see the issue now, this is fully my fault. I did not have the distributed builds enabled yet on this system, it's been a while since I pulled updates to my config. Sorry!! | 15:36:43 |
| Capypara | still weird that it didn't pull from the cache server though, but I'll debug that a bit in a bit more controlled environment | 15:37:45 |
|  tpool joined the room. | 16:36:11 |
 aloisw | Did it pull from another cache or build from scratch? | 17:39:28 |
| Capypara | From scratch. The hashes are also different, so it seems to be have built differently than nix. | 17:42:53 |
| Capypara | I normally build my Steam Deck configuration on my main PC and then push everything into my cache. | 17:43:14 |
| Capypara | I don't observe any problems though, it finished building and everything seems to work. | 17:43:37 |
| aloisw | Oh if the hashes are different, it's expected it won't pull from the cache. So the real question is if it's expected that the hashes are different. | 17:43:59 |
| aloisw | Normally the hashes should not be different, but there have been some bug fixes. | 17:44:26 |
| Capypara | Yeah, I noticed that just now. I was able to get it to pull from my cache in a little test. | 17:44:38 |
| aloisw | You may want to check what caused the hashes to be different. | 17:45:20 |
| Capypara | Even with Nix I noticed some things getting rebuilt and having different hashes if I build from another system, even though they shouldn't, but never the kernel. | 17:45:35 |
| Capypara | Yeah, I'll probably do that later. | 17:45:45 |
| aloisw | Well the kernel getting a different hash is certainly unexpected unless you do weird stuff like patching your kernel in ways that end up depending on impurities. | 17:46:36 |
