Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Do not require --allow-dirty-locks in pure fetchTree/fetchGit #12364

Open
roberth opened this issue Jan 27, 2025 · 0 comments
Open

Do not require --allow-dirty-locks in pure fetchTree/fetchGit #12364

roberth opened this issue Jan 27, 2025 · 0 comments
Assignees
@edolstra
Labels
regression Something doesn't work anymore

Comments

@roberth
Copy link
Member

roberth commented Jan 27, 2025

I only need to supply --allow-dirty-locks when writing the flake.lock?

No, currently you also need it when using the flake. But as I noted in the PR description, maybe we should lift this restriction.

Originally posted by @edolstra in #12220 (comment)
@roberth roberth added the regression Something doesn't work anymore label Jan 27, 2025
@edolstra edolstra self-assigned this Jan 28, 2025
edolstra added a commit to DeterminateSystems/nix-src that referenced this issue Jan 28, 2025
@edolstra
Allow use of lock files with unlocked entries as long as they have a …
09d563c 
…NAR hash

Fixes NixOS#12364.
@edolstra edolstra mentioned this issue Jan 28, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@edolstra edolstra

Labels
regression Something doesn't work anymore
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roberth @edolstra