| 17 Jul 2022 |
 @rendakuenthusiast:imperishable.name | so what maeks nixos-unstable-small different from nixos-unstable? | 05:38:50 |
 Buckley | the -small channels have a smaller set of prebuilt packages, and less tests are required to pass for the channel to move forward | 05:40:14 |
| Buckley | so the channel moves forward quicker | 05:40:33 |
| @rendakuenthusiast:imperishable.name | okay nevermind that failed | 05:41:04 |
| @rendakuenthusiast:imperishable.name | Activation failed: Child process exited with error code: 4
| Failed: Child process exited with error code: 4
| 05:41:28 |
 Winter (she/her) | In reply to @rendakuenthusiast:imperishable.name
okay nevermind that failed well it didn't segfault at least! | 05:43:56 |
| @rendakuenthusiast:imperishable.name | okay if I try the deploy again and actually remove that stanza, it works | 05:46:52 |
| Winter (she/her) | which stanza? | 05:58:56 |
| @rendakuenthusiast:imperishable.name | the one with the vhost I was trying to get rid of | 07:24:44 |
|  Christos Trochalakis joined the room. | 07:49:05 |
| Christos Trochalakis | Hello! I am using colmena with flakes, is it possible to build node configurations with hydra (hydraJobs)? | 13:49:19 |
|  @atharvaamritkar:matrix.org left the room. | 15:12:28 |
 Zhaofeng Li | In reply to @ctrochalakis:matrix.org
Hello! I am using colmena with flakes, is it possible to build node configurations with hydra (hydraJobs)? You may be able to wrap the node configurations back into nixosSystems. The Colmena flake exposes the deploymentOptions NixOS module so the deployment.* options still work. | 19:49:35 |
|  slby joined the room. | 20:08:22 |
| 18 Jul 2022 |
| @rendakuenthusiast:imperishable.name | another weird issue I'm running into | 04:55:45 |
| @rendakuenthusiast:imperishable.name | I wrote a helper function that woudl generate an nginx vhost set of the form { services.nginx.virtualHosts."hostname.example.com" = <nginx configuration> } | 04:56:34 |
| @rendakuenthusiast:imperishable.name | so that I could define the vhost for a service in the same module I define the service in | 04:56:58 |
| @rendakuenthusiast:imperishable.name | so I have my helper function return the above set, and then use \\ helperFunction { hostname="hostname"; } to merge it into the config set that was already being returned for each service I'm running | 04:57:32 |
| @rendakuenthusiast:imperishable.name | and this is causing existing configuration to stop appearing in ways I don't understand | 04:57:52 |
| @rendakuenthusiast:imperishable.name | if I have a set a and a set b with no keys in common, a \\ b will just merge them without overwriting anything, right? | 04:58:12 |
| Winter (she/her) | you mean //, right? | 05:00:49 |
| @rendakuenthusiast:imperishable.name | er, yes, // | 05:04:09 |
| @rendakuenthusiast:imperishable.name | I didn't type it wrong in my code | 05:04:33 |
| @rendakuenthusiast:imperishable.name | okay, I have a minimal example: https://privatebin.net/?849782ab0b96f528#9W3j2DCQz6fRo57akit3xWHGk3XquY9g5zE7tB6qotDi | 05:41:57 |
| @rendakuenthusiast:imperishable.name | when I say "works", I mean the first version there creates the nginx vhost host.example.com, and the second version doesn't create it | 05:42:21 |
| @rendakuenthusiast:imperishable.name | and I"m not sure why, I woudl expect those two expressions to be equivalent | 05:42:35 |
| 19 Jul 2022 |
| Zhaofeng Li | // only does shallow merging. For example, { fruits.apple = 1; } // { fruits.banana = 2; } returns { fruits.banana = 2; }. What you want for configurations is lib.mkMerge: https://nixos.org/manual/nixos/stable/#sec-option-definitions-merging | 08:18:55 |
| 21 Jul 2022 |
| @rendakuenthusiast:imperishable.name | huh, I did not know those were the semantics of // | 20:25:08 |
| @rendakuenthusiast:imperishable.name | I wish that documentation had been easier to find | 20:25:46 |
| @rendakuenthusiast:imperishable.name | so, if I use lib.mkMerge in my code, I get this error:
error: You're trying to declare a value of type `lambda'
rather than an attribute-set for the option
`'!
This usually happens if `' has option
definitions inside that are not matched. Please check how to properly define
this option by e.g. referring to `man 5 configuration.nix'!
(use '--show-trace' to show detailed location information)
| 20:44:30 |
