[Nix#9501] Locking error on 2.19 with path:. #93
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#93
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Upstream-Issue: NixOS/nix#9501
Describe the bug
When trying to lock a new flake input using 2.19 it complains about using a relative path:
Note that using the implicit
path:
works (either use just the.
withoutpath:
or nothing at all) since it seems to use the full path in these casesthough the docs seem to suggest that these should behave the same:
and of course since the error is about relative paths it works just fine with full paths and works as a workaround
Steps To Reproduce
path:.
Expected behavior
The docs state the following:
but it does not seem to be the case.
It is also regression compared to 2.18.1:
Additional context
I was specifically working inside of a git repo with untracked changes that I was trying to quickly test before committing.
Tried looking at the git blame, and to me it seems like #9239 might have introduced the issue.
Here it seems to assume that the path is always absolute, but I'm not confident enough with my knowledge of the nix code base to be 100% sure. The error might come from elsewhere and I'm just making a fool of myself here.
3d46fa85c8/src/libfetchers/path.cc (L90-L98)
Priorities
Add 👍 to issues you find important.