-
Notifications
You must be signed in to change notification settings - Fork 107
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 NUR input #347
Comments
This is a side effect of 3d3d6bb. Which makes it so that a local flake registry is created from all your inputs. So once you rebuild once and the flake registry gets created the next time you update your inputs they get set to paths in the nix store. The goal with that commit and the feature in fup is to allow you to easily do |
Absolutely, the custom registry comes handy sometimes. OTOH, when they shadow the normal one it breaks assumptions. Nix has a |
I agree, we should make this opt-in.
There has been some upstream work recently, let me check if I find it. Here, it is: NixOS/nix#4976 |
We no longer set the registry by default to all your inputs. Since that feature is now opt-in, I think we can close this. |
Expected Behavior
Running
flk update
on a DevOS machine should update thenur
input to the tip of the appropriate git branch.Current Behavior
flk update
idempotently converts the input to the equivalent path:/nix/store/xxx-source.Possible Solution
Explicitly specify
nur.url = "github:nix-community/nur"
, downside being that it is redundant- and silly-looking as well as fragile.Altternatively, fix this in a more general way, since this is the second time such an issue occurs (#142) which suggests there's an underlying issue.
Steps to Reproduce
nur
from the registryflake.lock
Context
I use NUR together with DevOS. I believe based on looking at the code that this issue is still present in
develop
.Your Environment
I use a system configuration based on the current tip of
core
. This phenomenon hit me on Friday at this commit but took me until today to realize.The text was updated successfully, but these errors were encountered: