| 26 Sep 2022 |
 @rendakuenthusiast:imperishable.name | jhillyerd: where does that substituteInPlace function come from? is that supposed to be shell code? | 05:01:59 |
 jhillyerd | I believe it is one of the shell functions that mkDerivation provides | 05:05:43 |
 Zhaofeng Li | In reply to @rendakuenthusiast:imperishable.name
and when colmena tries to deploy from my laptop, I have /usr/bin/pgrep installed at that path in my normal OS Hmm, pgrep should have been added when the tests were enabled in https://github.com/NixOS/nixpkgs/commit/835c3419d9b9 | 19:42:12 |
| Zhaofeng Li | In reply to @rendakuenthusiast:imperishable.name
Winter (she/her): I'm using builtins.fetchTarball to fetch an additional module with some custom modifications I made, from a server I control I recommend adding a sha256 to the fetchTarball call so it's pinned to the specific version of the module and cached correctly. If you don't have a sha256, Nix itself has some time-based caching (need to look at the expiration - don't know offhand) | 19:44:50 |
| Zhaofeng Li | (it's 1 hour and can be controlled with tarball-ttl) | 19:46:53 |
| 27 Sep 2022 |
| @rendakuenthusiast:imperishable.name | In reply to @zhaofeng:zhaofeng.li
I recommend adding a sha256 to the fetchTarball call so it's pinned to the specific version of the module and cached correctly. If you don't have a sha256, Nix itself has some time-based caching (need to look at the expiration - don't know offhand) so I updated the file at the url and wanted it to get refetched | 00:58:54 |
| @rendakuenthusiast:imperishable.name | I tried doing the trick of wiping out the sha256, but it just said that the hash of the previously-downloaded version was what the hash had to be | 00:59:16 |
| @rendakuenthusiast:imperishable.name | not the new version I uploaded | 00:59:21 |
| @rendakuenthusiast:imperishable.name | so it's not fetching the new version | 00:59:28 |
| Zhaofeng Li | In reply to @rendakuenthusiast:imperishable.name
I tried doing the trick of wiping out the sha256, but it just said that the hash of the previously-downloaded version was what the hash had to be If you set sha256 to all zeroes (or lib.fakeSha256) does it force a refetch? | 01:00:20 |
| @rendakuenthusiast:imperishable.name | Zhaofeng Li: that's what i tried, it doesn't force a refresh, it says that it expects the same sha256 that was there before corresponding to the outdated version of the file | 03:50:27 |
|  @palo:xaos.space changed their profile picture. | 07:29:30 |
| @palo:xaos.space changed their profile picture. | 07:31:44 |
| @palo:xaos.space changed their profile picture. | 07:35:09 |
|  @skamdart:matrix.org joined the room. | 21:40:02 |
| 30 Sep 2022 |
|  yaya joined the room. | 12:26:01 |
|  @lara:uwu.is left the room. | 12:36:09 |
|  /madonius[er|he] joined the room. | 21:11:36 |
| 1 Oct 2022 |
 @garionion:entr0py.de | hey, i want to convert my previous nixops config to a flake using colmena. however, as we have some shared config and custompackages in our infrastructure, i included the shared git repo as git submodule. however, when i want to deploy/update the servers with colmena, it does not find the file with the overlay config. my flake.nix looks like this: https://dev.paste42.de/FIPsp7Iu2e1OjV7V0RgWY89oZQ431zfZ | 18:17:29 |
| @garionion:entr0py.de | (everything under ./fem is the submodule | 18:17:49 |
| @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 |
