This program is experimental and its interface is subject to change.
nix registry pin - pin a flake to its current version or to the current version of a flake URL
nix registry pin [option...] url locked
nixpkgsto its most recent Git revision:
# nix registry pin nixpkgs
Afterwards the user registry will have an entry like this:
nix registry list | grep '^user ' user flake:nixpkgs github:NixOS/nixpkgs/925b70cd964ceaedee26fde9b19cc4c4f081196a
nix flake infowill say:
# nix flake info nixpkgs Resolved URL: github:NixOS/nixpkgs/925b70cd964ceaedee26fde9b19cc4c4f081196a Locked URL: github:NixOS/nixpkgs/925b70cd964ceaedee26fde9b19cc4c4f081196a …
nixpkgsin a custom registry to its most recent Git revision:
# nix registry pin --registry ./custom-flake-registry.json nixpkgs
This command adds an entry to the user registry that maps flake reference url to the corresponding locked flake reference, that is, a flake reference that specifies an exact revision or content hash. This ensures that until this registry entry is removed, all uses of url will resolve to exactly the same flake.
Entries can be removed using
nix registry remove.
The registry to operate on.
Pass the value expr as the argument name to Nix functions.
Pass the string string as the argument name to Nix functions.
Start an interactive environment if evaluation fails.
The URL of the Nix store to use for evaluation, i.e. to store derivations (
.drvfiles) and inputs referenced by them.
Allow access to mutable paths and repositories.
Add path to the Nix search path. The Nix search path is initialized from the colon-separated
NIX_PATHenvironment variable, and is used to look up the location of Nix expressions using paths enclosed in angle brackets (i.e.,
For instance, passing
-I /home/eelco/Dev -I /etc/nixos
will cause Nix to look for paths relative to
/etc/nixos, in that order. This is equivalent to setting the
NIX_PATHenvironment variable to
It is also possible to match paths against a prefix. For example, passing
-I nixpkgs=/home/eelco/Dev/nixpkgs-branch -I /etc/nixos
will cause Nix to search for
If a path in the Nix search path starts with
https://, it is interpreted as the URL of a tarball that will be downloaded and unpacked to a temporary location. The tarball must consist of a single top-level directory. For example, passing
tells Nix to download and use the current contents of the
masterbranch in the
The URLs of the tarballs from the official
nixos.orgchannels (see the manual page for
nix-channel) can be abbreviated as
channel:<channel-name>. For instance, the following two flags are equivalent:
-I nixpkgs=channel:nixos-21.05 -I nixpkgs=https://nixos.org/channels/nixos-21.05/nixexprs.tar.xz
You can also fetch source trees using flake URLs and add them to the search path. For instance,
specifies that the prefix
nixpkgsshall refer to the source tree downloaded from the
nixpkgsentry in the flake registry. Similarly,
<nixpkgs>refer to a particular branch of the
NixOS/nixpkgsrepository on GitHub.
Override the flake registries, redirecting original-ref to resolved-ref.
Set the logging verbosity level to 'debug'.
Set the format of log output; one of
Print full build logs on standard error.
Decrease the logging verbosity level.
Increase the logging verbosity level.
Show usage information.
Disable substituters and consider all previously downloaded files up-to-date.
Set the Nix configuration setting name to value (overriding
Consider all previously downloaded files out-of-date.
During evaluation, rewrite missing or corrupted files in the Nix store. During building, rebuild missing or corrupted store paths.
Show version information.
man nix.conffor overriding configuration settings with command line flags.