| 8 May 2024 |
 Charles | When using flakes and git, nix does not know files exist unless they are checked into git. Try running git add -AN and then trying again | 01:55:46 |
| Charles | * When using flakes and git, nix does not know files exist unless they are checked in or staged in git. Try running
`git add -AN` and then trying again | 01:56:42 |
 @mfed3:matrix.org | So my original config was a git repo but this one is not, I didn't realize it doesn't work at all without it being a git repo | 01:58:30 |
| @mfed3:matrix.org | Ok so can I just git init from that folder or do I need to delete the flake.nix and lock file and redo nix flake init? | 01:59:22 |
| Charles | If it's not a git repo then it should work | 02:00:04 |
| Charles | Make sure you didn't typo your paths in your nix code | 02:00:18 |
| Charles | Maybe try running git status to double check that it isn't a git repo | 02:01:09 |
| @mfed3:matrix.org | k I committed everything in there now, reran, same error | 02:03:08 |
| Charles | In reply to @charles:computer.surgery
Make sure you didn't typo your paths in your nix code Try this | 02:03:56 |
| Charles | The error looks like you wrote ./foo.nix but actually have ./bar.nix instead for example | 02:04:51 |
| Charles | That or it's not getting copied into the store, which would be the git thing | 02:05:15 |
| @mfed3:matrix.org | For modules, relative path to a folder from root of a flake would be ./hosts/file.nix not hosts/file.nix and no quotes around them in modules correct | 02:06:00 |
| @mfed3:matrix.org | Omg I'm a fuckin idiot, fatfingered a ../ in one of the imports 3 deep in one of the configs | 02:37:36 |
| @mfed3:matrix.org | Man the error messages are so useless lol | 02:37:57 |
| @mfed3:matrix.org | Thanks charles you were right after all :D | 02:39:01 |
| @mfed3:matrix.org | Works, system officially flakified | 02:44:24 |
 tomberek | That did not make a symlink? | 02:57:55 |
|  checooh joined the room. | 11:56:37 |
|  aszeszo joined the room. | 18:31:41 |
 @abmantis:abcosta.com | 
Download image.png | 21:28:47 |
| @abmantis:abcosta.com | it does, but still I just ran nix develop --profile ./nix-profile /home/acosta/dev/thirdparty/nix-environments#home-assistant and it fetched stuff before opening the environment | 21:29:24 |
| 9 May 2024 |
|  @theutz:matrix.org left the room. | 08:52:16 |
| @mfed3:matrix.org | Hey guys I have a question on autoupgrade, what does this actually do:
system.autoUpgrade = {
enable = true;
allowReboot = true;
flake = inputs.self.outPath;
flags = [ "--update-input" "nixpkgs" "--print-build-logs" ];
};
| 12:24:14 |
| @mfed3:matrix.org | Is that making the system run a nixos-rebuild switch automatically at 4:40 and build what is in the flake.lock | 12:25:09 |
| @mfed3:matrix.org | Or is that actually doing a nix flake update then building it | 12:25:43 |
|  remi-gelinas joined the room. | 13:25:37 |
|  Charles Hamilton joined the room. | 19:19:05 |
 @aidalgol:matrix.org | In reply to @mfed3:matrix.org
Hey guys I have a question on autoupgrade, what does this actually do:
system.autoUpgrade = {
enable = true;
allowReboot = true;
flake = inputs.self.outPath;
flags = [ "--update-input" "nixpkgs" "--print-build-logs" ];
};
Going by the description of system.autoUpgrade.flags, this will update the nixpkgs input to your system config flake.
If you are using flakes and use a local repo you can add [ "--update-input" "nixpkgs" "--commit-lock-file" ] to update nixpkgs.
| 20:40:24 |
| @aidalgol:matrix.org | You could also point system.autoUpgrade.flake to a remote flake (e.g. a git repo), and something else keeps that flake up to date, and the nixos-rebuild systemd job on your server will just apply the flake as-is. | 20:42:16 |
| @mfed3:matrix.org | It isn't very clear because I saw peoples usage on other websites saying they run it this way, and it will bump the lock file, meaning it blows past the lock file and changes the one on your local | 21:15:48 |
