Updating input ref doesn't invalidate lockfile #10

Open
opened 2020-10-01 20:29:51 +00:00 by andir · 0 comments
andir commented 2020-10-01 20:29:51 +00:00 (Migrated from github.com)

Whenever I update an input in a flake.nix without actually updating the flake.lock the compat expression uses the input as specified in the lockfile. I think for consistency reasons it should fail during eval. Otherwise this might lead to an inconsistent state as users might forget to update the lockfile while the build succeeds.

Whenever I update an input in a `flake.nix` without actually updating the `flake.lock` the compat expression uses the input as specified in the lockfile. I think for consistency reasons it should fail during eval. Otherwise this might lead to an inconsistent state as users might forget to update the lockfile while the build succeeds.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/flake-compat#10
No description provided.