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 don’t know whether that’s the cause of your issues, but nix build /some/path will indeed resolve to git+file:///some/path if /some/path is a git repository, or path:/some/path otherwise. Which I think makes perfect sense, because people (well, me at least) will expect nix build . to work regardless of whether I’m in a git repo or not, and to play with git if I’m in a git repo.
And having a way to explicitly specify path:FOO is also very handy for the 1% cases where I need to force the use of a plain path even if the path is a git repository.
The removed lines converted the flake path passed by the command line
from `/some/path` to `git+file:///some/path`.
This technically shouldn't cause any issues, however running
`nixos-rebuild switch` inside a directory `/nix/store` will cause the
switch to fail and leave a partially construct generation (see issue #144811
for details).
By itself this shouldn't be too much of an issue, however thanks to
another issue in `systemd-boot-builder.py` this can leave the system
in a broken state for those using `boot.loader.systemd-boot` (AFAIK the
default), where future `nixos-rebuild switch` will fail
(see issue #93694 for details).
The issue can be fixed by running
`nix-env -p /nix/var/nix/profiles/system --delete-generations old`,
however this makes newbies very confused and it is showing in our
support threads in Matrix and Discourse (see
https://discourse.nixos.org/t/need-help-on-failure-of-building-my-configuration/16842).
Keep in mind this is a workaround. The actual issue seems to be in nix
itself (see: NixOS/nix#5510).
See also #150065 for an alternative fix that caused other issues.
Kudos for @figsoda for figuring out this fix.
(cherry picked from commit c274d04)
Describe the bug
see: NixOS/nixpkgs#144811
It seems that
nix build FOO
does different things when FOO is~/some/path
vspath:~/some/path
.This might also explain another issue I found long ago, with nixos-rebuild: NixOS/nixpkgs#101648
This bug strikes me as odd, why is the path parsing code not being handled the same at this point when it's been guessed or specified as a path?
The text was updated successfully, but these errors were encountered: