| 8 Aug 2024 |
 hanleym | In reply to @dazai:matrix.org
also sometime magic rollback is annoying, sometimes networkmanager fails to restart for no reason I think this was finally fixed. | 19:18:50 |
| hanleym | I disabled my hotfix for that a few weeks ago and it has been working. | 19:19:39 |
 dazai | hanleym: that page only shows how to build remotely on target, or how to cross build from x86_64 to aarch64. I have an aarch64 deployment server and a x86_64 deployment server that I want to deploy natively from, but with the same flake file | 19:23:43 |
| dazai | I don't want to build on target since I don't want builds to interrupt my production services | 19:24:07 |
| dazai | also good to know that that was finally fixed it was annoying me haha | 19:24:29 |
| hanleym | https://colmena.cli.rs/unstable/reference/deployment.html#deploymentbuildontarget | 19:24:54 |
| hanleym | Set that to false and it will build on the host. | 19:25:08 |
| hanleym | That should be the default though. | 19:25:48 |
| hanleym | dazai: ^ | 19:27:55 |
| dazai | yeah I know but i still need to specify architecture for colmena.meta.nixpkgs right? | 19:28:32 |
| dazai | https://colmena.cli.rs/unstable/tutorial/flakes.html | 19:28:56 |
| dazai | in the flake tutorial it has this
colmena = {
meta = {
nixpkgs = import nixpkgs {
system = "x86_64-linux";
overlays = [];
};
};
meaning i have to change my flake depending what machine i'm deploying on, does that make sense?
| 19:29:24 |
 dantefromhell | In reply to @hanleym:matrix.org
I haven't seen anything like --magic-rollback in deploy-rs, but I also don't think I've needed it. IIRC the boot counting feature was recently comitted to nixpkgs. I havent checked it in detail, but my understanding was that it allows you doing automated rollbacks (at least) if boot fail.
Not sure if that's what you had in mind? | 19:50:45 |
| dantefromhell | In reply to @dazai:matrix.org
in the flake tutorial it has this
colmena = {
meta = {
nixpkgs = import nixpkgs {
system = "x86_64-linux";
overlays = [];
};
};
meaning i have to change my flake depending what machine i'm deploying on, does that make sense?
interestimg issue 🤔
I might have a similar one when I get my rpis...
Essentially you would need to figure out the architecture of the system colmena/nix is running on and use that in the import statement. | 19:56:29 |
| dantefromhell | * interestimg issue 🤔
I might have a similar one when I get my rpis...
Essentially you would need to figure out the architecture of the system colmena/nix is running on and use that in the import statement.
me trying to rephrase the problem.for clarity... | 19:57:02 |
| hanleym | builtins.currentSystem? | 19:58:03 |
| dazai | hehe flakes don't have that | 19:58:25 |
| dazai | https://github.com/NixOS/nix/issues/3843 | 19:58:37 |
| dazai | thats why flake-utils exists, usually you just define your config inside of an "eachSystem" function and then it will define that config for each system, for example outputs.colmena.systems.x86_64.someSystem then if you tried to run colmena apply --on someSystem on an aarch64 it would complain about someSystem not being defined for the current architecture | 20:01:53 |
| dazai | but it doesn't seem like colmena is set up for that | 20:02:07 |
| 9 Aug 2024 |
|  @julienmalka:matrix.org left the room. | 10:47:30 |
| 13 Aug 2024 |
|  Niklauz joined the room. | 21:55:04 |
| 15 Aug 2024 |
 ser(ial) | how can i use imports = [ in host definition? | 02:41:06 |
| ser(ial) | error says: error: infinite recursion encountered | 02:41:42 |
| hanleym | I'm fairly sure I do this... Do you have a example you can share? | 14:09:56 |
| hanleym | Is it possible the thing you are importing is indeed causing infinite recursion? | 14:10:16 |
| 16 Aug 2024 |
| ser(ial) | i'm trying to import nix-bitcoin | 03:10:21 |
| ser(ial) |
| 03:18:08 |
| ser(ial) | "${nix-bitcoin}/modules/modules.nix"
];```
| 03:18:16 |
| ser(ial) | if it's wrong way in colmena, what is the correct one to manage nix-bitcoin with colmena? | 03:19:38 |
