populate, krops writeDeploy: refer to generated flakes as path:

Generated flakes got locked with a bare nix flake lock in their directory,
and writeDeploy deployed them by their path.  Nix takes both for the
enclosing Git work tree, if the target directory lies in one, e.g. a home
directory kept in Git, and fails, because generated flakes aren't tracked
there.  Both refer to generated flakes as path: now.

An edge case deploys into a Git work tree, and the deploy test covers
deploying generated flakes.

0 files changed, 0 insertions, 0 deletions