| 13 May 2022 |
 @linus:schreibt.jetzt | there used to be nix-push, but that was removed in favour of the unstable nix copy interface 🙃 | 08:36:14 |
 snartvellental | why is nix such a big ocean lol :D sometimes I feel like i've seen 5% or 0,05% | 11:23:03 |
 Buckley | Because nix invites the user to jump into the whole stack and mess around :o | 13:05:35 |
 @schnecfk:ruhr-uni-bochum.de | Interesting. I'm currently not at home and tried apply-local for the first time to update my laptop. It fails and claims my machine isn't a NixOS machine 🤔 | 13:48:31 |
 Zhaofeng Li | Which versions of nixpkgs and Colmena? It doesn't look like they changed the format of /etc/os-release again | 18:59:04 |
| 18 May 2022 |
 @janejasperous:one.ems.host | hi, im configuring my systems using colmente to deploy in my network. I'd like to have some machines running 21.11 others 22.05 other unstable. I get working this for packages, but not for full nixos system (modules,...) | 12:27:06 |
| @janejasperous:one.ems.host | * hi, im configuring my systems using colmena to deploy in my network. I'd like to have some machines running 21.11 others 22.05 other unstable. I get working this for packages, but not for full nixos system (modules,...) | 12:27:13 |
| @janejasperous:one.ems.host | i expected declare machines as server1 = inputs.nixpkgs-2305.lib.nixosSystem { (...) | 12:29:26 |
| @janejasperous:one.ems.host | * i expected declare machines as server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) | 12:29:35 |
| @janejasperous:one.ems.host | * i expected declare machines as server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) to work | 12:29:58 |
 @phaer:matrix.org | In reply to @janejasperous:one.ems.host
i expected declare machines as server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) to work You don't need lib.nixosSystem for colmena, just the config | 15:01:51 |
| @phaer:matrix.org | server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) }.config could also work, i think? But haven't tested this | 15:03:21 |
| @schnecfk:ruhr-uni-bochum.de | In reply to @phaer:matrix.org
server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) }.config could also work, i think? But haven't tested this Kind of - I'm using such a shim to use nixosConfigurations and colmena together: https://github.com/zhaofengli/colmena/issues/60#issuecomment-1047199551 | 15:04:14 |
| @phaer:matrix.org | Ah, good to know. I personally just keep my stuff in the nixosModules output of my flake and can then put them into colmena configs for hosts I deploy with colmena or nixosConfigurations as needed | 15:05:44 |
| @janejasperous:one.ems.host | Effectively im using colmena + nixos-rebuild | 19:57:00 |
| @janejasperous:one.ems.host | In reply to @phaer:matrix.org
You don't need lib.nixosSystem for colmena, just the config ok that work locally with nixos-rebuild. This piece of code fails becuase overwrite nixpkgs-2205 for nixpkgs | 21:43:00 |
| @janejasperous:one.ems.host | colmena = {
meta = {
nixpkgs = import nixpkgs { system = "x86_64-linux"; };
specialArgs = { inherit inputs; };
};
} // builtins.mapAttrs (name: value: {
nixpkgs.system = value.config.nixpkgs.system;
imports = value._module.args.modules;
}) (self.nixosConfigurations);
| 21:43:21 |
| @janejasperous:one.ems.host | In reply to @phaer:matrix.org
You don't need lib.nixosSystem for colmena, just the config * ok that works locally with nixos-rebuild. This piece of code fails makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:43:48 |
| @janejasperous:one.ems.host | * ok server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) } that works locally with nixos-rebuild. This piece of code fails makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:44:21 |
| @janejasperous:one.ems.host | * ok server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) } works locally with nixos-rebuild. This piece of code fails makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:44:30 |
| @janejasperous:one.ems.host | * ok server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) } works locally with nixos-rebuild. This piece of code makes colmena overwrite nixpkgs-2205 for nixpkgs | 21:44:42 |
| @schnecfk:ruhr-uni-bochum.de | In reply to @janejasperous:one.ems.host
ok server1 = inputs.nixpkgs-2205.lib.nixosSystem { (...) } works locally with nixos-rebuild. This piece of code makes colmena overwrite nixpkgs-2205 for nixpkgs For that to work, you'll likely also need to use nodeNixpkgs as described in the colmena manual | 22:59:32 |
| 19 May 2022 |
| @janejasperous:one.ems.host | In reply to @schnecfk:ruhr-uni-bochum.de
For that to work, you'll likely also need to use nodeNixpkgs as described in the colmena manual of course, that works. but duplicate code. Could be interesting colmena accepts nixosSystem.config as is | 08:39:52 |
| @schnecfk:ruhr-uni-bochum.de | Maybe I can change my shim a bit 🤔 Might be non-ideal. For example: nodeNixpkgs could probably be populated from nixosConfigurations.hostname.pkgs | 09:10:59 |
|  Michael Peyton Jones joined the room. | 17:33:16 |
| 21 May 2022 |
|  @hanemile:matrix.org joined the room. | 20:31:51 |
| 23 May 2022 |
 @blaggacao:matrix.org | How colmena would look like in a nushell:
colmena | where tag = oakland | each { |it| ^comena deploy ($it.fragment) }
| 05:17:05 |
| @blaggacao:matrix.org | * How colmena would look like in a nushell: (pseudo code)
```nu
colmena | where tag = oakland | each { |it| ^colmena deploy ($it.fragment) }
``` | 05:17:58 |
| 24 May 2022 |
 aanderse | any way to increase debug/error logging for the deployment.keys options? i'm not getting much and i don't know what i'm doing wrong | 20:27:15 |
| aanderse | using keyCommand, btw | 20:27:33 |
