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
I have been creating a clean directory tree derivation by only symlinking interpolated paths of the relevant subdirectories.
Nix files in one of the subdirectories import files from different subdirectory.
But since the subdirectory paths are interpolated, each subdirectory will end up as a separate store path.
Since 2.16, the imported path appears to be resolved relative to realpath in some cases, breaking the previously working code.
I think this new behaviour is better in terms of #2109 but it is still a regression and I was asked to report it.
error:
… while calling the 'import' builtin
at /home/jtojnar/Projects/nixpkgs-hammering/144-store/overlays/overlay.nix:1:1:
1| import ../lib
| ^
2|
error: getting status of '/home/jtojnar/Projects/nixpkgs-hammering/144-store/lib': No such file or directory
Expected behavior
No error should be produced.
Unless this regression is acceptable, since this error is sensible wrt #2109.
Describe the bug
I have been creating a clean directory tree derivation by only symlinking interpolated paths of the relevant subdirectories.
Nix files in one of the subdirectories import files from different subdirectory.
But since the subdirectory paths are interpolated, each subdirectory will end up as a separate store path.
Since 2.16, the imported path appears to be resolved relative to realpath in some cases, breaking the previously working code.
I think this new behaviour is better in terms of #2109 but it is still a regression and I was asked to report it.
I bisected the regression to 94812cc
Steps To Reproduce
Expected behavior
No error should be produced.
Unless this regression is acceptable, since this error is sensible wrt #2109.
nix-env --version
output2.18.1
Additional context
Discovered in jtojnar/nixpkgs-hammering#144
Priorities
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: