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.

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

flk update fails because of obsolete flag #159

Closed
bbjubjub2494 opened this issue Mar 13, 2021 · 3 comments
Closed

flk update fails because of obsolete flag #159

bbjubjub2494 opened this issue Mar 13, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@bbjubjub2494
Copy link
Contributor

Expected Behavior

flk update goes smoothly

Current Behavior

[devshell]$ flk update
error: unrecognised flag '--recreate-lock-file'
Try 'nix --help' for more information.

Possible Solution

remove all 2 occurrences of this CLI flag

Steps to Reproduce

  1. clone/get devos
  2. Run flk update to get nix to the latest revision
  3. Restart the devShell
  4. Run flk update

Context

Went to flk update this morning on https://github.com/lourkeur/config (based off 0.7) and it didn't work. This also affects trunk.

Your Environment

NixOS 20.09 x86_64

@bbjubjub2494 bbjubjub2494 added the bug Something isn't working label Mar 13, 2021
@nrdxp
Copy link
Collaborator

nrdxp commented Mar 13, 2021

This flag still exists in the nixFlakes from nixpkgs master, which is what users will use by default. The latest nix from nix master has changed the semantics of the update command to make the --recreate-lock-file obsolete.

There have been quite a number of useful changes to Nix in the last few months, including improved documentation, so what I was planning on doing very soon, was to set the system nix from the nix flake instead of from nixpkgs so that users can enjoy all the latest changes. Once that's done, this will be resolved.

@Pacman99
Copy link
Member

Also if you update your flake, nix flake check will be failing for another day or so, because of a bug with aarch64 nixUnstable that results in it depending libcpuid, which doesn't evaluate for aarch64. The fix has been backported, but hydra hasn't gotten to it yet.

@nrdxp
Copy link
Collaborator

nrdxp commented Mar 15, 2021

fixed by d51cd34

@nrdxp nrdxp closed this as completed Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants