New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nix develop nixpkgs#hello --unpack
is broken when nixpkgs
is a path ("Read-only filesystem")
#7361
Comments
cannot reproduce with |
Interestingly, it works when I use Here are the |
that is weird because I use separate nixpkgs registries for my system and user, and it still worked |
I can indeed reproduce it when That's because there's a logic to automatically Lines 563 to 566 in eece14d
That behaviour makes sense in combination with #5720 for running I think we could disable that at the very least when the flake is in the store. |
nix develop nixpkgs#hello --unpack
appears broken ("Read-only filesystem")nix develop nixpkgs#hello --unpack
is broken when nixpkgs
is a path ("Read-only filesystem")
Not stale, still happens as of |
Describe the bug
Running
nix develop nixpkgs#hello --unpack
to get an unpacked hello source directory gives me "Read-only filesystem" errors:Steps To Reproduce
nix develop nixpkgs#hello --unpack
Expected behavior
I'd expect to not see the "Read-only filesystem" errors and be dropped into a shell with access to the unpacked source.
nix-env --version
outputnix-env (Nix) 2.12.0pre20221116_561440b
(lazy trees branch, but also validated with the 2.11.0 release)Additional context
N/A.
The text was updated successfully, but these errors were encountered: