FAQ/Pinning Nixpkgs - Revision history

Sandro: Drop pre nix 2.0, warn about negatives of pinning

2025-10-21T14:20:30Z

Drop pre nix 2.0, warn about negatives of pinning

@@ Line 8: / Line 8: @@
 Note: You can <code>sudo nix-channel --remove nixpkgs</code>, but you still need a nix-channel for nixos
 <pre>
@@ Line 13: / Line 15: @@
 nixos https://nixos.org/channels/nixos-21.05
 </pre>
 Nix 2.0 introduces new builtins, <code>fetchTarball</code> and <code>fetchGit</code>, which make it possible to fetch a specific version of nixpkgs without depending on an existing one:
@@ Line 29: / Line 29: @@
 </syntaxhighlight>
-Or, to use git for fetching<!-- (this has the advantage of being somewhat faster for updates, but is slower for the initial fetch) [not true anymore, the repository sharing mechanism has been disabled (https://github.com/NixOS/nix/pull/2358)]-->:
+Or, to use git for fetching:
 <syntaxhighlight lang="nix">
@@ Line 51: / Line 51: @@
 while evaluating anonymous function at /nix/store/b93cq865x6qxpn4dw9ivrk3yjcsm8r97-nixos-19.09/pkgs/stdenv/generic/make-derivation.nix:142:17, called from undefined position:
 program 'git' failed with exit code 128
 </syntaxhighlight>

Vater at 18:47, 11 July 2025

2025-07-11T18:47:21Z

← Older revision		Revision as of 18:47, 11 July 2025
Line 235:		Line 235:
	== See also ==		== See also ==

	- [https://nix.dev/reference/pinning-nixpkgs Pinning Nixpkgs]		* [https://nix.dev/reference/pinning-nixpkgs Pinning Nixpkgs]
			* [https://nix.dev/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs Towards Reproducibility: Pinning Nixpkgs]
	- [https://nix.dev/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs Towards Reproducibility: Pinning Nixpkgs]		* [https://nix.dev/guides/recipes/dependency-management.html Dependency Management]

	- [https://nix.dev/guides/recipes/dependency-management.html Dependency Management]

SigmaSquadron: FAQ Breadcrumb

2025-04-17T17:05:56Z

FAQ Breadcrumb

← Older revision		Revision as of 17:05, 17 April 2025
Line 1:		Line 1:
			{{FAQ/breadcrumb}}
	It is possible (and indeed, fairly easy) to pin a specific version of		It is possible (and indeed, fairly easy) to pin a specific version of
	Nixpkgs. This can be used to upgrade individual applications		Nixpkgs. This can be used to upgrade individual applications

Niklas Korz: Improve indentation of systemd example

2025-01-04T21:16:45Z

Improve indentation of systemd example

← Older revision		Revision as of 21:16, 4 January 2025
Line 183:		Line 183:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	environment.systemPackages = with pkgs; [		environment.systemPackages = with pkgs; [
	unstable.bind		unstable.bind
	unstable.dnsutils		unstable.dnsutils
	vim		vim
	];		];
	</syntaxhighlight>		</syntaxhighlight>

Line 195:		Line 195:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	services.bind.enable = true;		services.bind.enable = true;
	...		...
	</syntaxhighlight>		</syntaxhighlight>

Line 204:		Line 204:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	users.users.named =		users.users.named = {
	{ uid = config.ids.uids.bind;		uid = config.ids.uids.bind;
	description = "BIND daemon user";		description = "BIND daemon user";
	};		};
	systemd.services.mybind = {		systemd.services.mybind = {
	description = "BIND Domain Name Server";		description = "BIND Domain Name Server";
	unitConfig.Documentation = "man:named(8)";		unitConfig.Documentation = "man:named(8)";
	after = [ "network.target" ];		after = [ "network.target" ];
	wantedBy = [ "multi-user.target" ];		wantedBy = [ "multi-user.target" ];
	preStart = ''		preStart = ''
	mkdir -m 0755 -p /etc/bind		mkdir -m 0755 -p /etc/bind
	if ! [ -f "/etc/bind/rndc.key" ]; then		if ! [ -f "/etc/bind/rndc.key" ]; then
	${pkgs.unstable.bind.out}/sbin/rndc-confgen -c /etc/bind/rndc.key -u named -a -A hmac-sha256 2>/dev/null		${pkgs.unstable.bind.out}/sbin/rndc-confgen -c /etc/bind/rndc.key -u named -a -A hmac-sha256 2>/dev/null
	fi		fi
	${pkgs.coreutils}/bin/mkdir -p /run/named		${pkgs.coreutils}/bin/mkdir -p /run/named
	chown named /run/named		chown named /run/named
	'';		'';
	serviceConfig = {		serviceConfig = {
	ExecStart = "${pkgs.unstable.bind.out}/sbin/named -u named -4 -c /etc/bind/named.conf -f";		ExecStart = "${pkgs.unstable.bind.out}/sbin/named -u named -4 -c /etc/bind/named.conf -f";
	ExecReload = "${pkgs.unstable.bind.out}/sbin/rndc -k '/etc/bind/rndc.key' reload";		ExecReload = "${pkgs.unstable.bind.out}/sbin/rndc -k '/etc/bind/rndc.key' reload";
	ExecStop = "${pkgs.unstable.bind.out}/sbin/rndc -k '/etc/bind/rndc.key' stop";		ExecStop = "${pkgs.unstable.bind.out}/sbin/rndc -k '/etc/bind/rndc.key' stop";
	};		};

	};		};
	</syntaxhighlight>		</syntaxhighlight>

AndersonTorres at 01:01, 13 June 2024

2024-06-13T01:01:28Z

← Older revision		Revision as of 01:01, 13 June 2024
Line 236:		Line 236:

	- [https://nix.dev/reference/pinning-nixpkgs Pinning Nixpkgs]		- [https://nix.dev/reference/pinning-nixpkgs Pinning Nixpkgs]

	- [https://nix.dev/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs Towards Reproducibility: Pinning Nixpkgs]		- [https://nix.dev/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs Towards Reproducibility: Pinning Nixpkgs]

	- [https://nix.dev/guides/recipes/dependency-management.html Dependency Management]		- [https://nix.dev/guides/recipes/dependency-management.html Dependency Management]

AndersonTorres at 01:01, 13 June 2024

2024-06-13T01:01:09Z

← Older revision		Revision as of 01:01, 13 June 2024
Line 235:		Line 235:
	== See also ==		== See also ==

	[https://nix.dev/reference/pinning-nixpkgs Pinning Nixpkgs]		- [https://nix.dev/reference/pinning-nixpkgs Pinning Nixpkgs]
	[https://nix.dev/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs Towards Reproducibility: Pinning Nixpkgs]		- [https://nix.dev/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs Towards Reproducibility: Pinning Nixpkgs]
	[https://nix.dev/guides/recipes/dependency-management.html Dependency Management]		- [https://nix.dev/guides/recipes/dependency-management.html Dependency Management]

AndersonTorres: nix.dev references

2024-06-13T01:00:48Z

nix.dev references

← Older revision		Revision as of 01:00, 13 June 2024
Line 232:		Line 232:
	where all the stuff just comes from the bind services definition(which you can get from the source link on the nixos options page.)		where all the stuff just comes from the bind services definition(which you can get from the source link on the nixos options page.)
	Just replace named variables, and replace <code>${pkgs.bind.out</code> with <code>${pkgs.unstable.bind.out}</code>		Just replace named variables, and replace <code>${pkgs.bind.out</code> with <code>${pkgs.unstable.bind.out}</code>

			== See also ==

			[https://nix.dev/reference/pinning-nixpkgs Pinning Nixpkgs]
			[https://nix.dev/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs Towards Reproducibility: Pinning Nixpkgs]
			[https://nix.dev/guides/recipes/dependency-management.html Dependency Management]

imported>Eyeinsky: /* Pinning an unstable service */

2024-01-02T19:54:41Z

Pinning an unstable service

← Older revision		Revision as of 19:54, 2 January 2024
Line 157:		Line 157:
	How to upgrade a single package and service to an unstable version		How to upgrade a single package and service to an unstable version

	There is probably a better way, especially once flakes come around. Some packages let you specify which <code>package</code> to run as an option but most don't. The following is a generic way for those which don't:		There is probably a better way, especially once flakes come around. Some packages let you specify which <code>package</code> to run as an option but most don't. The following is a generic way that also works for those which don't.

	add to configuration.nix a set allowing unstable packages.		add to configuration.nix a set allowing unstable packages.

imported>Eyeinsky: /* Pinning an unstable service */

2024-01-02T19:53:23Z

Pinning an unstable service

← Older revision		Revision as of 19:53, 2 January 2024
Line 157:		Line 157:
	How to upgrade a single package and service to an unstable version		How to upgrade a single package and service to an unstable version

	There is probably a better way, especially once flakes ~~comes~~ around. Some packages, let you specify which <code>package</code> to run as an option ~~for instance. Most~~ don't ~~in my experience~~. ~~This~~ is ~~how you do it~~ for ~~one that doesn~~'t.		There is probably a better way, especially once flakes come around. Some packages let you specify which <code>package</code> to run as an option but most don't. The following is a generic way for those which don't:

	add to configuration.nix a set allowing unstable packages.		add to configuration.nix a set allowing unstable packages.

imported>Legendofmiracles: Add note about https://lazamar.co.uk/nix-versions/

2021-11-20T15:16:39Z

Add note about https://lazamar.co.uk/nix-versions/

← Older revision		Revision as of 15:16, 20 November 2021
Line 3:		Line 3:
	separately on their own terms, and to ensure their deployability is		separately on their own terms, and to ensure their deployability is
	not impacted by other systems' requirements.		not impacted by other systems' requirements.

			Another reason why one would want to pin nixpkgs is to get older versions of a specific software. [https://lazamar.co.uk/nix-versions/ This site] can show you all the versions a package went through, and what nixpkgs revision to use to get your specific version.

	Note: You can <code>sudo nix-channel --remove nixpkgs</code>, but you still need a nix-channel for nixos		Note: You can <code>sudo nix-channel --remove nixpkgs</code>, but you still need a nix-channel for nixos