You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nix flake metadata command in the root fails like this:
error: found circular import of flake 'path:./a'
… while updating the flake input 'a/b'
… while updating the flake input 'a'
… while updating the lock file of flake 'path:/home/andi/.../a?narHash=....'
It is complaining about a circular import which isn't one. It appears as if the circular dependency detection is working based on the input string and not on some normalized absolute path.
Expected behavior
I would except to be able to nest flakes in a few directories to keep implementation details for packages in sub-flakes where they are being maintained.
nix-env --version output
nix-env (Nix) 2.4pre20210326_dd77f71
Additional context
There was an issue about circular dependencies that claims that they are now supported but apparently they are not supported anymore?
The text was updated successfully, but these errors were encountered:
Describe the bug
When I have a directory structure that has at least two directories with the same name nested in it where each of the folders contains a
flake.nix
:When given a minimal flake.nix for each of them (except for the last one in
a/a
) like this:The
nix flake metadata
command in the root fails like this:It is complaining about a circular import which isn't one. It appears as if the circular dependency detection is working based on the input string and not on some normalized absolute path.
Expected behavior
I would except to be able to nest flakes in a few directories to keep implementation details for packages in sub-flakes where they are being maintained.
nix-env --version
outputnix-env (Nix) 2.4pre20210326_dd77f71
Additional context
There was an issue about circular dependencies that claims that they are now supported but apparently they are not supported anymore?
The text was updated successfully, but these errors were encountered: