Yeah I’m doing the same, I even tried to import a nonexistent file, and use build like you instead of switch, but I’m only getting the error from above.

What’s your nix version?

nix (Nix) 2.34.6

deleted by creator

I think we’re doing different things, that’s why it’s giving us completely different errors.

I just added files to imports in configuration.nix

I’m guessing you’ve got some manual error checking implemented with assertions?

error:
       … while calling the 'seq' builtin
         at «github:nixos/nixpkgs/4bd9165a9165d7b5e33ae57f3eecbcb28fb231c9?narHash=sha256-l/iNYDZ4bGOAFQY2q8y5OAfBBtrDAaPuRQqWaFHVRXM%3D»/lib/modules.nix:402:18:
          401|         options = checked options;
          402|         config = checked (removeAttrs config [ "_module" ]);
             |                  ^
          403|         _module = checked (config._module);

       … while evaluating a branch condition
         at «github:nixos/nixpkgs/4bd9165a9165d7b5e33ae57f3eecbcb28fb231c9?narHash=sha256-l/iNYDZ4bGOAFQY2q8y5OAfBBtrDAaPuRQqWaFHVRXM%3D»/lib/modules.nix:305:9:
          304|       checkUnmatched =
          305|         if config._module.check && config._module.freeformType == null && merged.unmatchedDefns != [ ] then
             |         ^
          306|           let

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: Path 'nix/bobo/test.nix' does not exist in Git repository "/home/bobo/dotfiles".
Command 'nix --extra-experimental-features 'nix-command flakes' build --print-out-paths '/home/bobo/dotfiles/nix#nixosConfigurations."bobo".config.system.build.nixos-rebuild' --no-link' returned non-zero exit status 1.

I can often only try to guess what’s wrong by reading the stacktrace top-to-bottom, so I’ve somewhat gotten used to doing that.

I’m yet to see any nix error be more readable top to bottom. And I think it’s intentionally designed that way so you don’t need to scroll up.

I actually thought, it said somewhere in there, that the file isn’t staged, but apparently not even that (anymore?).

It’s a different error. To me it looks like you tried to import a file that doesn’t exist. I made the file correctly and imported it, just didn’t git add it. After committing I switched without issues.

Only the modules/terminal/new_file.nix in the second-last line is relevant.

For me that error message was in the same spot. The rest of the trace is what was evaled so you got to that error. It’s the same principle as stack trace in other languages.

You don’t happen to be using Lix or something, do you?

No, unstable nixos + home-manager. The error above was from

sudo nixos-rebuild switch --flake ...

For me there was only 1 line beneath that error, it’s more visible than the warning. Maybe they improved it, or you started reading from the top?

I just completely forgot about that error because I have an extremely basic config.

Fortunately, your comment is not relevant at all since I incorrectly posted the warning instead of the explicit error:

error: Path 'path/to/file' in the repository "/path/to/repo" is not tracked by Git.

It even gives you

To make it visible to Nix, run:

git -C "/path/to/repo" add "path/to/file"

random pile of unclear errors

warning: Git tree ‘/path/to/repo’ is dirty