| 1 Oct 2022 |
 @garionion:entr0py.de | * (everything under ./fem is the submodule) | 18:17:53 |
 Zhaofeng Li | Sadly flakes don't support (*) submodules at the moment. As a workaround, you can add the fem submodule as a flake input.
(*) Actually the water is muddier but this is the simplest description of the situation at the moment.
| 20:22:10 |
| 2 Oct 2022 |
|  Daniel joined the room. | 00:48:54 |
| @garionion:entr0py.de | In reply to @zhaofeng:zhaofeng.li
Sadly flakes don't support (*) submodules at the moment. As a workaround, you can add the fem submodule as a flake input.
(*) Actually the water is muddier but this is the simplest description of the situation at the moment.
But I would have to add a flake.nix to fem right? Or can I just use a plain git repo as a input? | 09:35:38 |
| @garionion:entr0py.de | * But I would have to add a flake.nix to `fem` right? Or can I just use a plain git repo as an input? | 09:35:46 |
 @yuka:yuka.dev | inputs.<name>.flake = false; | 09:38:20 |
 [0x4A6F] | In reply to @yuka:yuka.dev
I have another request: In flake-enabled deployments, can we pass the nixpkgs flake so that the hive expression can use nixpkgs.lib.nixosSystem and get the proper system.nixos.(revision|versionSuffix)? Using colmena.defaults.system.nixos.version = "${nixpkgs.lib.trivial.release}.git.${nixpkgs.shortRev}"; as a workaround for now. | 22:43:06 |
| 5 Oct 2022 |
|  Rosuavio joined the room. | 19:07:48 |
| 7 Oct 2022 |
 Wanja Hentze | Hey, does anybody know what the semantics are when I set both meta.nixpkgs and meta.nodeNixpkgs? The docs don't really say: https://colmena.cli.rs/unstable/reference/meta.html#nixpkgs | 07:30:30 |
| Wanja Hentze | Background: I'm trying to use the new colmena.lib.makeHive entry point, but that errors in hermetic mode if meta.nixpkgs is unset, even if meta.nodeNixpkgs is set. But I do want per-node nixpkgs pinning | 07:31:36 |
| Wanja Hentze | Maybe that's a bug, and it should not error out there. In that case, let me know and I'll provide a PR to fix it :) | 07:32:04 |
|  @v:meowy.tech changed their display name from v to vā. | 08:13:11 |
| Zhaofeng Li | In reply to @whentze:matrix.org
Hey, does anybody know what the semantics are when I set both meta.nixpkgs and meta.nodeNixpkgs? The docs don't really say: https://colmena.cli.rs/unstable/reference/meta.html#nixpkgs nodeNixpkgs is used to evaluate the node configs, but meta.nixpkgs.lib is still used for evaluating meta itself and other stuff which is why it's still required. | 13:53:01 |
| Zhaofeng Li | I agree that this isn't ideal and can be confusing (there was even a PR a while ago trying to remove the dependency) | 13:54:43 |
| Wanja Hentze | ah, those semantics are fine actually :) | 14:06:58 |
| Wanja Hentze | (in my opinion) | 14:07:08 |
| Wanja Hentze | I was just worried that meta.nixpkgs would take precendence maybe and override my carefully written meta.nodeNixpkgs | 14:08:02 |
| 9 Oct 2022 |
 Winter (she/her) | I have 2 nodes, and when running colmena build, the progress indicator displays 2 running, 1 succeeded when the 2 builds are running, but the eval has succeeded. (I assume that's what it's saying succeeded?) Is this intentional? It seems confusing. | 17:47:53 |
| Winter (she/her) | * I have 2 nodes, and when running colmena build, the progress indicator displays 2 running, 1 succeeded when the 2 builds are running, but the eval has succeeded. (I assume that's what it's saying succeeded?) Is this intentional? It's confusing š
| 17:48:05 |
| Winter (she/her) | When one of the nodes finishes building, it jumps to 1 running, 1 succeeded. | 17:48:39 |
| Winter (she/her) | Smells like a bug | 17:48:44 |
| Zhaofeng Li | Yeah, it does look like a bug. Need to take a look at the job management part. | 18:25:33 |
| Winter (she/her) | I'm on latest master btw | 18:37:40 |
| Winter (she/her) | (as of when I sent that message, anyways) | 18:37:56 |
| Winter (she/her) | can get commit hash later if that helps | 18:38:10 |
| Winter (she/her) | though i doubt it's changed since then | 18:38:16 |
|  manny joined the room. | 19:53:08 |
| 11 Oct 2022 |
 Linux Hackerman | Hm, is anybody else using toString in their secret definitions? lazy-trees breaks that. Just a heads-up. | 11:32:16 |
| Linux Hackerman | * Hm, is anybody else using Flakes and toString in their secret definitions? lazy-trees breaks that. Just a heads-up. | 11:33:56 |
| Linux Hackerman | I currently have keyCommand = ["gpg" "--decrypt" ((toString ../secrets) + "/${if value.shared then "shared" else config.networking.hostName}/${name}.gpg")]; in my secrets module. | 11:34:13 |
