Okay the fastest workaround I found for now is:

# build laptop's system on the server (a lot already built, doesn't take long)
server$ nix build .#nixosConfigurations.$LAPTOP.config.system.build.toplevel)"

# copy system manually from server to laptop
laptop$ nix copy --from ssh://server "$(nix eval --raw --apply builtins.toString .#nixosConfigurations."$(hostname)".config.system.build.toplevel)"
# then nixos-rebuild as usual
laptop$ nixos-rebuild --flake . --use-remote-sudo switch

@arianvp Would be nice if stack traces could be constricted to include/exclude specific paths.

- Paths within my git repo ... *very much* care about *all* of them
- Paths within nixpkgs ... *maybe* care about 4-8 frames

to find the error, you gotta sift through 500 lines of garbage. Makes iterating on NixOS a nightmare

`nixos-rebuild` should collapse irrelevant internal frames by default. If you need the whole trace use `nix build .#nixosConfigurations.host.config.system.build.toplevel`.

@itsfoss this is why @nixos_org exists
#nixos #nixosConfigurations #dotfiles #immutability