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

local flake registry freezes branches #142

Closed
bbjubjub2494 opened this issue Mar 1, 2021 · 0 comments · Fixed by #143
Closed

local flake registry freezes branches #142

bbjubjub2494 opened this issue Mar 1, 2021 · 0 comments · Fixed by #143
Labels
bug Something isn't working

Comments

@bbjubjub2494
Copy link
Contributor

Expected Behavior

Running flk update on a devos machine should update the nixos and override inputs to the tip of the appropriate git branches.

Current Behavior

flk update idempotently converts both inputs to the equivalent path:/nix/store/xxx-source.

Possible Solution

The two nix.registry entries generated by hosts/default.nix seem to be the problem: they effectively force any occurrence of nixpkgs or nixpkgs/release-20.09 to resolve to the specific store path at hand.

Steps to Reproduce

  1. get a on a devos machine
  2. try to update any flake that pulls in nixpkgs and/or nixpkgs/release-20.09
  3. observe commit message and contents of flake.lock

Context

Your Environment

I'm on 0.7 but I think it's still in master. Here's the commit where it happened.

@bbjubjub2494 bbjubjub2494 added the bug Something isn't working label Mar 1, 2021
@nrdxp nrdxp mentioned this issue Mar 1, 2021
@nrdxp nrdxp closed this as completed in #143 Mar 1, 2021
nrdxp added a commit that referenced this issue Mar 1, 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

Successfully merging a pull request may close this issue.

1 participant