| 15 Apr 2025 |
 ststefa | Ah, I think I did a mess with systemd-boot (on the system) vs. grub (in my flake) | 19:31:07 |
 dish1892 | Did you use the hardware-config.nix from the system where you installed nix on? (With nixinfect) | 19:54:33 |
| ststefa | No, I didn‘t grasp that the colmena deployment process is entirely unrelated to the „nixos-rebuild approach. Now that makes sense. But it also means that I should somehow collect the /etc/nixos/configuration.nix plus imported files and base my colmenas input on that, no? Is there maybe a clever workflow to do that? Or is there a better approach? | 21:04:12 |
| ststefa | My goal would be to build a fully automated workflow which is agnostic to any pre-existing state/config | 21:09:14 |
| 16 Apr 2025 |
 dustee | i can build this configuration with nixos-rebuild but colmena throws infinite recursion, is there a way to fix it?
{
inputs,
...
}: {
imports = [
# this file configures some third party module and the imported function requires inputs as a consequence
(import "${inputs.my-flake}/modules-profiles/some-app-configs/default-with-inputs.nix")
];
… while evaluating the module argument `inputs'
error: infinite recursion encountered
| 22:21:50 |
| dustee | * i can build this nixos host configuration with nixos-rebuild but colmena throws infinite recursion, is there a way to fix it?
{
inputs,
...
}: {
imports = [
# this file configures some third party module and the imported function requires inputs as a consequence
(import "${inputs.my-flake}/modules-profiles/some-app-configs/default-with-inputs.nix")
];
… while evaluating the module argument `inputs'
error: infinite recursion encountered
| 22:22:00 |
| 18 Apr 2025 |
|  fabaff joined the room. | 18:03:45 |
| 19 Apr 2025 |
|  sako -w- left the room. | 17:36:43 |
| 20 Apr 2025 |
|  mannp changed their profile picture. | 20:22:14 |
| 21 Apr 2025 |
|  Tammi (ey/em) left the room. | 10:24:43 |
| 24 Apr 2025 |
|  Lan Tian joined the room. | 16:37:36 |
