diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 3d4bb049991f..5f21df834d56 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -26,7 +26,6 @@ For new packages please briefly describe the package or provide a link to its ho
- [ ] (Package updates) Added a release notes entry if the change is major or breaking
- [ ] (Module updates) Added a release notes entry if the change is significant
- [ ] (Module addition) Added a release notes entry if adding a new NixOS module
- - [ ] (Release notes changes) Ran `nixos/doc/manual/md-to-db.sh` to update generated release notes
- [ ] Fits [CONTRIBUTING.md](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md).
-Documentation in nixpkgs is transitioning to a markdown-centric workflow. Release notes now require a translation step to convert from markdown to a compatible docbook document.
+Documentation in nixpkgs is transitioning to a markdown-centric workflow. In the past release notes required a translation step to convert from markdown to a compatible docbook document, but this is no longer necessary.
Steps for updating 23.05 Release notes:
1. Edit `nixos/doc/manual/release-notes/rl-2305.section.md` with the desired changes
-2. Run `./nixos/doc/manual/md-to-db.sh` to render `nixos/doc/manual/from_md/release-notes/rl-2305.section.xml`
-3. Include changes to `rl-2305.section.md` and `rl-2305.section.xml` in the same commit.
+2. Commit changes to `rl-2305.section.md`.
## Reviewing contributions
diff --git a/doc/Makefile b/doc/Makefile
index 1e54aef9bd12..ee98a3ee9213 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -3,7 +3,7 @@ MD_TARGETS=$(addsuffix .xml, $(basename $(shell find . -type f -regex '.*\.md$$'
PANDOC ?= pandoc
pandoc_media_dir = media
-# NOTE: Keep in sync with NixOS manual (/nixos/doc/manual/md-to-db.sh) and conversion script (/maintainers/scripts/db-to-md.sh).
+# NOTE: Keep in sync with conversion script (/maintainers/scripts/db-to-md.sh).
# TODO: Remove raw-attribute when we can get rid of DocBook altogether.
pandoc_commonmark_enabled_extensions = +attributes+fenced_divs+footnotes+bracketed_spans+definition_lists+pipe_tables+raw_attribute
# Not needed:
diff --git a/doc/build-aux/pandoc-filters/docbook-writer/html-elements.lua b/doc/build-aux/pandoc-filters/docbook-writer/html-elements.lua
deleted file mode 100644
index 8f4de40ce5f8..000000000000
--- a/doc/build-aux/pandoc-filters/docbook-writer/html-elements.lua
+++ /dev/null
@@ -1,11 +0,0 @@
---[[
-Converts some HTML elements commonly used in Markdown to corresponding DocBook elements.
-]]
-
-function RawInline(elem)
- if elem.format == 'html' and elem.text == '' then
- return pandoc.RawInline('docbook', '')
- elseif elem.format == 'html' and elem.text == '' then
- return pandoc.RawInline('docbook', '')
- end
-end
diff --git a/doc/hooks/breakpoint.section.md b/doc/hooks/breakpoint.section.md
index 41e50653e91d..9600e06b7934 100644
--- a/doc/hooks/breakpoint.section.md
+++ b/doc/hooks/breakpoint.section.md
@@ -10,9 +10,7 @@ nativeBuildInputs = [ breakpointHook ];
When a build failure happens there will be an instruction printed that shows how to attach with `cntr` to the build sandbox.
::: {.note}
-::: {.title}
Caution with remote builds
-:::
This won’t work with remote builds as the build environment is on a different machine and can’t be accessed by `cntr`. Remote builds can be turned off by setting `--option builders ''` for `nix-build` or `--builders ''` for `nix build`.
:::
diff --git a/nixos/doc/manual/configuration/modularity.section.md b/nixos/doc/manual/configuration/modularity.section.md
index 3395ace20c4f..2eff15387987 100644
--- a/nixos/doc/manual/configuration/modularity.section.md
+++ b/nixos/doc/manual/configuration/modularity.section.md
@@ -67,7 +67,13 @@ When using multiple modules, you may need to access configuration values
defined in other modules. This is what the `config` function argument is
for: it contains the complete, merged system configuration. That is,
`config` is the result of combining the configurations returned by every
-module [^1] . For example, here is a module that adds some packages to
+module. (If you're wondering how it's possible that the (indirect) *result*
+of a function is passed as an *input* to that same function: that's
+because Nix is a "lazy" language --- it only computes values when
+they are needed. This works as long as no individual configuration
+value depends on itself.)
+
+For example, here is a module that adds some packages to
[](#opt-environment.systemPackages) only if
[](#opt-services.xserver.enable) is set to `true` somewhere else:
@@ -125,9 +131,3 @@ in
{ imports = [ (netConfig "nixos.localdomain") ]; }
```
-
-[^1]: If you're wondering how it's possible that the (indirect) *result*
- of a function is passed as an *input* to that same function: that's
- because Nix is a "lazy" language --- it only computes values when
- they are needed. This works as long as no individual configuration
- value depends on itself.
diff --git a/nixos/doc/manual/configuration/sshfs-file-systems.section.md b/nixos/doc/manual/configuration/sshfs-file-systems.section.md
index 4dd1b203a249..d8c9dea6c337 100644
--- a/nixos/doc/manual/configuration/sshfs-file-systems.section.md
+++ b/nixos/doc/manual/configuration/sshfs-file-systems.section.md
@@ -8,7 +8,7 @@ It means that if you have SSH access to a machine, no additional setup is needed
## Interactive mounting {#sec-sshfs-interactive}
-In NixOS, SSHFS is packaged as sshfs.
+In NixOS, SSHFS is packaged as `sshfs`.
Once installed, mounting a directory interactively is simple as running:
```ShellSession
$ sshfs my-user@example.com:/my-dir /mnt/my-dir
diff --git a/nixos/doc/manual/configuration/x-windows.chapter.md b/nixos/doc/manual/configuration/x-windows.chapter.md
index be185cf4c314..bef35f448874 100644
--- a/nixos/doc/manual/configuration/x-windows.chapter.md
+++ b/nixos/doc/manual/configuration/x-windows.chapter.md
@@ -69,7 +69,7 @@ Wine, you should also set the following:
hardware.opengl.driSupport32Bit = true;
```
-## Auto-login {#sec-x11-auto-login .unnumbered}
+## Auto-login {#sec-x11-auto-login}
The x11 login screen can be skipped entirely, automatically logging you
into your window manager and desktop environment when you boot your
@@ -96,7 +96,7 @@ services.xserver.displayManager.autoLogin.enable = true;
services.xserver.displayManager.autoLogin.user = "alice";
```
-## Intel Graphics drivers {#sec-x11--graphics-cards-intel .unnumbered}
+## Intel Graphics drivers {#sec-x11--graphics-cards-intel}
There are two choices for Intel Graphics drivers in X.org: `modesetting`
(included in the xorg-server itself) and `intel` (provided by the
@@ -136,7 +136,7 @@ services.xserver.deviceSection = ''
Note that this will likely downgrade the performance compared to
`modesetting` or `intel` with DRI 3 (default).
-## Proprietary NVIDIA drivers {#sec-x11-graphics-cards-nvidia .unnumbered}
+## Proprietary NVIDIA drivers {#sec-x11-graphics-cards-nvidia}
NVIDIA provides a proprietary driver for its graphics cards that has
better 3D performance than the X.org drivers. It is not enabled by
@@ -158,7 +158,7 @@ services.xserver.videoDrivers = [ "nvidiaLegacy304" ];
You may need to reboot after enabling this driver to prevent a clash
with other kernel modules.
-## Proprietary AMD drivers {#sec-x11--graphics-cards-amd .unnumbered}
+## Proprietary AMD drivers {#sec-x11--graphics-cards-amd}
AMD provides a proprietary driver for its graphics cards that is not
enabled by default because it's not Free Software, is often broken in
@@ -173,7 +173,7 @@ services.xserver.videoDrivers = [ "amdgpu-pro" ];
You will need to reboot after enabling this driver to prevent a clash
with other kernel modules.
-## Touchpads {#sec-x11-touchpads .unnumbered}
+## Touchpads {#sec-x11-touchpads}
Support for Synaptics touchpads (found in many laptops such as the Dell
Latitude series) can be enabled as follows:
@@ -192,7 +192,7 @@ services.xserver.libinput.touchpad.tapping = false;
Note: the use of `services.xserver.synaptics` is deprecated since NixOS
17.09.
-## GTK/Qt themes {#sec-x11-gtk-and-qt-themes .unnumbered}
+## GTK/Qt themes {#sec-x11-gtk-and-qt-themes}
GTK themes can be installed either to user profile or system-wide (via
`environment.systemPackages`). To make Qt 5 applications look similar to
@@ -204,7 +204,7 @@ qt.platformTheme = "gtk2";
qt.style = "gtk2";
```
-## Custom XKB layouts {#custom-xkb-layouts .unnumbered}
+## Custom XKB layouts {#custom-xkb-layouts}
It is possible to install custom [ XKB
](https://en.wikipedia.org/wiki/X_keyboard_extension) keyboard layouts
diff --git a/nixos/doc/manual/configuration/xfce.chapter.md b/nixos/doc/manual/configuration/xfce.chapter.md
index 60771b36fa9c..a80be2b523e2 100644
--- a/nixos/doc/manual/configuration/xfce.chapter.md
+++ b/nixos/doc/manual/configuration/xfce.chapter.md
@@ -24,7 +24,7 @@ Some Xfce programs are not installed automatically. To install them
manually (system wide), put them into your
[](#opt-environment.systemPackages) from `pkgs.xfce`.
-## Thunar {#sec-xfce-thunar-plugins .unnumbered}
+## Thunar {#sec-xfce-thunar-plugins}
Thunar (the Xfce file manager) is automatically enabled when Xfce is
enabled. To enable Thunar without enabling Xfce, use the configuration
@@ -35,7 +35,7 @@ If you'd like to add extra plugins to Thunar, add them to
[](#opt-programs.thunar.plugins). You shouldn't just add them to
[](#opt-environment.systemPackages).
-## Troubleshooting {#sec-xfce-troubleshooting .unnumbered}
+## Troubleshooting {#sec-xfce-troubleshooting}
Even after enabling udisks2, volume management might not work. Thunar
and/or the desktop takes time to show up. Thunar will spit out this kind
diff --git a/nixos/doc/manual/contributing-to-this-manual.chapter.md b/nixos/doc/manual/contributing-to-this-manual.chapter.md
index 557599809222..c306cc084cdb 100644
--- a/nixos/doc/manual/contributing-to-this-manual.chapter.md
+++ b/nixos/doc/manual/contributing-to-this-manual.chapter.md
@@ -6,7 +6,6 @@ You can quickly check your edits with the following:
```ShellSession
$ cd /path/to/nixpkgs
-$ ./nixos/doc/manual/md-to-db.sh
$ nix-build nixos/release.nix -A manual.x86_64-linux
```
diff --git a/nixos/doc/manual/default.nix b/nixos/doc/manual/default.nix
index 9dab1738abed..e0bcec1ea6b5 100644
--- a/nixos/doc/manual/default.nix
+++ b/nixos/doc/manual/default.nix
@@ -68,12 +68,34 @@ let
optionIdPrefix = "test-opt-";
};
- sources = lib.sourceFilesBySuffices ./. [".xml"];
+ sources = runCommand "manual-sources" {
+ inputs = lib.sourceFilesBySuffices ./. [ ".xml" ".md" ];
+ nativeBuildInputs = [ pkgs.nixos-render-docs ];
+ } ''
+ mkdir $out
+ cd $out
+ cp -r --no-preserve=all $inputs/* .
+
+ declare -a convert_args
+ while read -r mf; do
+ if [[ "$mf" = *.chapter.md ]]; then
+ convert_args+=("--chapter")
+ else
+ convert_args+=("--section")
+ fi
+
+ convert_args+=("from_md/''${mf%.md}.xml" "$mf")
+ done < <(find . -type f -name '*.md')
+
+ nixos-render-docs manual docbook-fragment \
+ --manpage-urls ${manpageUrls} \
+ "''${convert_args[@]}"
+ '';
modulesDoc = runCommand "modules.xml" {
nativeBuildInputs = [ pkgs.nixos-render-docs ];
} ''
- nixos-render-docs manual docbook \
+ nixos-render-docs manual docbook-section \
--manpage-urls ${manpageUrls} \
"$out" \
--section \
@@ -255,8 +277,7 @@ in rec {
# Generate the NixOS manpages.
manpages = runCommand "nixos-manpages"
- { inherit sources;
- nativeBuildInputs = [
+ { nativeBuildInputs = [
buildPackages.installShellFiles
] ++ lib.optionals allowDocBook [
buildPackages.libxml2.bin
diff --git a/nixos/doc/manual/development/freeform-modules.section.md b/nixos/doc/manual/development/freeform-modules.section.md
index 10e876b96d59..514a06f97ee7 100644
--- a/nixos/doc/manual/development/freeform-modules.section.md
+++ b/nixos/doc/manual/development/freeform-modules.section.md
@@ -13,9 +13,8 @@ checking for entire option trees, it is only recommended for use in
submodules.
::: {#ex-freeform-module .example}
-::: {.title}
**Example: Freeform submodule**
-:::
+
The following shows a submodule assigning a freeform type that allows
arbitrary attributes with `str` values below `settings`, but also
declares an option for the `settings.port` attribute to have it
diff --git a/nixos/doc/manual/development/option-declarations.section.md b/nixos/doc/manual/development/option-declarations.section.md
index 18ec7ba903a9..59470bf1bc11 100644
--- a/nixos/doc/manual/development/option-declarations.section.md
+++ b/nixos/doc/manual/development/option-declarations.section.md
@@ -87,6 +87,7 @@ lib.mkOption {
description = lib.mdDoc "Whether to enable magic.";
}
```
+:::
### `mkPackageOption`, `mkPackageOptionMD` {#sec-option-declarations-util-mkPackageOption}
@@ -108,7 +109,7 @@ You can omit the default path if the name of the option is also attribute path i
During the transition to CommonMark documentation `mkPackageOption` creates an option with a DocBook description attribute, once the transition is completed it will create a CommonMark description instead. `mkPackageOptionMD` always creates an option with a CommonMark description attribute and will be removed some time after the transition is completed.
-::: {#ex-options-declarations-util-mkPackageOption .title}
+[]{#ex-options-declarations-util-mkPackageOption}
Examples:
::: {#ex-options-declarations-util-mkPackageOption-hello .example}
@@ -122,6 +123,7 @@ lib.mkOption {
description = lib.mdDoc "The hello package to use.";
}
```
+:::
::: {#ex-options-declarations-util-mkPackageOption-ghc .example}
```nix
@@ -138,6 +140,7 @@ lib.mkOption {
description = lib.mdDoc "The GHC package to use.";
}
```
+:::
## Extensible Option Types {#sec-option-declarations-eot}
@@ -186,9 +189,7 @@ changing the main service module file and the type system automatically
enforces that there can only be a single display manager enabled.
::: {#ex-option-declaration-eot-service .example}
-::: {.title}
**Example: Extensible type placeholder in the service module**
-:::
```nix
services.xserver.displayManager.enable = mkOption {
description = "Display manager to use";
@@ -198,9 +199,7 @@ services.xserver.displayManager.enable = mkOption {
:::
::: {#ex-option-declaration-eot-backend-gdm .example}
-::: {.title}
**Example: Extending `services.xserver.displayManager.enable` in the `gdm` module**
-:::
```nix
services.xserver.displayManager.enable = mkOption {
type = with types; nullOr (enum [ "gdm" ]);
@@ -209,9 +208,7 @@ services.xserver.displayManager.enable = mkOption {
:::
::: {#ex-option-declaration-eot-backend-sddm .example}
-::: {.title}
**Example: Extending `services.xserver.displayManager.enable` in the `sddm` module**
-:::
```nix
services.xserver.displayManager.enable = mkOption {
type = with types; nullOr (enum [ "sddm" ]);
diff --git a/nixos/doc/manual/development/option-def.section.md b/nixos/doc/manual/development/option-def.section.md
index 22cf38873cf0..6a3dc26b99be 100644
--- a/nixos/doc/manual/development/option-def.section.md
+++ b/nixos/doc/manual/development/option-def.section.md
@@ -12,7 +12,7 @@ config = {
However, sometimes you need to wrap an option definition or set of
option definitions in a *property* to achieve certain effects:
-## Delaying Conditionals {#sec-option-definitions-delaying-conditionals .unnumbered}
+## Delaying Conditionals {#sec-option-definitions-delaying-conditionals}
If a set of option definitions is conditional on the value of another
option, you may need to use `mkIf`. Consider, for instance:
@@ -56,7 +56,7 @@ config = {
};
```
-## Setting Priorities {#sec-option-definitions-setting-priorities .unnumbered}
+## Setting Priorities {#sec-option-definitions-setting-priorities}
A module can override the definitions of an option in other modules by
setting an *override priority*. All option definitions that do not have the lowest
@@ -72,7 +72,7 @@ This definition causes all other definitions with priorities above 10 to
be discarded. The function `mkForce` is equal to `mkOverride 50`, and
`mkDefault` is equal to `mkOverride 1000`.
-## Ordering Definitions {#sec-option-definitions-ordering .unnumbered}
+## Ordering Definitions {#sec-option-definitions-ordering}
It is also possible to influence the order in which the definitions for an option are
merged by setting an *order priority* with `mkOrder`. The default order priority is 1000.
@@ -89,7 +89,7 @@ definitions in the final list value of `hardware.firmware`.
Note that this is different from [override priorities](#sec-option-definitions-setting-priorities):
setting an order does not affect whether the definition is included or not.
-## Merging Configurations {#sec-option-definitions-merging .unnumbered}
+## Merging Configurations {#sec-option-definitions-merging}
In conjunction with `mkIf`, it is sometimes useful for a module to
return multiple sets of option definitions, to be merged together as if
diff --git a/nixos/doc/manual/development/option-types.section.md b/nixos/doc/manual/development/option-types.section.md
index 0e9c4a4d16be..51977c58333f 100644
--- a/nixos/doc/manual/development/option-types.section.md
+++ b/nixos/doc/manual/development/option-types.section.md
@@ -36,9 +36,8 @@ merging is handled.
together. This type is recommended when the option type is unknown.
::: {#ex-types-anything .example}
- ::: {.title}
**Example: `types.anything` Example**
- :::
+
Two definitions of this type like
```nix
@@ -357,9 +356,7 @@ you will still need to provide a default value (e.g. an empty attribute set)
if you want to allow users to leave it undefined.
::: {#ex-submodule-direct .example}
-::: {.title}
**Example: Directly defined submodule**
-:::
```nix
options.mod = mkOption {
description = "submodule example";
@@ -378,9 +375,7 @@ options.mod = mkOption {
:::
::: {#ex-submodule-reference .example}
-::: {.title}
**Example: Submodule defined as a reference**
-:::
```nix
let
modOptions = {
@@ -408,9 +403,7 @@ multiple definitions of the submodule option set
([Example: Definition of a list of submodules](#ex-submodule-listof-definition)).
::: {#ex-submodule-listof-declaration .example}
-::: {.title}
**Example: Declaration of a list of submodules**
-:::
```nix
options.mod = mkOption {
description = "submodule example";
@@ -429,9 +422,7 @@ options.mod = mkOption {
:::
::: {#ex-submodule-listof-definition .example}
-::: {.title}
**Example: Definition of a list of submodules**
-:::
```nix
config.mod = [
{ foo = 1; bar = "one"; }
@@ -446,9 +437,7 @@ multiple named definitions of the submodule option set
([Example: Definition of attribute sets of submodules](#ex-submodule-attrsof-definition)).
::: {#ex-submodule-attrsof-declaration .example}
-::: {.title}
**Example: Declaration of attribute sets of submodules**
-:::
```nix
options.mod = mkOption {
description = "submodule example";
@@ -467,9 +456,7 @@ options.mod = mkOption {
:::
::: {#ex-submodule-attrsof-definition .example}
-::: {.title}
**Example: Definition of attribute sets of submodules**
-:::
```nix
config.mod.one = { foo = 1; bar = "one"; };
config.mod.two = { foo = 2; bar = "two"; };
@@ -489,9 +476,8 @@ Types are mainly characterized by their `check` and `merge` functions.
([Example: Overriding a type check](#ex-extending-type-check-2)).
::: {#ex-extending-type-check-1 .example}
- ::: {.title}
**Example: Adding a type check**
- :::
+
```nix
byte = mkOption {
description = "An integer between 0 and 255.";
@@ -501,9 +487,8 @@ Types are mainly characterized by their `check` and `merge` functions.
:::
::: {#ex-extending-type-check-2 .example}
- ::: {.title}
**Example: Overriding a type check**
- :::
+
```nix
nixThings = mkOption {
description = "words that start with 'nix'";
diff --git a/nixos/doc/manual/development/settings-options.section.md b/nixos/doc/manual/development/settings-options.section.md
index 334149d021cb..476ba4b03f9d 100644
--- a/nixos/doc/manual/development/settings-options.section.md
+++ b/nixos/doc/manual/development/settings-options.section.md
@@ -119,9 +119,8 @@ have a predefined type and string generator already declared under
default Elixir keyword list
-::: {#pkgs-formats-result}
+[]{#pkgs-formats-result}
These functions all return an attribute set with these values:
-:::
`type`
@@ -144,9 +143,8 @@ These functions all return an attribute set with these values:
:::
::: {#ex-settings-nix-representable .example}
-::: {.title}
**Example: Module with conventional `settings` option**
-:::
+
The following shows a module for an example program that uses a JSON
configuration file. It demonstrates how above values can be used, along
with some other related best practices. See the comments for
@@ -220,9 +218,7 @@ the port, which will enforce it to be a valid integer and make it show
up in the manual.
::: {#ex-settings-typed-attrs .example}
-::: {.title}
**Example: Declaring a type-checked `settings` attribute**
-:::
```nix
settings = lib.mkOption {
type = lib.types.submodule {
diff --git a/nixos/doc/manual/development/writing-modules.chapter.md b/nixos/doc/manual/development/writing-modules.chapter.md
index fa24679b7fc8..a0ec4a5df96e 100644
--- a/nixos/doc/manual/development/writing-modules.chapter.md
+++ b/nixos/doc/manual/development/writing-modules.chapter.md
@@ -37,9 +37,7 @@ options, but does not declare any. The structure of full NixOS modules
is shown in [Example: Structure of NixOS Modules](#ex-module-syntax).
::: {#ex-module-syntax .example}
-::: {.title}
**Example: Structure of NixOS Modules**
-:::
```nix
{ config, pkgs, ... }:
@@ -102,9 +100,7 @@ Exec directives](#exec-escaping-example) for an example. When using these
functions system environment substitution should *not* be disabled explicitly.
::: {#locate-example .example}
-::: {.title}
**Example: NixOS Module for the "locate" Service**
-:::
```nix
{ config, lib, pkgs, ... }:
@@ -165,9 +161,7 @@ in {
:::
::: {#exec-escaping-example .example}
-::: {.title}
**Example: Escaping in Exec directives**
-:::
```nix
{ config, lib, pkgs, utils, ... }:
diff --git a/nixos/doc/manual/development/writing-nixos-tests.section.md b/nixos/doc/manual/development/writing-nixos-tests.section.md
index 5bcdf6e58eb1..d80e314e6251 100644
--- a/nixos/doc/manual/development/writing-nixos-tests.section.md
+++ b/nixos/doc/manual/development/writing-nixos-tests.section.md
@@ -417,8 +417,7 @@ with foo_running:
`seconds_interval`
-:
- specifies how often the condition should be polled:
+: specifies how often the condition should be polled:
```py
@polling_condition(seconds_interval=10)
@@ -428,8 +427,7 @@ def foo_running():
`description`
-:
- is used in the log when the condition is checked. If this is not provided, the description is pulled from the docstring of the function. These two are therefore equivalent:
+: is used in the log when the condition is checked. If this is not provided, the description is pulled from the docstring of the function. These two are therefore equivalent:
```py
@polling_condition
diff --git a/nixos/doc/manual/from_md/README.md b/nixos/doc/manual/from_md/README.md
deleted file mode 100644
index cc6d08ca0a15..000000000000
--- a/nixos/doc/manual/from_md/README.md
+++ /dev/null
@@ -1,5 +0,0 @@
-This directory is temporarily needed while we transition the manual to CommonMark. It stores the output of the ../md-to-db.sh script that converts CommonMark files back to DocBook.
-
-We are choosing to convert the Markdown to DocBook at authoring time instead of manual building time, because we do not want the pandoc toolchain to become part of the NixOS closure.
-
-Do not edit the DocBook files inside this directory or its subdirectories. Instead, edit the corresponding .md file in the normal manual directories, and run ../md-to-db.sh to update the file here.
diff --git a/nixos/doc/manual/from_md/administration/boot-problems.section.xml b/nixos/doc/manual/from_md/administration/boot-problems.section.xml
deleted file mode 100644
index 144661c86eba..000000000000
--- a/nixos/doc/manual/from_md/administration/boot-problems.section.xml
+++ /dev/null
@@ -1,144 +0,0 @@
-
- Boot Problems
-
- If NixOS fails to boot, there are a number of kernel command line
- parameters that may help you to identify or fix the issue. You can
- add these parameters in the GRUB boot menu by pressing “e” to modify
- the selected boot entry and editing the line starting with
- linux. The following are some useful kernel
- command line parameters that are recognised by the NixOS boot
- scripts or by systemd:
-
-
-
-
- boot.shell_on_fail
-
-
-
- Allows the user to start a root shell if something goes wrong
- in stage 1 of the boot process (the initial ramdisk). This is
- disabled by default because there is no authentication for the
- root shell.
-
-
-
-
-
- boot.debug1
-
-
-
- Start an interactive shell in stage 1 before anything useful
- has been done. That is, no modules have been loaded and no
- file systems have been mounted, except for
- /proc and /sys.
-
-
-
-
-
- boot.debug1devices
-
-
-
- Like boot.debug1, but runs stage1 until
- kernel modules are loaded and device nodes are created. This
- may help with e.g. making the keyboard work.
-
-
-
-
-
- boot.debug1mounts
-
-
-
- Like boot.debug1 or
- boot.debug1devices, but runs stage1 until
- all filesystems that are mounted during initrd are mounted
- (see
- neededForBoot).
- As a motivating example, this could be useful if you’ve
- forgotten to set
- neededForBoot
- on a file system.
-
-
-
-
-
- boot.trace
-
-
-
- Print every shell command executed by the stage 1 and 2 boot
- scripts.
-
-
-
-
-
- single
-
-
-
- Boot into rescue mode (a.k.a. single user mode). This will
- cause systemd to start nothing but the unit
- rescue.target, which runs
- sulogin to prompt for the root password and
- start a root login shell. Exiting the shell causes the system
- to continue with the normal boot process.
-
-
-
-
-
- systemd.log_level=debug
- systemd.log_target=console
-
-
-
- Make systemd very verbose and send log messages to the console
- instead of the journal. For more parameters recognised by
- systemd, see systemd(1).
-
-
-
-
-
- In addition, these arguments are recognised by the live image only:
-
-
-
-
- live.nixos.passwd=password
-
-
-
- Set the password for the nixos live user.
- This can be used for SSH access if there are issues using the
- terminal.
-
-
-
-
-
- Notice that for boot.shell_on_fail,
- boot.debug1,
- boot.debug1devices, and
- boot.debug1mounts, if you did
- not select start the new
- shell as pid 1, and you exit from the new
- shell, boot will proceed normally from the point where it failed, as
- if you’d chosen ignore the error and continue.
-
-
- If no login prompts or X11 login screens appear (e.g. due to hanging
- dependencies), you can press Alt+ArrowUp. If you’re lucky, this will
- start rescue mode (described above). (Also note that since most
- units have a 90-second timeout before systemd gives up on them, the
- agetty login prompts should appear eventually
- unless something is very wrong.)
-
-
diff --git a/nixos/doc/manual/from_md/administration/cleaning-store.chapter.xml b/nixos/doc/manual/from_md/administration/cleaning-store.chapter.xml
deleted file mode 100644
index 35dfaf30f457..000000000000
--- a/nixos/doc/manual/from_md/administration/cleaning-store.chapter.xml
+++ /dev/null
@@ -1,72 +0,0 @@
-
- Cleaning the Nix Store
-
- Nix has a purely functional model, meaning that packages are never
- upgraded in place. Instead new versions of packages end up in a
- different location in the Nix store (/nix/store).
- You should periodically run Nix’s garbage
- collector to remove old, unreferenced packages. This is
- easy:
-
-
-$ nix-collect-garbage
-
-
- Alternatively, you can use a systemd unit that does the same in the
- background:
-
-
-# systemctl start nix-gc.service
-
-
- You can tell NixOS in configuration.nix to run
- this unit automatically at certain points in time, for instance,
- every night at 03:15:
-
-
-nix.gc.automatic = true;
-nix.gc.dates = "03:15";
-
-
- The commands above do not remove garbage collector roots, such as
- old system configurations. Thus they do not remove the ability to
- roll back to previous configurations. The following command deletes
- old roots, removing the ability to roll back to them:
-
-
-$ nix-collect-garbage -d
-
-
- You can also do this for specific profiles, e.g.
-
-
-$ nix-env -p /nix/var/nix/profiles/per-user/eelco/profile --delete-generations old
-
-
- Note that NixOS system configurations are stored in the profile
- /nix/var/nix/profiles/system.
-
-
- Another way to reclaim disk space (often as much as 40% of the size
- of the Nix store) is to run Nix’s store optimiser, which seeks out
- identical files in the store and replaces them with hard links to a
- single copy.
-
-
-$ nix-store --optimise
-
-
- Since this command needs to read the entire Nix store, it can take
- quite a while to finish.
-
-
- NixOS Boot Entries
-
- If your /boot partition runs out of space,
- after clearing old profiles you must rebuild your system with
- nixos-rebuild boot or
- nixos-rebuild switch to update the
- /boot partition and clear space.
-
-
-
diff --git a/nixos/doc/manual/from_md/administration/container-networking.section.xml b/nixos/doc/manual/from_md/administration/container-networking.section.xml
deleted file mode 100644
index a64053cdfa5e..000000000000
--- a/nixos/doc/manual/from_md/administration/container-networking.section.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-
- Container Networking
-
- When you create a container using
- nixos-container create, it gets it own private
- IPv4 address in the range 10.233.0.0/16. You can
- get the container’s IPv4 address as follows:
-
-
-# nixos-container show-ip foo
-10.233.4.2
-
-$ ping -c1 10.233.4.2
-64 bytes from 10.233.4.2: icmp_seq=1 ttl=64 time=0.106 ms
-
-
- Networking is implemented using a pair of virtual Ethernet devices.
- The network interface in the container is called
- eth0, while the matching interface in the host is
- called ve-container-name (e.g.,
- ve-foo). The container has its own network
- namespace and the CAP_NET_ADMIN capability, so it
- can perform arbitrary network configuration such as setting up
- firewall rules, without affecting or having access to the host’s
- network.
-
-
- By default, containers cannot talk to the outside network. If you
- want that, you should set up Network Address Translation (NAT) rules
- on the host to rewrite container traffic to use your external IP
- address. This can be accomplished using the following configuration
- on the host:
-
-
-networking.nat.enable = true;
-networking.nat.internalInterfaces = ["ve-+"];
-networking.nat.externalInterface = "eth0";
-
-
- where eth0 should be replaced with the desired
- external interface. Note that ve-+ is a wildcard
- that matches all container interfaces.
-
-
- If you are using Network Manager, you need to explicitly prevent it
- from managing container interfaces:
-
-
-networking.networkmanager.unmanaged = [ "interface-name:ve-*" ];
-
-
- You may need to restart your system for the changes to take effect.
-
-
diff --git a/nixos/doc/manual/from_md/administration/containers.chapter.xml b/nixos/doc/manual/from_md/administration/containers.chapter.xml
deleted file mode 100644
index afbd5b35aaa5..000000000000
--- a/nixos/doc/manual/from_md/administration/containers.chapter.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
- Container Management
-
- NixOS allows you to easily run other NixOS instances as
- containers. Containers are a light-weight
- approach to virtualisation that runs software in the container at
- the same speed as in the host system. NixOS containers share the Nix
- store of the host, making container creation very efficient.
-
-
-
- Currently, NixOS containers are not perfectly isolated from the
- host system. This means that a user with root access to the
- container can do things that affect the host. So you should not
- give container root access to untrusted users.
-
-
-
- NixOS containers can be created in two ways: imperatively, using the
- command nixos-container, and declaratively, by
- specifying them in your configuration.nix. The
- declarative approach implies that containers get upgraded along with
- your host system when you run nixos-rebuild,
- which is often not what you want. By contrast, in the imperative
- approach, containers are configured and updated independently from
- the host system.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/administration/control-groups.chapter.xml b/nixos/doc/manual/from_md/administration/control-groups.chapter.xml
deleted file mode 100644
index f78c05878031..000000000000
--- a/nixos/doc/manual/from_md/administration/control-groups.chapter.xml
+++ /dev/null
@@ -1,67 +0,0 @@
-
- Control Groups
-
- To keep track of the processes in a running system, systemd uses
- control groups (cgroups). A control group is a
- set of processes used to allocate resources such as CPU, memory or
- I/O bandwidth. There can be multiple control group hierarchies,
- allowing each kind of resource to be managed independently.
-
-
- The command systemd-cgls lists all control groups
- in the systemd hierarchy, which is what systemd
- uses to keep track of the processes belonging to each service or
- user session:
-
-
-$ systemd-cgls
-├─user
-│ └─eelco
-│ └─c1
-│ ├─ 2567 -:0
-│ ├─ 2682 kdeinit4: kdeinit4 Running...
-│ ├─ ...
-│ └─10851 sh -c less -R
-└─system
- ├─httpd.service
- │ ├─2444 httpd -f /nix/store/3pyacby5cpr55a03qwbnndizpciwq161-httpd.conf -DNO_DETACH
- │ └─...
- ├─dhcpcd.service
- │ └─2376 dhcpcd --config /nix/store/f8dif8dsi2yaa70n03xir8r653776ka6-dhcpcd.conf
- └─ ...
-
-
- Similarly, systemd-cgls cpu shows the cgroups in
- the CPU hierarchy, which allows per-cgroup CPU scheduling
- priorities. By default, every systemd service gets its own CPU
- cgroup, while all user sessions are in the top-level CPU cgroup.
- This ensures, for instance, that a thousand run-away processes in
- the httpd.service cgroup cannot starve the CPU
- for one process in the postgresql.service cgroup.
- (By contrast, it they were in the same cgroup, then the PostgreSQL
- process would get 1/1001 of the cgroup’s CPU time.) You can limit a
- service’s CPU share in configuration.nix:
-
-
-systemd.services.httpd.serviceConfig.CPUShares = 512;
-
-
- By default, every cgroup has 1024 CPU shares, so this will halve the
- CPU allocation of the httpd.service cgroup.
-
-
- There also is a memory hierarchy that controls
- memory allocation limits; by default, all processes are in the
- top-level cgroup, so any service or session can exhaust all
- available memory. Per-cgroup memory limits can be specified in
- configuration.nix; for instance, to limit
- httpd.service to 512 MiB of RAM (excluding swap):
-
-
-systemd.services.httpd.serviceConfig.MemoryLimit = "512M";
-
-
- The command systemd-cgtop shows a continuously
- updated list of all cgroups with their CPU and memory usage.
-
-
diff --git a/nixos/doc/manual/from_md/administration/declarative-containers.section.xml b/nixos/doc/manual/from_md/administration/declarative-containers.section.xml
deleted file mode 100644
index efc3432ba1a1..000000000000
--- a/nixos/doc/manual/from_md/administration/declarative-containers.section.xml
+++ /dev/null
@@ -1,60 +0,0 @@
-
- Declarative Container Specification
-
- You can also specify containers and their configuration in the
- host’s configuration.nix. For example, the
- following specifies that there shall be a container named
- database running PostgreSQL:
-
-
-containers.database =
- { config =
- { config, pkgs, ... }:
- { services.postgresql.enable = true;
- services.postgresql.package = pkgs.postgresql_14;
- };
- };
-
-
- If you run nixos-rebuild switch, the container
- will be built. If the container was already running, it will be
- updated in place, without rebooting. The container can be configured
- to start automatically by setting
- containers.database.autoStart = true in its
- configuration.
-
-
- By default, declarative containers share the network namespace of
- the host, meaning that they can listen on (privileged) ports.
- However, they cannot change the network configuration. You can give
- a container its own network as follows:
-
-
-containers.database = {
- privateNetwork = true;
- hostAddress = "192.168.100.10";
- localAddress = "192.168.100.11";
-};
-
-
- This gives the container a private virtual Ethernet interface with
- IP address 192.168.100.11, which is hooked up to
- a virtual Ethernet interface on the host with IP address
- 192.168.100.10. (See the next section for details
- on container networking.)
-
-
- To disable the container, just remove it from
- configuration.nix and run
- nixos-rebuild switch. Note that this will not
- delete the root directory of the container in
- /var/lib/nixos-containers. Containers can be
- destroyed using the imperative method:
- nixos-container destroy foo.
-
-
- Declarative containers can be started and stopped using the
- corresponding systemd service, e.g.
- systemctl start container@database.
-
-
diff --git a/nixos/doc/manual/from_md/administration/imperative-containers.section.xml b/nixos/doc/manual/from_md/administration/imperative-containers.section.xml
deleted file mode 100644
index 865fc4689398..000000000000
--- a/nixos/doc/manual/from_md/administration/imperative-containers.section.xml
+++ /dev/null
@@ -1,132 +0,0 @@
-
- Imperative Container Management
-
- We’ll cover imperative container management using
- nixos-container first. Be aware that container
- management is currently only possible as root.
-
-
- You create a container with identifier foo as
- follows:
-
-
-# nixos-container create foo
-
-
- This creates the container’s root directory in
- /var/lib/nixos-containers/foo and a small
- configuration file in
- /etc/nixos-containers/foo.conf. It also builds
- the container’s initial system configuration and stores it in
- /nix/var/nix/profiles/per-container/foo/system.
- You can modify the initial configuration of the container on the
- command line. For instance, to create a container that has
- sshd running, with the given public key for
- root:
-
-
-# nixos-container create foo --config '
- services.openssh.enable = true;
- users.users.root.openssh.authorizedKeys.keys = ["ssh-dss AAAAB3N…"];
-'
-
-
- By default the next free address in the
- 10.233.0.0/16 subnet will be chosen as container
- IP. This behavior can be altered by setting
- --host-address and
- --local-address:
-
-
-# nixos-container create test --config-file test-container.nix \
- --local-address 10.235.1.2 --host-address 10.235.1.1
-
-
- Creating a container does not start it. To start the container, run:
-
-
-# nixos-container start foo
-
-
- This command will return as soon as the container has booted and has
- reached multi-user.target. On the host, the
- container runs within a systemd unit called
- container@container-name.service. Thus, if
- something went wrong, you can get status info using
- systemctl:
-
-
-# systemctl status container@foo
-
-
- If the container has started successfully, you can log in as root
- using the root-login operation:
-
-
-# nixos-container root-login foo
-[root@foo:~]#
-
-
- Note that only root on the host can do this (since there is no
- authentication). You can also get a regular login prompt using the
- login operation, which is available to all users
- on the host:
-
-
-# nixos-container login foo
-foo login: alice
-Password: ***
-
-
- With nixos-container run, you can execute
- arbitrary commands in the container:
-
-
-# nixos-container run foo -- uname -a
-Linux foo 3.4.82 #1-NixOS SMP Thu Mar 20 14:44:05 UTC 2014 x86_64 GNU/Linux
-
-
- There are several ways to change the configuration of the container.
- First, on the host, you can edit
- /var/lib/container/name/etc/nixos/configuration.nix,
- and run
-
-
-# nixos-container update foo
-
-
- This will build and activate the new configuration. You can also
- specify a new configuration on the command line:
-
-
-# nixos-container update foo --config '
- services.httpd.enable = true;
- services.httpd.adminAddr = "foo@example.org";
- networking.firewall.allowedTCPPorts = [ 80 ];
-'
-
-# curl http://$(nixos-container show-ip foo)/
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">…
-
-
- However, note that this will overwrite the container’s
- /etc/nixos/configuration.nix.
-
-
- Alternatively, you can change the configuration from within the
- container itself by running nixos-rebuild switch
- inside the container. Note that the container by default does not
- have a copy of the NixOS channel, so you should run
- nix-channel --update first.
-
-
- Containers can be stopped and started using
- nixos-container stop and
- nixos-container start, respectively, or by using
- systemctl on the container’s service unit. To
- destroy a container, including its file system, do
-
-
-# nixos-container destroy foo
-
-
diff --git a/nixos/doc/manual/from_md/administration/logging.chapter.xml b/nixos/doc/manual/from_md/administration/logging.chapter.xml
deleted file mode 100644
index 4da38c065a27..000000000000
--- a/nixos/doc/manual/from_md/administration/logging.chapter.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-
- Logging
-
- System-wide logging is provided by systemd’s
- journal, which subsumes traditional logging
- daemons such as syslogd and klogd. Log entries are kept in binary
- files in /var/log/journal/. The command
- journalctl allows you to see the contents of the
- journal. For example,
-
-
-$ journalctl -b
-
-
- shows all journal entries since the last reboot. (The output of
- journalctl is piped into less
- by default.) You can use various options and match operators to
- restrict output to messages of interest. For instance, to get all
- messages from PostgreSQL:
-
-
-$ journalctl -u postgresql.service
--- Logs begin at Mon, 2013-01-07 13:28:01 CET, end at Tue, 2013-01-08 01:09:57 CET. --
-...
-Jan 07 15:44:14 hagbard postgres[2681]: [2-1] LOG: database system is shut down
--- Reboot --
-Jan 07 15:45:10 hagbard postgres[2532]: [1-1] LOG: database system was shut down at 2013-01-07 15:44:14 CET
-Jan 07 15:45:13 hagbard postgres[2500]: [1-1] LOG: database system is ready to accept connections
-
-
- Or to get all messages since the last reboot that have at least a
- critical severity level:
-
-
-$ journalctl -b -p crit
-Dec 17 21:08:06 mandark sudo[3673]: pam_unix(sudo:auth): auth could not identify password for [alice]
-Dec 29 01:30:22 mandark kernel[6131]: [1053513.909444] CPU6: Core temperature above threshold, cpu clock throttled (total events = 1)
-
-
- The system journal is readable by root and by users in the
- wheel and systemd-journal
- groups. All users have a private journal that can be read using
- journalctl.
-
-
diff --git a/nixos/doc/manual/from_md/administration/maintenance-mode.section.xml b/nixos/doc/manual/from_md/administration/maintenance-mode.section.xml
deleted file mode 100644
index c86b1911c117..000000000000
--- a/nixos/doc/manual/from_md/administration/maintenance-mode.section.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
- Maintenance Mode
-
- You can enter rescue mode by running:
-
-
-# systemctl rescue
-
-
- This will eventually give you a single-user root shell. Systemd will
- stop (almost) all system services. To get out of maintenance mode,
- just exit from the rescue shell.
-
-
diff --git a/nixos/doc/manual/from_md/administration/network-problems.section.xml b/nixos/doc/manual/from_md/administration/network-problems.section.xml
deleted file mode 100644
index 4c0598ca94e8..000000000000
--- a/nixos/doc/manual/from_md/administration/network-problems.section.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
- Network Problems
-
- Nix uses a so-called binary cache to optimise
- building a package from source into downloading it as a pre-built
- binary. That is, whenever a command like
- nixos-rebuild needs a path in the Nix store, Nix
- will try to download that path from the Internet rather than build
- it from source. The default binary cache is
- https://cache.nixos.org/. If this cache is
- unreachable, Nix operations may take a long time due to HTTP
- connection timeouts. You can disable the use of the binary cache by
- adding --option use-binary-caches false, e.g.
-
-
-# nixos-rebuild switch --option use-binary-caches false
-
-
- If you have an alternative binary cache at your disposal, you can
- use it instead:
-
-
-# nixos-rebuild switch --option binary-caches http://my-cache.example.org/
-
-
diff --git a/nixos/doc/manual/from_md/administration/rebooting.chapter.xml b/nixos/doc/manual/from_md/administration/rebooting.chapter.xml
deleted file mode 100644
index 78ee75afb642..000000000000
--- a/nixos/doc/manual/from_md/administration/rebooting.chapter.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
- Rebooting and Shutting Down
-
- The system can be shut down (and automatically powered off) by
- doing:
-
-
-# shutdown
-
-
- This is equivalent to running systemctl poweroff.
-
-
- To reboot the system, run
-
-
-# reboot
-
-
- which is equivalent to systemctl reboot.
- Alternatively, you can quickly reboot the system using
- kexec, which bypasses the BIOS by directly
- loading the new kernel into memory:
-
-
-# systemctl kexec
-
-
- The machine can be suspended to RAM (if supported) using
- systemctl suspend, and suspended to disk using
- systemctl hibernate.
-
-
- These commands can be run by any user who is logged in locally, i.e.
- on a virtual console or in X11; otherwise, the user is asked for
- authentication.
-
-
diff --git a/nixos/doc/manual/from_md/administration/rollback.section.xml b/nixos/doc/manual/from_md/administration/rollback.section.xml
deleted file mode 100644
index a8df053011c5..000000000000
--- a/nixos/doc/manual/from_md/administration/rollback.section.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
- Rolling Back Configuration Changes
-
- After running nixos-rebuild to switch to a new
- configuration, you may find that the new configuration doesn’t work
- very well. In that case, there are several ways to return to a
- previous configuration.
-
-
- First, the GRUB boot manager allows you to boot into any previous
- configuration that hasn’t been garbage-collected. These
- configurations can be found under the GRUB submenu NixOS -
- All configurations. This is especially useful if the new
- configuration fails to boot. After the system has booted, you can
- make the selected configuration the default for subsequent boots:
-
-
-# /run/current-system/bin/switch-to-configuration boot
-
-
- Second, you can switch to the previous configuration in a running
- system:
-
-
-# nixos-rebuild switch --rollback
-
-
- This is equivalent to running:
-
-
-# /nix/var/nix/profiles/system-N-link/bin/switch-to-configuration switch
-
-
- where N is the number of the NixOS system
- configuration. To get a list of the available configurations, do:
-
-
-$ ls -l /nix/var/nix/profiles/system-*-link
-...
-lrwxrwxrwx 1 root root 78 Aug 12 13:54 /nix/var/nix/profiles/system-268-link -> /nix/store/202b...-nixos-13.07pre4932_5a676e4-4be1055
-
-
diff --git a/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml b/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml
deleted file mode 100644
index 3b7bd6cd30cf..000000000000
--- a/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml
+++ /dev/null
@@ -1,141 +0,0 @@
-
- Service Management
-
- In NixOS, all system services are started and monitored using the
- systemd program. systemd is the init process of the
- system (i.e. PID 1), the parent of all other processes. It manages a
- set of so-called units, which can be things like
- system services (programs), but also mount points, swap files,
- devices, targets (groups of units) and more. Units can have complex
- dependencies; for instance, one unit can require that another unit
- must be successfully started before the first unit can be started.
- When the system boots, it starts a unit named
- default.target; the dependencies of this unit
- cause all system services to be started, file systems to be mounted,
- swap files to be activated, and so on.
-
-
- Interacting with a running systemd
-
- The command systemctl is the main way to
- interact with systemd. The following paragraphs
- demonstrate ways to interact with any OS running systemd as init
- system. NixOS is of no exception. The
- next section
- explains NixOS specific things worth knowing.
-
-
- Without any arguments, systemctl the status of
- active units:
-
-
-$ systemctl
--.mount loaded active mounted /
-swapfile.swap loaded active active /swapfile
-sshd.service loaded active running SSH Daemon
-graphical.target loaded active active Graphical Interface
-...
-
-
- You can ask for detailed status information about a unit, for
- instance, the PostgreSQL database service:
-
-
-$ systemctl status postgresql.service
-postgresql.service - PostgreSQL Server
- Loaded: loaded (/nix/store/pn3q73mvh75gsrl8w7fdlfk3fq5qm5mw-unit/postgresql.service)
- Active: active (running) since Mon, 2013-01-07 15:55:57 CET; 9h ago
- Main PID: 2390 (postgres)
- CGroup: name=systemd:/system/postgresql.service
- ├─2390 postgres
- ├─2418 postgres: writer process
- ├─2419 postgres: wal writer process
- ├─2420 postgres: autovacuum launcher process
- ├─2421 postgres: stats collector process
- └─2498 postgres: zabbix zabbix [local] idle
-
-Jan 07 15:55:55 hagbard postgres[2394]: [1-1] LOG: database system was shut down at 2013-01-07 15:55:05 CET
-Jan 07 15:55:57 hagbard postgres[2390]: [1-1] LOG: database system is ready to accept connections
-Jan 07 15:55:57 hagbard postgres[2420]: [1-1] LOG: autovacuum launcher started
-Jan 07 15:55:57 hagbard systemd[1]: Started PostgreSQL Server.
-
-
- Note that this shows the status of the unit (active and running),
- all the processes belonging to the service, as well as the most
- recent log messages from the service.
-
-
- Units can be stopped, started or restarted:
-
-
-# systemctl stop postgresql.service
-# systemctl start postgresql.service
-# systemctl restart postgresql.service
-
-
- These operations are synchronous: they wait until the service has
- finished starting or stopping (or has failed). Starting a unit
- will cause the dependencies of that unit to be started as well (if
- necessary).
-
-
-
- systemd in NixOS
-
- Packages in Nixpkgs sometimes provide systemd units with them,
- usually in e.g #pkg-out#/lib/systemd/. Putting
- such a package in environment.systemPackages
- doesn’t make the service available to users or the system.
-
-
- In order to enable a systemd system service
- with provided upstream package, use (e.g):
-
-
-systemd.packages = [ pkgs.packagekit ];
-
-
- Usually NixOS modules written by the community do the above, plus
- take care of other details. If a module was written for a service
- you are interested in, you’d probably need only to use
- services.#name#.enable = true;. These services
- are defined in Nixpkgs’
-
- nixos/modules/ directory . In case the
- service is simple enough, the above method should work, and start
- the service on boot.
-
-
- User systemd services on the other hand,
- should be treated differently. Given a package that has a systemd
- unit file at #pkg-out#/lib/systemd/user/, using
- will make you able to
- start the service via systemctl --user start,
- but it won’t start automatically on login. However, You can
- imperatively enable it by adding the package’s attribute to
- and then do this (e.g):
-
-
-$ mkdir -p ~/.config/systemd/user/default.target.wants
-$ ln -s /run/current-system/sw/lib/systemd/user/syncthing.service ~/.config/systemd/user/default.target.wants/
-$ systemctl --user daemon-reload
-$ systemctl --user enable syncthing.service
-
-
- If you are interested in a timer file, use
- timers.target.wants instead of
- default.target.wants in the 1st and 2nd
- command.
-
-
- Using systemctl --user enable syncthing.service
- instead of the above, will work, but it’ll use the absolute path
- of syncthing.service for the symlink, and this
- path is in /nix/store/.../lib/systemd/user/.
- Hence garbage collection will
- remove that file and you will wind up with a broken symlink in
- your systemd configuration, which in turn will not make the
- service / timer start on login.
-
-
-
diff --git a/nixos/doc/manual/from_md/administration/store-corruption.section.xml b/nixos/doc/manual/from_md/administration/store-corruption.section.xml
deleted file mode 100644
index 9ed572d484dc..000000000000
--- a/nixos/doc/manual/from_md/administration/store-corruption.section.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
- Nix Store Corruption
-
- After a system crash, it’s possible for files in the Nix store to
- become corrupted. (For instance, the Ext4 file system has the
- tendency to replace un-synced files with zero bytes.) NixOS tries
- hard to prevent this from happening: it performs a
- sync before switching to a new configuration, and
- Nix’s database is fully transactional. If corruption still occurs,
- you may be able to fix it automatically.
-
-
- If the corruption is in a path in the closure of the NixOS system
- configuration, you can fix it by doing
-
-
-# nixos-rebuild switch --repair
-
-
- This will cause Nix to check every path in the closure, and if its
- cryptographic hash differs from the hash recorded in Nix’s database,
- the path is rebuilt or redownloaded.
-
-
- You can also scan the entire Nix store for corrupt paths:
-
-
-# nix-store --verify --check-contents --repair
-
-
- Any corrupt paths will be redownloaded if they’re available in a
- binary cache; otherwise, they cannot be repaired.
-
-
diff --git a/nixos/doc/manual/from_md/administration/troubleshooting.chapter.xml b/nixos/doc/manual/from_md/administration/troubleshooting.chapter.xml
deleted file mode 100644
index 8bbb8a1fe729..000000000000
--- a/nixos/doc/manual/from_md/administration/troubleshooting.chapter.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
- Troubleshooting
-
- This chapter describes solutions to common problems you might
- encounter when you manage your NixOS system.
-
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/administration/user-sessions.chapter.xml b/nixos/doc/manual/from_md/administration/user-sessions.chapter.xml
deleted file mode 100644
index e8c64f153fc5..000000000000
--- a/nixos/doc/manual/from_md/administration/user-sessions.chapter.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
- User Sessions
-
- Systemd keeps track of all users who are logged into the system
- (e.g. on a virtual console or remotely via SSH). The command
- loginctl allows querying and manipulating user
- sessions. For instance, to list all user sessions:
-
-
-$ loginctl
- SESSION UID USER SEAT
- c1 500 eelco seat0
- c3 0 root seat0
- c4 500 alice
-
-
- This shows that two users are logged in locally, while another is
- logged in remotely. (Seats are essentially the
- combinations of displays and input devices attached to the system;
- usually, there is only one seat.) To get information about a
- session:
-
-
-$ loginctl session-status c3
-c3 - root (0)
- Since: Tue, 2013-01-08 01:17:56 CET; 4min 42s ago
- Leader: 2536 (login)
- Seat: seat0; vc3
- TTY: /dev/tty3
- Service: login; type tty; class user
- State: online
- CGroup: name=systemd:/user/root/c3
- ├─ 2536 /nix/store/10mn4xip9n7y9bxqwnsx7xwx2v2g34xn-shadow-4.1.5.1/bin/login --
- ├─10339 -bash
- └─10355 w3m nixos.org
-
-
- This shows that the user is logged in on virtual console 3. It also
- lists the processes belonging to this session. Since systemd keeps
- track of this, you can terminate a session in a way that ensures
- that all the session’s processes are gone:
-
-
-# loginctl terminate-session c3
-
-
diff --git a/nixos/doc/manual/from_md/configuration/abstractions.section.xml b/nixos/doc/manual/from_md/configuration/abstractions.section.xml
deleted file mode 100644
index 469e85979e0f..000000000000
--- a/nixos/doc/manual/from_md/configuration/abstractions.section.xml
+++ /dev/null
@@ -1,101 +0,0 @@
-
- Abstractions
-
- If you find yourself repeating yourself over and over, it’s time to
- abstract. Take, for instance, this Apache HTTP Server configuration:
-
-
-{
- services.httpd.virtualHosts =
- { "blog.example.org" = {
- documentRoot = "/webroot/blog.example.org";
- adminAddr = "alice@example.org";
- forceSSL = true;
- enableACME = true;
- enablePHP = true;
- };
- "wiki.example.org" = {
- documentRoot = "/webroot/wiki.example.org";
- adminAddr = "alice@example.org";
- forceSSL = true;
- enableACME = true;
- enablePHP = true;
- };
- };
-}
-
-
- It defines two virtual hosts with nearly identical configuration;
- the only difference is the document root directories. To prevent
- this duplication, we can use a let:
-
-
-let
- commonConfig =
- { adminAddr = "alice@example.org";
- forceSSL = true;
- enableACME = true;
- };
-in
-{
- services.httpd.virtualHosts =
- { "blog.example.org" = (commonConfig // { documentRoot = "/webroot/blog.example.org"; });
- "wiki.example.org" = (commonConfig // { documentRoot = "/webroot/wiki.example.com"; });
- };
-}
-
-
- The let commonConfig = ... defines a variable
- named commonConfig. The //
- operator merges two attribute sets, so the configuration of the
- second virtual host is the set commonConfig
- extended with the document root option.
-
-
- You can write a let wherever an expression is
- allowed. Thus, you also could have written:
-
-
-{
- services.httpd.virtualHosts =
- let commonConfig = ...; in
- { "blog.example.org" = (commonConfig // { ... })
- "wiki.example.org" = (commonConfig // { ... })
- };
-}
-
-
- but not { let commonConfig = ...; in ...; } since
- attributes (as opposed to attribute values) are not expressions.
-
-
- Functions provide another method
- of abstraction. For instance, suppose that we want to generate lots
- of different virtual hosts, all with identical configuration except
- for the document root. This can be done as follows:
-
-
-{
- services.httpd.virtualHosts =
- let
- makeVirtualHost = webroot:
- { documentRoot = webroot;
- adminAddr = "alice@example.org";
- forceSSL = true;
- enableACME = true;
- };
- in
- { "example.org" = (makeVirtualHost "/webroot/example.org");
- "example.com" = (makeVirtualHost "/webroot/example.com");
- "example.gov" = (makeVirtualHost "/webroot/example.gov");
- "example.nl" = (makeVirtualHost "/webroot/example.nl");
- };
-}
-
-
- Here, makeVirtualHost is a function that takes a
- single argument webroot and returns the
- configuration for a virtual host. That function is then called for
- several names to produce the list of virtual host configurations.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/ad-hoc-network-config.section.xml b/nixos/doc/manual/from_md/configuration/ad-hoc-network-config.section.xml
deleted file mode 100644
index 516022dc16d2..000000000000
--- a/nixos/doc/manual/from_md/configuration/ad-hoc-network-config.section.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
- Ad-Hoc Configuration
-
- You can use to
- specify shell commands to be run at the end of
- network-setup.service. This is useful for doing
- network configuration not covered by the existing NixOS modules. For
- instance, to statically configure an IPv6 address:
-
-
-networking.localCommands =
- ''
- ip -6 addr add 2001:610:685:1::1/64 dev eth0
- '';
-
-
diff --git a/nixos/doc/manual/from_md/configuration/ad-hoc-packages.section.xml b/nixos/doc/manual/from_md/configuration/ad-hoc-packages.section.xml
deleted file mode 100644
index c9a8d4f3f106..000000000000
--- a/nixos/doc/manual/from_md/configuration/ad-hoc-packages.section.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-
- Ad-Hoc Package Management
-
- With the command nix-env, you can install and
- uninstall packages from the command line. For instance, to install
- Mozilla Thunderbird:
-
-
-$ nix-env -iA nixos.thunderbird
-
-
- If you invoke this as root, the package is installed in the Nix
- profile /nix/var/nix/profiles/default and visible
- to all users of the system; otherwise, the package ends up in
- /nix/var/nix/profiles/per-user/username/profile
- and is not visible to other users. The -A flag
- specifies the package by its attribute name; without it, the package
- is installed by matching against its package name (e.g.
- thunderbird). The latter is slower because it
- requires matching against all available Nix packages, and is
- ambiguous if there are multiple matching packages.
-
-
- Packages come from the NixOS channel. You typically upgrade a
- package by updating to the latest version of the NixOS channel:
-
-
-$ nix-channel --update nixos
-
-
- and then running nix-env -i again. Other packages
- in the profile are not affected; this is the
- crucial difference with the declarative style of package management,
- where running nixos-rebuild switch causes all
- packages to be updated to their current versions in the NixOS
- channel. You can however upgrade all packages for which there is a
- newer version by doing:
-
-
-$ nix-env -u '*'
-
-
- A package can be uninstalled using the -e flag:
-
-
-$ nix-env -e thunderbird
-
-
- Finally, you can roll back an undesirable nix-env
- action:
-
-
-$ nix-env --rollback
-
-
- nix-env has many more flags. For details, see the
- nix-env(1) manpage or the Nix manual.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/adding-custom-packages.section.xml b/nixos/doc/manual/from_md/configuration/adding-custom-packages.section.xml
deleted file mode 100644
index b1a1a8df3247..000000000000
--- a/nixos/doc/manual/from_md/configuration/adding-custom-packages.section.xml
+++ /dev/null
@@ -1,118 +0,0 @@
-
- Adding Custom Packages
-
- It’s possible that a package you need is not available in NixOS. In
- that case, you can do two things. Either you can package it with
- Nix, or you can try to use prebuilt packages from upstream. Due to
- the peculiarities of NixOS, it is important to note that building
- software from source is often easier than using pre-built
- executables.
-
-
- Building with Nix
-
- This can be done either in-tree or out-of-tree. For an in-tree
- build, you can clone the Nixpkgs repository, add the package to
- your clone, and (optionally) submit a patch or pull request to
- have it accepted into the main Nixpkgs repository. This is
- described in detail in the
- Nixpkgs
- manual. In short, you clone Nixpkgs:
-
-
-$ git clone https://github.com/NixOS/nixpkgs
-$ cd nixpkgs
-
-
- Then you write and test the package as described in the Nixpkgs
- manual. Finally, you add it to
- , e.g.
-
-
-environment.systemPackages = [ pkgs.my-package ];
-
-
- and you run nixos-rebuild, specifying your own
- Nixpkgs tree:
-
-
-# nixos-rebuild switch -I nixpkgs=/path/to/my/nixpkgs
-
-
- The second possibility is to add the package outside of the
- Nixpkgs tree. For instance, here is how you specify a build of the
- GNU
- Hello package directly in
- configuration.nix:
-
-
-environment.systemPackages =
- let
- my-hello = with pkgs; stdenv.mkDerivation rec {
- name = "hello-2.8";
- src = fetchurl {
- url = "mirror://gnu/hello/${name}.tar.gz";
- sha256 = "0wqd8sjmxfskrflaxywc7gqw7sfawrfvdxd9skxawzfgyy0pzdz6";
- };
- };
- in
- [ my-hello ];
-
-
- Of course, you can also move the definition of
- my-hello into a separate Nix expression, e.g.
-
-
-environment.systemPackages = [ (import ./my-hello.nix) ];
-
-
- where my-hello.nix contains:
-
-
-with import <nixpkgs> {}; # bring all of Nixpkgs into scope
-
-stdenv.mkDerivation rec {
- name = "hello-2.8";
- src = fetchurl {
- url = "mirror://gnu/hello/${name}.tar.gz";
- sha256 = "0wqd8sjmxfskrflaxywc7gqw7sfawrfvdxd9skxawzfgyy0pzdz6";
- };
-}
-
-
- This allows testing the package easily:
-
-
-$ nix-build my-hello.nix
-$ ./result/bin/hello
-Hello, world!
-
-
-
- Using pre-built executables
-
- Most pre-built executables will not work on NixOS. There are two
- notable exceptions: flatpaks and AppImages. For flatpaks see the
- dedicated section.
- AppImages will not run as-is on NixOS. First you
- need to install appimage-run: add to
- /etc/nixos/configuration.nix
-
-
-environment.systemPackages = [ pkgs.appimage-run ];
-
-
- Then instead of running the AppImage as-is, run
- appimage-run foo.appimage.
-
-
- To make other pre-built executables work on NixOS, you need to
- package them with Nix and special helpers like
- autoPatchelfHook or
- buildFHSUserEnv. See the
- Nixpkgs
- manual for details. This is complex and often doing a
- source build is easier.
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/config-file.section.xml b/nixos/doc/manual/from_md/configuration/config-file.section.xml
deleted file mode 100644
index da5419cde4d3..000000000000
--- a/nixos/doc/manual/from_md/configuration/config-file.section.xml
+++ /dev/null
@@ -1,231 +0,0 @@
-
- NixOS Configuration File
-
- The NixOS configuration file generally looks like this:
-
-
-{ config, pkgs, ... }:
-
-{ option definitions
-}
-
-
- The first line ({ config, pkgs, ... }:) denotes
- that this is actually a function that takes at least the two
- arguments config and pkgs.
- (These are explained later, in chapter
- ) The function returns a
- set of option definitions
- ({ ... }). These definitions have the form
- name = value, where name is
- the name of an option and value is its value. For
- example,
-
-
-{ config, pkgs, ... }:
-
-{ services.httpd.enable = true;
- services.httpd.adminAddr = "alice@example.org";
- services.httpd.virtualHosts.localhost.documentRoot = "/webroot";
-}
-
-
- defines a configuration with three option definitions that together
- enable the Apache HTTP Server with /webroot as
- the document root.
-
-
- Sets can be nested, and in fact dots in option names are shorthand
- for defining a set containing another set. For instance,
- defines a set named
- services that contains a set named
- httpd, which in turn contains an option
- definition named enable with value
- true. This means that the example above can also
- be written as:
-
-
-{ config, pkgs, ... }:
-
-{ services = {
- httpd = {
- enable = true;
- adminAddr = "alice@example.org";
- virtualHosts = {
- localhost = {
- documentRoot = "/webroot";
- };
- };
- };
- };
-}
-
-
- which may be more convenient if you have lots of option definitions
- that share the same prefix (such as
- services.httpd).
-
-
- NixOS checks your option definitions for correctness. For instance,
- if you try to define an option that doesn’t exist (that is, doesn’t
- have a corresponding option declaration),
- nixos-rebuild will give an error like:
-
-
-The option `services.httpd.enable' defined in `/etc/nixos/configuration.nix' does not exist.
-
-
- Likewise, values in option definitions must have a correct type. For
- instance, services.httpd.enable must be a Boolean
- (true or false). Trying to
- give it a value of another type, such as a string, will cause an
- error:
-
-
-The option value `services.httpd.enable' in `/etc/nixos/configuration.nix' is not a boolean.
-
-
- Options have various types of values. The most important are:
-
-
-
-
- Strings
-
-
-
- Strings are enclosed in double quotes, e.g.
-
-
-networking.hostName = "dexter";
-
-
- Special characters can be escaped by prefixing them with a
- backslash (e.g. \").
-
-
- Multi-line strings can be enclosed in double single
- quotes, e.g.
-
-
-networking.extraHosts =
- ''
- 127.0.0.2 other-localhost
- 10.0.0.1 server
- '';
-
-
- The main difference is that it strips from each line a number
- of spaces equal to the minimal indentation of the string as a
- whole (disregarding the indentation of empty lines), and that
- characters like " and
- \ are not special (making it more
- convenient for including things like shell code). See more
- info about this in the Nix manual
- here.
-
-
-
-
-
- Booleans
-
-
-
- These can be true or
- false, e.g.
-
-
-networking.firewall.enable = true;
-networking.firewall.allowPing = false;
-
-
-
-
-
- Integers
-
-
-
- For example,
-
-
-boot.kernel.sysctl."net.ipv4.tcp_keepalive_time" = 60;
-
-
- (Note that here the attribute name
- net.ipv4.tcp_keepalive_time is enclosed in
- quotes to prevent it from being interpreted as a set named
- net containing a set named
- ipv4, and so on. This is because it’s not a
- NixOS option but the literal name of a Linux kernel setting.)
-
-
-
-
-
- Sets
-
-
-
- Sets were introduced above. They are name/value pairs enclosed
- in braces, as in the option definition
-
-
-fileSystems."/boot" =
- { device = "/dev/sda1";
- fsType = "ext4";
- options = [ "rw" "data=ordered" "relatime" ];
- };
-
-
-
-
-
- Lists
-
-
-
- The important thing to note about lists is that list elements
- are separated by whitespace, like this:
-
-
-boot.kernelModules = [ "fuse" "kvm-intel" "coretemp" ];
-
-
- List elements can be any other type, e.g. sets:
-
-
-swapDevices = [ { device = "/dev/disk/by-label/swap"; } ];
-
-
-
-
-
- Packages
-
-
-
- Usually, the packages you need are already part of the Nix
- Packages collection, which is a set that can be accessed
- through the function argument pkgs. Typical
- uses:
-
-
-environment.systemPackages =
- [ pkgs.thunderbird
- pkgs.emacs
- ];
-
-services.postgresql.package = pkgs.postgresql_14;
-
-
- The latter option definition changes the default PostgreSQL
- package used by NixOS’s PostgreSQL service to 14.x. For more
- information on packages, including how to add new ones, see
- .
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/config-syntax.chapter.xml b/nixos/doc/manual/from_md/configuration/config-syntax.chapter.xml
deleted file mode 100644
index baf9639554cc..000000000000
--- a/nixos/doc/manual/from_md/configuration/config-syntax.chapter.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
- Configuration Syntax
-
- The NixOS configuration file
- /etc/nixos/configuration.nix is actually a
- Nix expression, which is the Nix package
- manager’s purely functional language for describing how to build
- packages and configurations. This means you have all the expressive
- power of that language at your disposal, including the ability to
- abstract over common patterns, which is very useful when managing
- complex systems. The syntax and semantics of the Nix language are
- fully described in the
- Nix
- manual, but here we give a short overview of the most
- important constructs useful in NixOS configuration files.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/customizing-packages.section.xml b/nixos/doc/manual/from_md/configuration/customizing-packages.section.xml
deleted file mode 100644
index 8026c4102b48..000000000000
--- a/nixos/doc/manual/from_md/configuration/customizing-packages.section.xml
+++ /dev/null
@@ -1,90 +0,0 @@
-
- Customising Packages
-
- Some packages in Nixpkgs have options to enable or disable optional
- functionality or change other aspects of the package. For instance,
- the Firefox wrapper package (which provides Firefox with a set of
- plugins such as the Adobe Flash player) has an option to enable the
- Google Talk plugin. It can be set in
- configuration.nix as follows:
- nixpkgs.config.firefox.enableGoogleTalkPlugin = true;
-
-
-
- Unfortunately, Nixpkgs currently lacks a way to query available
- configuration options.
-
-
-
- Apart from high-level options, it’s possible to tweak a package in
- almost arbitrary ways, such as changing or disabling dependencies of
- a package. For instance, the Emacs package in Nixpkgs by default has
- a dependency on GTK 2. If you want to build it against GTK 3, you
- can specify that as follows:
-
-
-environment.systemPackages = [ (pkgs.emacs.override { gtk = pkgs.gtk3; }) ];
-
-
- The function override performs the call to the
- Nix function that produces Emacs, with the original arguments
- amended by the set of arguments specified by you. So here the
- function argument gtk gets the value
- pkgs.gtk3, causing Emacs to depend on GTK 3. (The
- parentheses are necessary because in Nix, function application binds
- more weakly than list construction, so without them,
- would be a list
- with two elements.)
-
-
- Even greater customisation is possible using the function
- overrideAttrs. While the
- override mechanism above overrides the arguments
- of a package function, overrideAttrs allows
- changing the attributes passed to
- mkDerivation. This permits changing any aspect of
- the package, such as the source code. For instance, if you want to
- override the source code of Emacs, you can say:
-
-
-environment.systemPackages = [
- (pkgs.emacs.overrideAttrs (oldAttrs: {
- name = "emacs-25.0-pre";
- src = /path/to/my/emacs/tree;
- }))
-];
-
-
- Here, overrideAttrs takes the Nix derivation
- specified by pkgs.emacs and produces a new
- derivation in which the original’s name and
- src attribute have been replaced by the given
- values by re-calling stdenv.mkDerivation. The
- original attributes are accessible via the function argument, which
- is conventionally named oldAttrs.
-
-
- The overrides shown above are not global. They do not affect the
- original package; other packages in Nixpkgs continue to depend on
- the original rather than the customised package. This means that if
- another package in your system depends on the original package, you
- end up with two instances of the package. If you want to have
- everything depend on your customised instance, you can apply a
- global override as follows:
-
-
-nixpkgs.config.packageOverrides = pkgs:
- { emacs = pkgs.emacs.override { gtk = pkgs.gtk3; };
- };
-
-
- The effect of this definition is essentially equivalent to modifying
- the emacs attribute in the Nixpkgs source tree.
- Any package in Nixpkgs that depends on emacs will
- be passed your customised instance. (However, the value
- pkgs.emacs in
- nixpkgs.config.packageOverrides refers to the
- original rather than overridden instance, to prevent an infinite
- recursion.)
-
-
diff --git a/nixos/doc/manual/from_md/configuration/declarative-packages.section.xml b/nixos/doc/manual/from_md/configuration/declarative-packages.section.xml
deleted file mode 100644
index bee310c2e34b..000000000000
--- a/nixos/doc/manual/from_md/configuration/declarative-packages.section.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-
- Declarative Package Management
-
- With declarative package management, you specify which packages you
- want on your system by setting the option
- . For instance,
- adding the following line to configuration.nix
- enables the Mozilla Thunderbird email application:
-
-
-environment.systemPackages = [ pkgs.thunderbird ];
-
-
- The effect of this specification is that the Thunderbird package
- from Nixpkgs will be built or downloaded as part of the system when
- you run nixos-rebuild switch.
-
-
-
- Some packages require additional global configuration such as
- D-Bus or systemd service registration so adding them to
- might not be
- sufficient. You are advised to check the
- list of options whether a NixOS
- module for the package does not exist.
-
-
-
- You can get a list of the available packages as follows:
-
-
-$ nix-env -qaP '*' --description
-nixos.firefox firefox-23.0 Mozilla Firefox - the browser, reloaded
-...
-
-
- The first column in the output is the attribute
- name, such as nixos.thunderbird.
-
-
- Note: the nixos prefix tells us that we want to
- get the package from the nixos channel and works
- only in CLI tools. In declarative configuration use
- pkgs prefix (variable).
-
-
- To uninstall a package, simply remove it from
- and run
- nixos-rebuild switch.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/file-systems.chapter.xml b/nixos/doc/manual/from_md/configuration/file-systems.chapter.xml
deleted file mode 100644
index e5285c797555..000000000000
--- a/nixos/doc/manual/from_md/configuration/file-systems.chapter.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
- File Systems
-
- You can define file systems using the fileSystems
- configuration option. For instance, the following definition causes
- NixOS to mount the Ext4 file system on device
- /dev/disk/by-label/data onto the mount point
- /data:
-
-
-fileSystems."/data" =
- { device = "/dev/disk/by-label/data";
- fsType = "ext4";
- };
-
-
- This will create an entry in /etc/fstab, which
- will generate a corresponding
- systemd.mount
- unit via
- systemd-fstab-generator.
- The filesystem will be mounted automatically unless
- "noauto" is present in
- options.
- "noauto" filesystems can be mounted
- explicitly using systemctl e.g.
- systemctl start data.mount. Mount points are
- created automatically if they don’t already exist. For
- device, it’s best to use the topology-independent
- device aliases in /dev/disk/by-label and
- /dev/disk/by-uuid, as these don’t change if the
- topology changes (e.g. if a disk is moved to another IDE
- controller).
-
-
- You can usually omit the file system type
- (fsType), since mount can
- usually detect the type and load the necessary kernel module
- automatically. However, if the file system is needed at early boot
- (in the initial ramdisk) and is not ext2,
- ext3 or ext4, then it’s best
- to specify fsType to ensure that the kernel
- module is available.
-
-
-
- System startup will fail if any of the filesystems fails to mount,
- dropping you to the emergency shell. You can make a mount
- asynchronous and non-critical by adding
- options = [ "nofail" ];.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/firewall.section.xml b/nixos/doc/manual/from_md/configuration/firewall.section.xml
deleted file mode 100644
index 6e1ffab72c54..000000000000
--- a/nixos/doc/manual/from_md/configuration/firewall.section.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
- Firewall
-
- NixOS has a simple stateful firewall that blocks incoming
- connections and other unexpected packets. The firewall applies to
- both IPv4 and IPv6 traffic. It is enabled by default. It can be
- disabled as follows:
-
-
-networking.firewall.enable = false;
-
-
- If the firewall is enabled, you can open specific TCP ports to the
- outside world:
-
-
-networking.firewall.allowedTCPPorts = [ 80 443 ];
-
-
- Note that TCP port 22 (ssh) is opened automatically if the SSH
- daemon is enabled
- (services.openssh.enable = true). UDP ports can
- be opened through
- .
-
-
- To open ranges of TCP ports:
-
-
-networking.firewall.allowedTCPPortRanges = [
- { from = 4000; to = 4007; }
- { from = 8000; to = 8010; }
-];
-
-
- Similarly, UDP port ranges can be opened through
- .
-
-
diff --git a/nixos/doc/manual/from_md/configuration/gpu-accel.chapter.xml b/nixos/doc/manual/from_md/configuration/gpu-accel.chapter.xml
deleted file mode 100644
index c95d3dc86525..000000000000
--- a/nixos/doc/manual/from_md/configuration/gpu-accel.chapter.xml
+++ /dev/null
@@ -1,281 +0,0 @@
-
- GPU acceleration
-
- NixOS provides various APIs that benefit from GPU hardware
- acceleration, such as VA-API and VDPAU for video playback; OpenGL
- and Vulkan for 3D graphics; and OpenCL for general-purpose
- computing. This chapter describes how to set up GPU hardware
- acceleration (as far as this is not done automatically) and how to
- verify that hardware acceleration is indeed used.
-
-
- Most of the aforementioned APIs are agnostic with regards to which
- display server is used. Consequently, these instructions should
- apply both to the X Window System and Wayland compositors.
-
-
- OpenCL
-
- OpenCL
- is a general compute API. It is used by various applications such
- as Blender and Darktable to accelerate certain operations.
-
-
- OpenCL applications load drivers through the Installable
- Client Driver (ICD) mechanism. In this mechanism, an
- ICD file specifies the path to the OpenCL driver for a particular
- GPU family. In NixOS, there are two ways to make ICD files visible
- to the ICD loader. The first is through the
- OCL_ICD_VENDORS environment variable. This
- variable can contain a directory which is scanned by the ICL
- loader for ICD files. For example:
-
-
-$ export \
- OCL_ICD_VENDORS=`nix-build '<nixpkgs>' --no-out-link -A rocm-opencl-icd`/etc/OpenCL/vendors/
-
-
- The second mechanism is to add the OpenCL driver package to
- . This links
- the ICD file under /run/opengl-driver, where it
- will be visible to the ICD loader.
-
-
- The proper installation of OpenCL drivers can be verified through
- the clinfo command of the clinfo package. This
- command will report the number of hardware devices that is found
- and give detailed information for each device:
-
-
-$ clinfo | head -n3
-Number of platforms 1
-Platform Name AMD Accelerated Parallel Processing
-Platform Vendor Advanced Micro Devices, Inc.
-
-
- AMD
-
- Modern AMD
- Graphics
- Core Next (GCN) GPUs are supported through the
- rocm-opencl-icd package. Adding this package to
- enables
- OpenCL support:
-
-
-hardware.opengl.extraPackages = [
- rocm-opencl-icd
-];
-
-
-
- Intel
-
- Intel
- Gen8 and later GPUs are supported by the Intel NEO OpenCL
- runtime that is provided by the intel-compute-runtime package.
- For Gen7 GPUs, the deprecated Beignet runtime can be used, which
- is provided by the beignet package. The proprietary Intel OpenCL
- runtime, in the intel-ocl package, is an alternative for Gen7
- GPUs.
-
-
- The intel-compute-runtime, beignet, or intel-ocl package can be
- added to to
- enable OpenCL support. For example, for Gen8 and later GPUs, the
- following configuration can be used:
-
-
-hardware.opengl.extraPackages = [
- intel-compute-runtime
-];
-
-
-
-
- Vulkan
-
- Vulkan
- is a graphics and compute API for GPUs. It is used directly by
- games or indirectly though compatibility layers like
- DXVK.
-
-
- By default, if
- is enabled, mesa is installed and provides Vulkan for supported
- hardware.
-
-
- Similar to OpenCL, Vulkan drivers are loaded through the
- Installable Client Driver (ICD) mechanism.
- ICD files for Vulkan are JSON files that specify the path to the
- driver library and the supported Vulkan version. All successfully
- loaded drivers are exposed to the application as different GPUs.
- In NixOS, there are two ways to make ICD files visible to Vulkan
- applications: an environment variable and a module option.
-
-
- The first option is through the
- VK_ICD_FILENAMES environment variable. This
- variable can contain multiple JSON files, separated by
- :. For example:
-
-
-$ export \
- VK_ICD_FILENAMES=`nix-build '<nixpkgs>' --no-out-link -A amdvlk`/share/vulkan/icd.d/amd_icd64.json
-
-
- The second mechanism is to add the Vulkan driver package to
- . This links
- the ICD file under /run/opengl-driver, where it
- will be visible to the ICD loader.
-
-
- The proper installation of Vulkan drivers can be verified through
- the vulkaninfo command of the vulkan-tools
- package. This command will report the hardware devices and drivers
- found, in this example output amdvlk and radv:
-
-
-$ vulkaninfo | grep GPU
- GPU id : 0 (Unknown AMD GPU)
- GPU id : 1 (AMD RADV NAVI10 (LLVM 9.0.1))
- ...
-GPU0:
- deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
- deviceName = Unknown AMD GPU
-GPU1:
- deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
-
-
- A simple graphical application that uses Vulkan is
- vkcube from the vulkan-tools package.
-
-
- AMD
-
- Modern AMD
- Graphics
- Core Next (GCN) GPUs are supported through either radv,
- which is part of mesa, or the amdvlk package. Adding the amdvlk
- package to
- makes amdvlk the default driver and hides radv and lavapipe from
- the device list. A specific driver can be forced as follows:
-
-
-hardware.opengl.extraPackages = [
- pkgs.amdvlk
-];
-
-# To enable Vulkan support for 32-bit applications, also add:
-hardware.opengl.extraPackages32 = [
- pkgs.driversi686Linux.amdvlk
-];
-
-# Force radv
-environment.variables.AMD_VULKAN_ICD = "RADV";
-# Or
-environment.variables.VK_ICD_FILENAMES =
- "/run/opengl-driver/share/vulkan/icd.d/radeon_icd.x86_64.json";
-
-
-
-
- VA-API
-
- VA-API
- (Video Acceleration API) is an open-source library and API
- specification, which provides access to graphics hardware
- acceleration capabilities for video processing.
-
-
- VA-API drivers are loaded by libva. The version
- in nixpkgs is built to search the opengl driver path, so drivers
- can be installed in
- .
-
-
- VA-API can be tested using:
-
-
-$ nix-shell -p libva-utils --run vainfo
-
-
- Intel
-
- Modern Intel GPUs use the iHD driver, which can be installed
- with:
-
-
-hardware.opengl.extraPackages = [
- intel-media-driver
-];
-
-
- Older Intel GPUs use the i965 driver, which can be installed
- with:
-
-
-hardware.opengl.extraPackages = [
- vaapiIntel
-];
-
-
-
-
- Common issues
-
- User permissions
-
- Except where noted explicitly, it should not be necessary to
- adjust user permissions to use these acceleration APIs. In the
- default configuration, GPU devices have world-read/write
- permissions (/dev/dri/renderD*) or are tagged
- as uaccess
- (/dev/dri/card*). The access control lists of
- devices with the uaccess tag will be updated
- automatically when a user logs in through
- systemd-logind. For example, if the user
- alice is logged in, the access control list
- should look as follows:
-
-
-$ getfacl /dev/dri/card0
-# file: dev/dri/card0
-# owner: root
-# group: video
-user::rw-
-user:alice:rw-
-group::rw-
-mask::rw-
-other::---
-
-
- If you disabled (this functionality of)
- systemd-logind, you may need to add the user
- to the video group and log in again.
-
-
-
- Mixing different versions of nixpkgs
-
- The Installable Client Driver (ICD)
- mechanism used by OpenCL and Vulkan loads runtimes into its
- address space using dlopen. Mixing an ICD
- loader mechanism and runtimes from different version of nixpkgs
- may not work. For example, if the ICD loader uses an older
- version of glibc than the runtime, the runtime may not be
- loadable due to missing symbols. Unfortunately, the loader will
- generally be quiet about such issues.
-
-
- If you suspect that you are running into library version
- mismatches between an ICL loader and a runtime, you could run an
- application with the LD_DEBUG variable set to
- get more diagnostic information. For example, OpenCL can be
- tested with LD_DEBUG=files clinfo, which
- should report missing symbols.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/ipv4-config.section.xml b/nixos/doc/manual/from_md/configuration/ipv4-config.section.xml
deleted file mode 100644
index 49ec6f5952ec..000000000000
--- a/nixos/doc/manual/from_md/configuration/ipv4-config.section.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
- IPv4 Configuration
-
- By default, NixOS uses DHCP (specifically,
- dhcpcd) to automatically configure network
- interfaces. However, you can configure an interface manually as
- follows:
-
-
-networking.interfaces.eth0.ipv4.addresses = [ {
- address = "192.168.1.2";
- prefixLength = 24;
-} ];
-
-
- Typically you’ll also want to set a default gateway and set of name
- servers:
-
-
-networking.defaultGateway = "192.168.1.1";
-networking.nameservers = [ "8.8.8.8" ];
-
-
-
- Statically configured interfaces are set up by the systemd service
- interface-name-cfg.service. The default gateway
- and name server configuration is performed by
- network-setup.service.
-
-
-
- The host name is set using
- :
-
-
-networking.hostName = "cartman";
-
-
- The default host name is nixos. Set it to the
- empty string ("") to allow the DHCP
- server to provide the host name.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/ipv6-config.section.xml b/nixos/doc/manual/from_md/configuration/ipv6-config.section.xml
deleted file mode 100644
index 2adb10622624..000000000000
--- a/nixos/doc/manual/from_md/configuration/ipv6-config.section.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
- IPv6 Configuration
-
- IPv6 is enabled by default. Stateless address autoconfiguration is
- used to automatically assign IPv6 addresses to all interfaces, and
- Privacy Extensions (RFC 4946) are enabled by default. You can adjust
- the default for this by setting
- . This option may be
- overridden on a per-interface basis by
- . You
- can disable IPv6 support globally by setting:
-
-
-networking.enableIPv6 = false;
-
-
- You can disable IPv6 on a single interface using a normal sysctl (in
- this example, we use interface eth0):
-
-
-boot.kernel.sysctl."net.ipv6.conf.eth0.disable_ipv6" = true;
-
-
- As with IPv4 networking interfaces are automatically configured via
- DHCPv6. You can configure an interface manually:
-
-
-networking.interfaces.eth0.ipv6.addresses = [ {
- address = "fe00:aa:bb:cc::2";
- prefixLength = 64;
-} ];
-
-
- For configuring a gateway, optionally with explicitly specified
- interface:
-
-
-networking.defaultGateway6 = {
- address = "fe00::1";
- interface = "enp0s3";
-};
-
-
- See for similar examples and additional
- information.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/kubernetes.chapter.xml b/nixos/doc/manual/from_md/configuration/kubernetes.chapter.xml
deleted file mode 100644
index da9ba323f18c..000000000000
--- a/nixos/doc/manual/from_md/configuration/kubernetes.chapter.xml
+++ /dev/null
@@ -1,115 +0,0 @@
-
- Kubernetes
-
- The NixOS Kubernetes module is a collective term for a handful of
- individual submodules implementing the Kubernetes cluster
- components.
-
-
- There are generally two ways of enabling Kubernetes on NixOS. One
- way is to enable and configure cluster components appropriately by
- hand:
-
-
-services.kubernetes = {
- apiserver.enable = true;
- controllerManager.enable = true;
- scheduler.enable = true;
- addonManager.enable = true;
- proxy.enable = true;
- flannel.enable = true;
-};
-
-
- Another way is to assign cluster roles (master and/or
- node) to the host. This enables apiserver,
- controllerManager, scheduler, addonManager, kube-proxy and etcd:
-
-
-services.kubernetes.roles = [ "master" ];
-
-
- While this will enable the kubelet and kube-proxy only:
-
-
-services.kubernetes.roles = [ "node" ];
-
-
- Assigning both the master and node roles is usable if you want a
- single node Kubernetes cluster for dev or testing purposes:
-
-
-services.kubernetes.roles = [ "master" "node" ];
-
-
- Note: Assigning either role will also default both
- and
- to true. This
- sets up flannel as CNI and activates automatic PKI bootstrapping.
-
-
-
- As of NixOS 19.03, it is mandatory to configure:
- . The
- masterAddress must be resolveable and routeable by all cluster
- nodes. In single node clusters, this can be set to
- localhost.
-
-
-
- Role-based access control (RBAC) authorization mode is enabled by
- default. This means that anonymous requests to the apiserver secure
- port will expectedly cause a permission denied error. All cluster
- components must therefore be configured with x509 certificates for
- two-way tls communication. The x509 certificate subject section
- determines the roles and permissions granted by the apiserver to
- perform clusterwide or namespaced operations. See also:
-
- Using RBAC Authorization.
-
-
- The NixOS kubernetes module provides an option for automatic
- certificate bootstrapping and configuration,
- . The PKI
- bootstrapping process involves setting up a certificate authority
- (CA) daemon (cfssl) on the kubernetes master node. cfssl generates a
- CA-cert for the cluster, and uses the CA-cert for signing
- subordinate certs issued to each of the cluster components.
- Subsequently, the certmgr daemon monitors active certificates and
- renews them when needed. For single node Kubernetes clusters,
- setting = true
- is sufficient and no further action is required. For joining extra
- node machines to an existing cluster on the other hand, establishing
- initial trust is mandatory.
-
-
- To add new nodes to the cluster: On any (non-master) cluster node
- where is
- enabled, the helper script
- nixos-kubernetes-node-join is available on PATH.
- Given a token on stdin, it will copy the token to the kubernetes
- secrets directory and restart the certmgr service. As requested
- certificates are issued, the script will restart kubernetes cluster
- components as needed for them to pick up new keypairs.
-
-
-
- Multi-master (HA) clusters are not supported by the easyCerts
- module.
-
-
-
- In order to interact with an RBAC-enabled cluster as an
- administrator, one needs to have cluster-admin privileges. By
- default, when easyCerts is enabled, a cluster-admin kubeconfig file
- is generated and linked into
- /etc/kubernetes/cluster-admin.kubeconfig as
- determined by
- .
- export KUBECONFIG=/etc/kubernetes/cluster-admin.kubeconfig
- will make kubectl use this kubeconfig to access and authenticate the
- cluster. The cluster-admin kubeconfig references an auto-generated
- keypair owned by root. Thus, only root on the kubernetes master may
- obtain cluster-admin rights by means of this file.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/linux-kernel.chapter.xml b/nixos/doc/manual/from_md/configuration/linux-kernel.chapter.xml
deleted file mode 100644
index f889306d51c0..000000000000
--- a/nixos/doc/manual/from_md/configuration/linux-kernel.chapter.xml
+++ /dev/null
@@ -1,221 +0,0 @@
-
- Linux Kernel
-
- You can override the Linux kernel and associated packages using the
- option boot.kernelPackages. For instance, this
- selects the Linux 3.10 kernel:
-
-
-boot.kernelPackages = pkgs.linuxKernel.packages.linux_3_10;
-
-
- Note that this not only replaces the kernel, but also packages that
- are specific to the kernel version, such as the NVIDIA video
- drivers. This ensures that driver packages are consistent with the
- kernel.
-
-
- While pkgs.linuxKernel.packages contains all
- available kernel packages, you may want to use one of the
- unversioned pkgs.linuxPackages_* aliases such as
- pkgs.linuxPackages_latest, that are kept up to
- date with new versions.
-
-
- Please note that the current convention in NixOS is to only keep
- actively maintained kernel versions on both unstable and the
- currently supported stable release(s) of NixOS. This means that a
- non-longterm kernel will be removed after it’s abandoned by the
- kernel developers, even on stable NixOS versions. If you pin your
- kernel onto a non-longterm version, expect your evaluation to fail
- as soon as the version is out of maintenance.
-
-
- Longterm versions of kernels will be removed before the next stable
- NixOS that will exceed the maintenance period of the kernel version.
-
-
- The default Linux kernel configuration should be fine for most
- users. You can see the configuration of your current kernel with the
- following command:
-
-
-zcat /proc/config.gz
-
-
- If you want to change the kernel configuration, you can use the
- packageOverrides feature (see
- ). For instance, to
- enable support for the kernel debugger KGDB:
-
-
-nixpkgs.config.packageOverrides = pkgs: pkgs.lib.recursiveUpdate pkgs {
- linuxKernel.kernels.linux_5_10 = pkgs.linuxKernel.kernels.linux_5_10.override {
- extraConfig = ''
- KGDB y
- '';
- };
-};
-
-
- extraConfig takes a list of Linux kernel
- configuration options, one per line. The name of the option should
- not include the prefix CONFIG_. The option value
- is typically y, n or
- m (to build something as a kernel module).
-
-
- Kernel modules for hardware devices are generally loaded
- automatically by udev. You can force a module to
- be loaded via , e.g.
-
-
-boot.kernelModules = [ "fuse" "kvm-intel" "coretemp" ];
-
-
- If the module is required early during the boot (e.g. to mount the
- root file system), you can use
- :
-
-
-boot.initrd.kernelModules = [ "cifs" ];
-
-
- This causes the specified modules and their dependencies to be added
- to the initial ramdisk.
-
-
- Kernel runtime parameters can be set through
- , e.g.
-
-
-boot.kernel.sysctl."net.ipv4.tcp_keepalive_time" = 120;
-
-
- sets the kernel’s TCP keepalive time to 120 seconds. To see the
- available parameters, run sysctl -a.
-
-
- Building a custom kernel
-
- You can customize the default kernel configuration by overriding
- the arguments for your kernel package:
-
-
-pkgs.linux_latest.override {
- ignoreConfigErrors = true;
- autoModules = false;
- kernelPreferBuiltin = true;
- extraStructuredConfig = with lib.kernel; {
- DEBUG_KERNEL = yes;
- FRAME_POINTER = yes;
- KGDB = yes;
- KGDB_SERIAL_CONSOLE = yes;
- DEBUG_INFO = yes;
- };
-}
-
-
- See pkgs/os-specific/linux/kernel/generic.nix
- for details on how these arguments affect the generated
- configuration. You can also build a custom version of Linux by
- calling pkgs.buildLinux directly, which
- requires the src and version
- arguments to be specified.
-
-
- To use your custom kernel package in your NixOS configuration, set
-
-
-boot.kernelPackages = pkgs.linuxPackagesFor yourCustomKernel;
-
-
- Note that this method will use the common configuration defined in
- pkgs/os-specific/linux/kernel/common-config.nix,
- which is suitable for a NixOS system.
-
-
- If you already have a generated configuration file, you can build
- a kernel that uses it with
- pkgs.linuxManualConfig:
-
-
-let
- baseKernel = pkgs.linux_latest;
-in pkgs.linuxManualConfig {
- inherit (baseKernel) src modDirVersion;
- version = "${baseKernel.version}-custom";
- configfile = ./my_kernel_config;
- allowImportFromDerivation = true;
-}
-
-
-
- The build will fail if modDirVersion does not
- match the source’s kernel.release file, so
- modDirVersion should remain tied to
- src.
-
-
-
- To edit the .config file for Linux X.Y, proceed
- as follows:
-
-
-$ nix-shell '<nixpkgs>' -A linuxKernel.kernels.linux_X_Y.configEnv
-$ unpackPhase
-$ cd linux-*
-$ make nconfig
-
-
-
- Developing kernel modules
-
- When developing kernel modules it’s often convenient to run
- edit-compile-run loop as quickly as possible. See below snippet as
- an example of developing mellanox drivers.
-
-
-$ nix-build '<nixpkgs>' -A linuxPackages.kernel.dev
-$ nix-shell '<nixpkgs>' -A linuxPackages.kernel
-$ unpackPhase
-$ cd linux-*
-$ make -C $dev/lib/modules/*/build M=$(pwd)/drivers/net/ethernet/mellanox modules
-# insmod ./drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko
-
-
-
- ZFS
-
- It’s a common issue that the latest stable version of ZFS doesn’t
- support the latest available Linux kernel. It is recommended to
- use the latest available LTS that’s compatible with ZFS. Usually
- this is the default kernel provided by nixpkgs (i.e.
- pkgs.linuxPackages).
-
-
- Alternatively, it’s possible to pin the system to the latest
- available kernel version that is supported by
- ZFS like this:
-
-
-{
- boot.kernelPackages = pkgs.zfs.latestCompatibleLinuxPackages;
-}
-
-
- Please note that the version this attribute points to isn’t
- monotonic because the latest kernel version only refers to kernel
- versions supported by the Linux developers. In other words, the
- latest kernel version that ZFS is compatible with may decrease
- over time.
-
-
- An example: the latest version ZFS is compatible with is 5.19
- which is a non-longterm version. When 5.19 is out of maintenance,
- the latest supported kernel version is 5.15 because it’s longterm
- and the versions 5.16, 5.17 and 5.18 are already out of
- maintenance because they’re non-longterm.
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/luks-file-systems.section.xml b/nixos/doc/manual/from_md/configuration/luks-file-systems.section.xml
deleted file mode 100644
index 144a5acecae3..000000000000
--- a/nixos/doc/manual/from_md/configuration/luks-file-systems.section.xml
+++ /dev/null
@@ -1,84 +0,0 @@
-
- LUKS-Encrypted File Systems
-
- NixOS supports file systems that are encrypted using
- LUKS (Linux Unified Key Setup). For example,
- here is how you create an encrypted Ext4 file system on the device
- /dev/disk/by-uuid/3f6b0024-3a44-4fde-a43a-767b872abe5d:
-
-
-# cryptsetup luksFormat /dev/disk/by-uuid/3f6b0024-3a44-4fde-a43a-767b872abe5d
-
-WARNING!
-========
-This will overwrite data on /dev/disk/by-uuid/3f6b0024-3a44-4fde-a43a-767b872abe5d irrevocably.
-
-Are you sure? (Type uppercase yes): YES
-Enter LUKS passphrase: ***
-Verify passphrase: ***
-
-# cryptsetup luksOpen /dev/disk/by-uuid/3f6b0024-3a44-4fde-a43a-767b872abe5d crypted
-Enter passphrase for /dev/disk/by-uuid/3f6b0024-3a44-4fde-a43a-767b872abe5d: ***
-
-# mkfs.ext4 /dev/mapper/crypted
-
-
- The LUKS volume should be automatically picked up by
- nixos-generate-config, but you might want to
- verify that your hardware-configuration.nix looks
- correct. To manually ensure that the system is automatically mounted
- at boot time as /, add the following to
- configuration.nix:
-
-
-boot.initrd.luks.devices.crypted.device = "/dev/disk/by-uuid/3f6b0024-3a44-4fde-a43a-767b872abe5d";
-fileSystems."/".device = "/dev/mapper/crypted";
-
-
- Should grub be used as bootloader, and /boot is
- located on an encrypted partition, it is necessary to add the
- following grub option:
-
-
-boot.loader.grub.enableCryptodisk = true;
-
-
- FIDO2
-
- NixOS also supports unlocking your LUKS-Encrypted file system
- using a FIDO2 compatible token. In the following example, we will
- create a new FIDO2 credential and add it as a new key to our
- existing device /dev/sda2:
-
-
-# export FIDO2_LABEL="/dev/sda2 @ $HOSTNAME"
-# fido2luks credential "$FIDO2_LABEL"
-f1d00200108b9d6e849a8b388da457688e3dd653b4e53770012d8f28e5d3b269865038c346802f36f3da7278b13ad6a3bb6a1452e24ebeeaa24ba40eef559b1b287d2a2f80b7
-
-# fido2luks -i add-key /dev/sda2 f1d00200108b9d6e849a8b388da457688e3dd653b4e53770012d8f28e5d3b269865038c346802f36f3da7278b13ad6a3bb6a1452e24ebeeaa24ba40eef559b1b287d2a2f80b7
-Password:
-Password (again):
-Old password:
-Old password (again):
-Added to key to device /dev/sda2, slot: 2
-
-
- To ensure that this file system is decrypted using the FIDO2
- compatible key, add the following to
- configuration.nix:
-
-
-boot.initrd.luks.fido2Support = true;
-boot.initrd.luks.devices."/dev/sda2".fido2.credential = "f1d00200108b9d6e849a8b388da457688e3dd653b4e53770012d8f28e5d3b269865038c346802f36f3da7278b13ad6a3bb6a1452e24ebeeaa24ba40eef559b1b287d2a2f80b7";
-
-
- You can also use the FIDO2 passwordless setup, but for security
- reasons, you might want to enable it only when your device is PIN
- protected, such as
- Trezor.
-
-
-boot.initrd.luks.devices."/dev/sda2".fido2.passwordLess = true;
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/modularity.section.xml b/nixos/doc/manual/from_md/configuration/modularity.section.xml
deleted file mode 100644
index 987b2fc43c01..000000000000
--- a/nixos/doc/manual/from_md/configuration/modularity.section.xml
+++ /dev/null
@@ -1,152 +0,0 @@
-
- Modularity
-
- The NixOS configuration mechanism is modular. If your
- configuration.nix becomes too big, you can split
- it into multiple files. Likewise, if you have multiple NixOS
- configurations (e.g. for different computers) with some commonality,
- you can move the common configuration into a shared file.
-
-
- Modules have exactly the same syntax as
- configuration.nix. In fact,
- configuration.nix is itself a module. You can use
- other modules by including them from
- configuration.nix, e.g.:
-
-
-{ config, pkgs, ... }:
-
-{ imports = [ ./vpn.nix ./kde.nix ];
- services.httpd.enable = true;
- environment.systemPackages = [ pkgs.emacs ];
- ...
-}
-
-
- Here, we include two modules from the same directory,
- vpn.nix and kde.nix. The
- latter might look like this:
-
-
-{ config, pkgs, ... }:
-
-{ services.xserver.enable = true;
- services.xserver.displayManager.sddm.enable = true;
- services.xserver.desktopManager.plasma5.enable = true;
- environment.systemPackages = [ pkgs.vim ];
-}
-
-
- Note that both configuration.nix and
- kde.nix define the option
- . When multiple
- modules define an option, NixOS will try to
- merge the definitions. In the case of
- , that’s easy: the
- lists of packages can simply be concatenated. The value in
- configuration.nix is merged last, so for
- list-type options, it will appear at the end of the merged list. If
- you want it to appear first, you can use
- mkBefore:
-
-
-boot.kernelModules = mkBefore [ "kvm-intel" ];
-
-
- This causes the kvm-intel kernel module to be
- loaded before any other kernel modules.
-
-
- For other types of options, a merge may not be possible. For
- instance, if two modules define
- ,
- nixos-rebuild will give an error:
-
-
-The unique option `services.httpd.adminAddr' is defined multiple times, in `/etc/nixos/httpd.nix' and `/etc/nixos/configuration.nix'.
-
-
- When that happens, it’s possible to force one definition take
- precedence over the others:
-
-
-services.httpd.adminAddr = pkgs.lib.mkForce "bob@example.org";
-
-
- When using multiple modules, you may need to access configuration
- values defined in other modules. This is what the
- config function argument is for: it contains the
- complete, merged system configuration. That is,
- config is the result of combining the
- configurations returned by every module
-
- If you’re wondering how it’s possible that the (indirect)
- result of a function is passed as an
- input to that same function: that’s because
- Nix is a lazy language — it only computes values
- when they are needed. This works as long as no individual
- configuration value depends on itself.
-
- . For example, here is a module that adds some packages
- to only if
- is set to
- true somewhere else:
-
-
-{ config, pkgs, ... }:
-
-{ environment.systemPackages =
- if config.services.xserver.enable then
- [ pkgs.firefox
- pkgs.thunderbird
- ]
- else
- [ ];
-}
-
-
- With multiple modules, it may not be obvious what the final value of
- a configuration option is. The command
- nixos-option allows you to find out:
-
-
-$ nixos-option services.xserver.enable
-true
-
-$ nixos-option boot.kernelModules
-[ "tun" "ipv6" "loop" ... ]
-
-
- Interactive exploration of the configuration is possible using
- nix repl, a read-eval-print loop for Nix
- expressions. A typical use:
-
-
-$ nix repl '<nixpkgs/nixos>'
-
-nix-repl> config.networking.hostName
-"mandark"
-
-nix-repl> map (x: x.hostName) config.services.httpd.virtualHosts
-[ "example.org" "example.gov" ]
-
-
- While abstracting your configuration, you may find it useful to
- generate modules using code, instead of writing files. The example
- below would have the same effect as importing a file which sets
- those options.
-
-
-{ config, pkgs, ... }:
-
-let netConfig = hostName: {
- networking.hostName = hostName;
- networking.useDHCP = false;
-};
-
-in
-
-{ imports = [ (netConfig "nixos.localdomain") ]; }
-
-
diff --git a/nixos/doc/manual/from_md/configuration/network-manager.section.xml b/nixos/doc/manual/from_md/configuration/network-manager.section.xml
deleted file mode 100644
index c49618b4b942..000000000000
--- a/nixos/doc/manual/from_md/configuration/network-manager.section.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-
- NetworkManager
-
- To facilitate network configuration, some desktop environments use
- NetworkManager. You can enable NetworkManager by setting:
-
-
-networking.networkmanager.enable = true;
-
-
- some desktop managers (e.g., GNOME) enable NetworkManager
- automatically for you.
-
-
- All users that should have permission to change network settings
- must belong to the networkmanager group:
-
-
-users.users.alice.extraGroups = [ "networkmanager" ];
-
-
- NetworkManager is controlled using either nmcli
- or nmtui (curses-based terminal user interface).
- See their manual pages for details on their usage. Some desktop
- environments (GNOME, KDE) have their own configuration tools for
- NetworkManager. On XFCE, there is no configuration tool for
- NetworkManager by default: by enabling
- , the graphical
- applet will be installed and will launch automatically when the
- graphical session is started.
-
-
-
- networking.networkmanager and
- networking.wireless (WPA Supplicant) can be
- used together if desired. To do this you need to instruct
- NetworkManager to ignore those interfaces like:
-
-
-networking.networkmanager.unmanaged = [
- "*" "except:type:wwan" "except:type:gsm"
-];
-
-
- Refer to the option description for the exact syntax and
- references to external documentation.
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/networking.chapter.xml b/nixos/doc/manual/from_md/configuration/networking.chapter.xml
deleted file mode 100644
index 2ed86ea3b589..000000000000
--- a/nixos/doc/manual/from_md/configuration/networking.chapter.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
- Networking
-
- This section describes how to configure networking components on
- your NixOS machine.
-
-
-
-
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/package-mgmt.chapter.xml b/nixos/doc/manual/from_md/configuration/package-mgmt.chapter.xml
deleted file mode 100644
index d3727edbe08d..000000000000
--- a/nixos/doc/manual/from_md/configuration/package-mgmt.chapter.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
- Package Management
-
- This section describes how to add additional packages to your
- system. NixOS has two distinct styles of package management:
-
-
-
-
- Declarative, where you declare what
- packages you want in your configuration.nix.
- Every time you run nixos-rebuild, NixOS will
- ensure that you get a consistent set of binaries corresponding
- to your specification.
-
-
-
-
- Ad hoc, where you install, upgrade and
- uninstall packages via the nix-env command.
- This style allows mixing packages from different Nixpkgs
- versions. It’s the only choice for non-root users.
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles.chapter.xml b/nixos/doc/manual/from_md/configuration/profiles.chapter.xml
deleted file mode 100644
index f3aacfc0a245..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles.chapter.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
- Profiles
-
- In some cases, it may be desirable to take advantage of
- commonly-used, predefined configurations provided by nixpkgs, but
- different from those that come as default. This is a role fulfilled
- by NixOS’s Profiles, which come as files living in
- <nixpkgs/nixos/modules/profiles>. That is
- to say, expected usage is to add them to the imports list of your
- /etc/configuration.nix as such:
-
-
-imports = [
- <nixpkgs/nixos/modules/profiles/profile-name.nix>
-];
-
-
- Even if some of these profiles seem only useful in the context of
- install media, many are actually intended to be used in real
- installs.
-
-
- What follows is a brief explanation on the purpose and use-case for
- each profile. Detailing each option configured by each one is out of
- scope.
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/all-hardware.section.xml b/nixos/doc/manual/from_md/configuration/profiles/all-hardware.section.xml
deleted file mode 100644
index 43ac5edea7f8..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/all-hardware.section.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
- All Hardware
-
- Enables all hardware supported by NixOS: i.e., all firmware is
- included, and all devices from which one may boot are enabled in the
- initrd. Its primary use is in the NixOS installation CDs.
-
-
- The enabled kernel modules include support for SATA and PATA, SCSI
- (partially), USB, Firewire (untested), Virtio (QEMU, KVM, etc.),
- VMware, and Hyper-V. Additionally,
- is enabled, and
- the firmware for the ZyDAS ZD1211 chipset is specifically installed.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/base.section.xml b/nixos/doc/manual/from_md/configuration/profiles/base.section.xml
deleted file mode 100644
index 83d35bd28676..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/base.section.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-
- Base
-
- Defines the software packages included in the minimal
- installation CD. It installs several utilities useful in a simple
- recovery or install media, such as a text-mode web browser, and
- tools for manipulating block devices, networking, hardware
- diagnostics, and filesystems (with their respective kernel modules).
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/clone-config.section.xml b/nixos/doc/manual/from_md/configuration/profiles/clone-config.section.xml
deleted file mode 100644
index 9430b49ea33d..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/clone-config.section.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
- Clone Config
-
- This profile is used in installer images. It provides an editable
- configuration.nix that imports all the modules that were also used
- when creating the image in the first place. As a result it allows
- users to edit and rebuild the live-system.
-
-
- On images where the installation media also becomes an installation
- target, copying over configuration.nix should be
- disabled by setting installer.cloneConfig to
- false. For example, this is done in
- sd-image-aarch64-installer.nix.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/demo.section.xml b/nixos/doc/manual/from_md/configuration/profiles/demo.section.xml
deleted file mode 100644
index 09c2680a1067..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/demo.section.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-
- Demo
-
- This profile just enables a demo user, with
- password demo, uid 1000,
- wheel group and
- autologin
- in the SDDM display manager.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/docker-container.section.xml b/nixos/doc/manual/from_md/configuration/profiles/docker-container.section.xml
deleted file mode 100644
index 97c2a92dcab5..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/docker-container.section.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
- Docker Container
-
- This is the profile from which the Docker images are generated. It
- prepares a working system by importing the
- Minimal and
- Clone Config
- profiles, and setting appropriate configuration options that are
- useful inside a container context, like
- .
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/graphical.section.xml b/nixos/doc/manual/from_md/configuration/profiles/graphical.section.xml
deleted file mode 100644
index 1b109519d436..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/graphical.section.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
- Graphical
-
- Defines a NixOS configuration with the Plasma 5 desktop. It’s used
- by the graphical installation CD.
-
-
- It sets ,
- ,
- ,
- and to true.
- It also includes glxinfo and firefox in the system packages list.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/hardened.section.xml b/nixos/doc/manual/from_md/configuration/profiles/hardened.section.xml
deleted file mode 100644
index 1fd5a9179887..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/hardened.section.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
- Hardened
-
- A profile with most (vanilla) hardening options enabled by default,
- potentially at the cost of stability, features and performance.
-
-
- This includes a hardened kernel, and limiting the system information
- available to processes through the /sys and
- /proc filesystems. It also disables the User
- Namespaces feature of the kernel, which stops Nix from being able to
- build anything (this particular setting can be overridden via
- ). See the
- profile
- source for further detail on which settings are altered.
-
-
-
- This profile enables options that are known to affect system
- stability. If you experience any stability issues when using the
- profile, try disabling it. If you report an issue and use this
- profile, always mention that you do.
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/headless.section.xml b/nixos/doc/manual/from_md/configuration/profiles/headless.section.xml
deleted file mode 100644
index 0910b9ffaad2..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/headless.section.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
- Headless
-
- Common configuration for headless machines (e.g., Amazon EC2
- instances).
-
-
- Disables sound,
- vesa, serial consoles,
- emergency
- mode, grub
- splash images and configures the kernel to reboot
- automatically on panic.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/installation-device.section.xml b/nixos/doc/manual/from_md/configuration/profiles/installation-device.section.xml
deleted file mode 100644
index 837e69df06e1..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/installation-device.section.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
- Installation Device
-
- Provides a basic configuration for installation devices like CDs.
- This enables redistributable firmware, includes the
- Clone Config profile
- and a copy of the Nixpkgs channel, so
- nixos-install works out of the box.
-
-
- Documentation for
- Nixpkgs and
- NixOS are
- forcefully enabled (to override the
- Minimal profile
- preference); the NixOS manual is shown automatically on TTY 8,
- udisks is disabled. Autologin is enabled as nixos
- user, while passwordless login as both root and
- nixos is possible. Passwordless
- sudo is enabled too.
- wpa_supplicant
- is enabled, but configured to not autostart.
-
-
- It is explained how to login, start the ssh server, and if
- available, how to start the display manager.
-
-
- Several settings are tweaked so that the installer has a better
- chance of succeeding under low-memory environments.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/minimal.section.xml b/nixos/doc/manual/from_md/configuration/profiles/minimal.section.xml
deleted file mode 100644
index a3fe30357dff..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/minimal.section.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-
- Minimal
-
- This profile defines a small NixOS configuration. It does not
- contain any graphical stuff. It’s a very short file that enables
- noXlibs, sets
- to only support the
- user-selected locale,
- disables packages’
- documentation, and disables
- sound.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/profiles/qemu-guest.section.xml b/nixos/doc/manual/from_md/configuration/profiles/qemu-guest.section.xml
deleted file mode 100644
index f33464f9db4d..000000000000
--- a/nixos/doc/manual/from_md/configuration/profiles/qemu-guest.section.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
- QEMU Guest
-
- This profile contains common configuration for virtual machines
- running under QEMU (using virtio).
-
-
- It makes virtio modules available on the initrd and sets the system
- time from the hardware clock to work around a bug in qemu-kvm.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/renaming-interfaces.section.xml b/nixos/doc/manual/from_md/configuration/renaming-interfaces.section.xml
deleted file mode 100644
index fca99edcbaea..000000000000
--- a/nixos/doc/manual/from_md/configuration/renaming-interfaces.section.xml
+++ /dev/null
@@ -1,62 +0,0 @@
-
- Renaming network interfaces
-
- NixOS uses the udev
- predictable
- naming scheme to assign names to network interfaces. This
- means that by default cards are not given the traditional names like
- eth0 or eth1, whose order can
- change unpredictably across reboots. Instead, relying on physical
- locations and firmware information, the scheme produces names like
- ens1, enp2s0, etc.
-
-
- These names are predictable but less memorable and not necessarily
- stable: for example installing new hardware or changing firmware
- settings can result in a
- name
- change. If this is undesirable, for example if you have a
- single ethernet card, you can revert to the traditional scheme by
- setting
- to
- false.
-
-
- Assigning custom names
-
- In case there are multiple interfaces of the same type, it’s
- better to assign custom names based on the device hardware
- address. For example, we assign the name wan to
- the interface with MAC address
- 52:54:00:12:01:01 using a netword link unit:
-
-
-systemd.network.links."10-wan" = {
- matchConfig.PermanentMACAddress = "52:54:00:12:01:01";
- linkConfig.Name = "wan";
-};
-
-
- Note that links are directly read by udev, not
- networkd, and will work even if networkd is disabled.
-
-
- Alternatively, we can use a plain old udev rule:
-
-
-services.udev.initrdRules = ''
- SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
- ATTR{address}=="52:54:00:12:01:01", KERNEL=="eth*", NAME="wan"
-'';
-
-
-
- The rule must be installed in the initrd using
- services.udev.initrdRules, not the usual
- services.udev.extraRules option. This is to
- avoid race conditions with other programs controlling the
- interface.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/ssh.section.xml b/nixos/doc/manual/from_md/configuration/ssh.section.xml
deleted file mode 100644
index e0d4031443ef..000000000000
--- a/nixos/doc/manual/from_md/configuration/ssh.section.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
- Secure Shell Access
-
- Secure shell (SSH) access to your machine can be enabled by setting:
-
-
-services.openssh.enable = true;
-
-
- By default, root logins using a password are disallowed. They can be
- disabled entirely by setting
- to
- "no".
-
-
- You can declaratively specify authorised RSA/DSA public keys for a
- user as follows:
-
-
-users.users.alice.openssh.authorizedKeys.keys =
- [ "ssh-dss AAAAB3NzaC1kc3MAAACBAPIkGWVEt4..." ];
-
-
diff --git a/nixos/doc/manual/from_md/configuration/sshfs-file-systems.section.xml b/nixos/doc/manual/from_md/configuration/sshfs-file-systems.section.xml
deleted file mode 100644
index 26984dd411a1..000000000000
--- a/nixos/doc/manual/from_md/configuration/sshfs-file-systems.section.xml
+++ /dev/null
@@ -1,139 +0,0 @@
-
- SSHFS File Systems
-
- SSHFS is
- a
- FUSE
- filesystem that allows easy access to directories on a remote
- machine using the SSH File Transfer Protocol (SFTP). It means that
- if you have SSH access to a machine, no additional setup is needed
- to mount a directory.
-
-
- Interactive mounting
-
- In NixOS, SSHFS is packaged as sshfs. Once
- installed, mounting a directory interactively is simple as
- running:
-
-
-$ sshfs my-user@example.com:/my-dir /mnt/my-dir
-
-
- Like any other FUSE file system, the directory is unmounted using:
-
-
-$ fusermount -u /mnt/my-dir
-
-
-
- Non-interactive mounting
-
- Mounting non-interactively requires some precautions because
- sshfs will run at boot and under a different
- user (root). For obvious reason, you can’t input a password, so
- public key authentication using an unencrypted key is needed. To
- create a new key without a passphrase you can do:
-
-
-$ ssh-keygen -t ed25519 -P '' -f example-key
-Generating public/private ed25519 key pair.
-Your identification has been saved in test-key
-Your public key has been saved in test-key.pub
-The key fingerprint is:
-SHA256:yjxl3UbTn31fLWeyLYTAKYJPRmzknjQZoyG8gSNEoIE my-user@workstation
-
-
- To keep the key safe, change the ownership to
- root:root and make sure the permissions are
- 600: OpenSSH normally refuses to use the key if
- it’s not well-protected.
-
-
- The file system can be configured in NixOS via the usual
- fileSystems option. Here’s
- a typical setup:
-
-
-{
- system.fsPackages = [ pkgs.sshfs ];
-
- fileSystems."/mnt/my-dir" = {
- device = "my-user@example.com:/my-dir/";
- fsType = "sshfs";
- options =
- [ # Filesystem options
- "allow_other" # for non-root access
- "_netdev" # this is a network fs
- "x-systemd.automount" # mount on demand
-
- # SSH options
- "reconnect" # handle connection drops
- "ServerAliveInterval=15" # keep connections alive
- "IdentityFile=/var/secrets/example-key"
- ];
- };
-}
-
-
- More options from ssh_config(5) can be given as
- well, for example you can change the default SSH port or specify a
- jump proxy:
-
-
-{
- options =
- [ "ProxyJump=bastion@example.com"
- "Port=22"
- ];
-}
-
-
- It’s also possible to change the ssh command
- used by SSHFS to connect to the server. For example:
-
-
-{
- options =
- [ (builtins.replaceStrings [" "] ["\\040"]
- "ssh_command=${pkgs.openssh}/bin/ssh -v -L 8080:localhost:80")
- ];
-
-}
-
-
-
- The escaping of spaces is needed because every option is written
- to the /etc/fstab file, which is a
- space-separated table.
-
-
-
- Troubleshooting
-
- If you’re having a hard time figuring out why mounting is
- failing, you can add the option
- "debug". This enables a verbose log
- in SSHFS that you can access via:
-
-
-$ journalctl -u $(systemd-escape -p /mnt/my-dir/).mount
-Jun 22 11:41:18 workstation mount[87790]: SSHFS version 3.7.1
-Jun 22 11:41:18 workstation mount[87793]: executing <ssh> <-x> <-a> <-oClearAllForwardings=yes> <-oServerAliveInterval=15> <-oIdentityFile=/var/secrets/wrong-key> <-2> <my-user@example.com> <-s> <sftp>
-Jun 22 11:41:19 workstation mount[87793]: my-user@example.com: Permission denied (publickey).
-Jun 22 11:41:19 workstation mount[87790]: read: Connection reset by peer
-Jun 22 11:41:19 workstation systemd[1]: mnt-my\x2ddir.mount: Mount process exited, code=exited, status=1/FAILURE
-Jun 22 11:41:19 workstation systemd[1]: mnt-my\x2ddir.mount: Failed with result 'exit-code'.
-Jun 22 11:41:19 workstation systemd[1]: Failed to mount /mnt/my-dir.
-Jun 22 11:41:19 workstation systemd[1]: mnt-my\x2ddir.mount: Consumed 54ms CPU time, received 2.3K IP traffic, sent 2.7K IP traffic.
-
-
-
- If the mount point contains special characters it needs to be
- escaped using systemd-escape. This is due
- to the way systemd converts paths into unit names.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/subversion.chapter.xml b/nixos/doc/manual/from_md/configuration/subversion.chapter.xml
deleted file mode 100644
index 4390fc54ab53..000000000000
--- a/nixos/doc/manual/from_md/configuration/subversion.chapter.xml
+++ /dev/null
@@ -1,121 +0,0 @@
-
- Subversion
-
- Subversion
- is a centralized version-control system. It can use a
- variety
- of protocols for communication between client and server.
-
-
- Subversion inside Apache HTTP
-
- This section focuses on configuring a web-based server on top of
- the Apache HTTP server, which uses
- WebDAV/DeltaV
- for communication.
-
-
- For more information on the general setup, please refer to the
- the
- appropriate section of the Subversion book.
-
-
- To configure, include in
- /etc/nixos/configuration.nix code to activate
- Apache HTTP, setting
- appropriately:
-
-
-services.httpd.enable = true;
-services.httpd.adminAddr = ...;
-networking.firewall.allowedTCPPorts = [ 80 443 ];
-
-
- For a simple Subversion server with basic authentication,
- configure the Subversion module for Apache as follows, setting
- hostName and documentRoot
- appropriately, and SVNParentPath to the parent
- directory of the repositories,
- AuthzSVNAccessFile to the location of the
- .authz file describing access permission, and
- AuthUserFile to the password file.
-
-
-services.httpd.extraModules = [
- # note that order is *super* important here
- { name = "dav_svn"; path = "${pkgs.apacheHttpdPackages.subversion}/modules/mod_dav_svn.so"; }
- { name = "authz_svn"; path = "${pkgs.apacheHttpdPackages.subversion}/modules/mod_authz_svn.so"; }
- ];
- services.httpd.virtualHosts = {
- "svn" = {
- hostName = HOSTNAME;
- documentRoot = DOCUMENTROOT;
- locations."/svn".extraConfig = ''
- DAV svn
- SVNParentPath REPO_PARENT
- AuthzSVNAccessFile ACCESS_FILE
- AuthName "SVN Repositories"
- AuthType Basic
- AuthUserFile PASSWORD_FILE
- Require valid-user
- '';
- }
-
-
- The key "svn" is just a symbolic name
- identifying the virtual host. The
- "/svn" in
- locations."/svn".extraConfig is the
- path underneath which the repositories will be served.
-
-
- This
- page explains how to set up the Subversion configuration
- itself. This boils down to the following:
-
-
- Underneath REPO_PARENT repositories can be set
- up as follows:
-
-
-$ svn create REPO_NAME
-
-
- Repository files need to be accessible by
- wwwrun:
-
-
-$ chown -R wwwrun:wwwrun REPO_PARENT
-
-
- The password file PASSWORD_FILE can be created
- as follows:
-
-
-$ htpasswd -cs PASSWORD_FILE USER_NAME
-
-
- Additional users can be set up similarly, omitting the
- c flag:
-
-
-$ htpasswd -s PASSWORD_FILE USER_NAME
-
-
- The file describing access permissions
- ACCESS_FILE will look something like the
- following:
-
-
-[/]
-* = r
-
-[REPO_NAME:/]
-USER_NAME = rw
-
-
- The Subversion repositories will be accessible as
- http://HOSTNAME/svn/REPO_NAME.
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/user-mgmt.chapter.xml b/nixos/doc/manual/from_md/configuration/user-mgmt.chapter.xml
deleted file mode 100644
index d61b248d5eef..000000000000
--- a/nixos/doc/manual/from_md/configuration/user-mgmt.chapter.xml
+++ /dev/null
@@ -1,105 +0,0 @@
-
- User Management
-
- NixOS supports both declarative and imperative styles of user
- management. In the declarative style, users are specified in
- configuration.nix. For instance, the following
- states that a user account named alice shall
- exist:
-
-
-users.users.alice = {
- isNormalUser = true;
- home = "/home/alice";
- description = "Alice Foobar";
- extraGroups = [ "wheel" "networkmanager" ];
- openssh.authorizedKeys.keys = [ "ssh-dss AAAAB3Nza... alice@foobar" ];
-};
-
-
- Note that alice is a member of the
- wheel and networkmanager
- groups, which allows her to use sudo to execute
- commands as root and to configure the network,
- respectively. Also note the SSH public key that allows remote logins
- with the corresponding private key. Users created in this way do not
- have a password by default, so they cannot log in via mechanisms
- that require a password. However, you can use the
- passwd program to set a password, which is
- retained across invocations of nixos-rebuild.
-
-
- If you set to false, then
- the contents of /etc/passwd and
- /etc/group will be congruent to your NixOS
- configuration. For instance, if you remove a user from
- and run nixos-rebuild, the user
- account will cease to exist. Also, imperative commands for managing
- users and groups, such as useradd, are no longer available.
- Passwords may still be assigned by setting the user’s
- hashedPassword
- option. A hashed password can be generated using
- mkpasswd.
-
-
- A user ID (uid) is assigned automatically. You can also specify a
- uid manually by adding
-
-
-uid = 1000;
-
-
- to the user specification.
-
-
- Groups can be specified similarly. The following states that a group
- named students shall exist:
-
-
-users.groups.students.gid = 1000;
-
-
- As with users, the group ID (gid) is optional and will be assigned
- automatically if it’s missing.
-
-
- In the imperative style, users and groups are managed by commands
- such as useradd, groupmod and
- so on. For instance, to create a user account named
- alice:
-
-
-# useradd -m alice
-
-
- To make all nix tools available to this new user use `su - USER`
- which opens a login shell (==shell that loads the profile) for given
- user. This will create the ~/.nix-defexpr symlink. So run:
-
-
-# su - alice -c "true"
-
-
- The flag -m causes the creation of a home
- directory for the new user, which is generally what you want. The
- user does not have an initial password and therefore cannot log in.
- A password can be set using the passwd utility:
-
-
-# passwd alice
-Enter new UNIX password: ***
-Retype new UNIX password: ***
-
-
- A user can be deleted using userdel:
-
-
-# userdel -r alice
-
-
- The flag -r deletes the user’s home directory.
- Accounts can be modified using usermod. Unix
- groups can be managed using groupadd,
- groupmod and groupdel.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/wayland.chapter.xml b/nixos/doc/manual/from_md/configuration/wayland.chapter.xml
deleted file mode 100644
index 07892c875bb2..000000000000
--- a/nixos/doc/manual/from_md/configuration/wayland.chapter.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
- Wayland
-
- While X11 (see ) is still the primary
- display technology on NixOS, Wayland support is steadily improving.
- Where X11 separates the X Server and the window manager, on Wayland
- those are combined: a Wayland Compositor is like an X11 window
- manager, but also embeds the Wayland Server
- functionality. This means it is sufficient to install a Wayland
- Compositor such as sway without separately enabling a Wayland
- server:
-
-
-programs.sway.enable = true;
-
-
- This installs the sway compositor along with some essential
- utilities. Now you can start sway from the TTY console.
-
-
- If you are using a wlroots-based compositor, like sway, and want to
- be able to share your screen, you might want to activate this
- option:
-
-
-xdg.portal.wlr.enable = true;
-
-
- and configure Pipewire using
- and related options.
-
-
diff --git a/nixos/doc/manual/from_md/configuration/wireless.section.xml b/nixos/doc/manual/from_md/configuration/wireless.section.xml
deleted file mode 100644
index 79feab47203a..000000000000
--- a/nixos/doc/manual/from_md/configuration/wireless.section.xml
+++ /dev/null
@@ -1,73 +0,0 @@
-
- Wireless Networks
-
- For a desktop installation using NetworkManager (e.g., GNOME), you
- just have to make sure the user is in the
- networkmanager group and you can skip the rest of
- this section on wireless networks.
-
-
- NixOS will start wpa_supplicant for you if you enable this setting:
-
-
-networking.wireless.enable = true;
-
-
- NixOS lets you specify networks for wpa_supplicant declaratively:
-
-
-networking.wireless.networks = {
- echelon = { # SSID with no spaces or special characters
- psk = "abcdefgh";
- };
- "echelon's AP" = { # SSID with spaces and/or special characters
- psk = "ijklmnop";
- };
- echelon = { # Hidden SSID
- hidden = true;
- psk = "qrstuvwx";
- };
- free.wifi = {}; # Public wireless network
-};
-
-
- Be aware that keys will be written to the nix store in plaintext!
- When no networks are set, it will default to using a configuration
- file at /etc/wpa_supplicant.conf. You should edit
- this file yourself to define wireless networks, WPA keys and so on
- (see wpa_supplicant.conf(5)).
-
-
- If you are using WPA2 you can generate pskRaw key using
- wpa_passphrase:
-
-
-$ wpa_passphrase ESSID PSK
-network={
- ssid="echelon"
- #psk="abcdefgh"
- psk=dca6d6ed41f4ab5a984c9f55f6f66d4efdc720ebf66959810f4329bb391c5435
-}
-
-
-networking.wireless.networks = {
- echelon = {
- pskRaw = "dca6d6ed41f4ab5a984c9f55f6f66d4efdc720ebf66959810f4329bb391c5435";
- };
-};
-
-
- or you can use it to directly generate the
- wpa_supplicant.conf:
-
-
-# wpa_passphrase ESSID PSK > /etc/wpa_supplicant.conf
-
-
- After you have edited the wpa_supplicant.conf,
- you need to restart the wpa_supplicant service.
-
-
-# systemctl restart wpa_supplicant.service
-
-
diff --git a/nixos/doc/manual/from_md/configuration/x-windows.chapter.xml b/nixos/doc/manual/from_md/configuration/x-windows.chapter.xml
deleted file mode 100644
index 319d3e980188..000000000000
--- a/nixos/doc/manual/from_md/configuration/x-windows.chapter.xml
+++ /dev/null
@@ -1,380 +0,0 @@
-
- X Window System
-
- The X Window System (X11) provides the basis of NixOS’ graphical
- user interface. It can be enabled as follows:
-
-
-services.xserver.enable = true;
-
-
- The X server will automatically detect and use the appropriate video
- driver from a set of X.org drivers (such as vesa
- and intel). You can also specify a driver
- manually, e.g.
-
-
-services.xserver.videoDrivers = [ "r128" ];
-
-
- to enable X.org’s xf86-video-r128 driver.
-
-
- You also need to enable at least one desktop or window manager.
- Otherwise, you can only log into a plain undecorated
- xterm window. Thus you should pick one or more of
- the following lines:
-
-
-services.xserver.desktopManager.plasma5.enable = true;
-services.xserver.desktopManager.xfce.enable = true;
-services.xserver.desktopManager.gnome.enable = true;
-services.xserver.desktopManager.mate.enable = true;
-services.xserver.windowManager.xmonad.enable = true;
-services.xserver.windowManager.twm.enable = true;
-services.xserver.windowManager.icewm.enable = true;
-services.xserver.windowManager.i3.enable = true;
-services.xserver.windowManager.herbstluftwm.enable = true;
-
-
- NixOS’s default display manager (the program
- that provides a graphical login prompt and manages the X server) is
- LightDM. You can select an alternative one by picking one of the
- following lines:
-
-
-services.xserver.displayManager.sddm.enable = true;
-services.xserver.displayManager.gdm.enable = true;
-
-
- You can set the keyboard layout (and optionally the layout variant):
-
-
-services.xserver.layout = "de";
-services.xserver.xkbVariant = "neo";
-
-
- The X server is started automatically at boot time. If you don’t
- want this to happen, you can set:
-
-
-services.xserver.autorun = false;
-
-
- The X server can then be started manually:
-
-
-# systemctl start display-manager.service
-
-
- On 64-bit systems, if you want OpenGL for 32-bit programs such as in
- Wine, you should also set the following:
-
-
-hardware.opengl.driSupport32Bit = true;
-
-
- Auto-login
-
- The x11 login screen can be skipped entirely, automatically
- logging you into your window manager and desktop environment when
- you boot your computer.
-
-
- This is especially helpful if you have disk encryption enabled.
- Since you already have to provide a password to decrypt your disk,
- entering a second password to login can be redundant.
-
-
- To enable auto-login, you need to define your default window
- manager and desktop environment. If you wanted no desktop
- environment and i3 as your your window manager, you’d define:
-
-
-services.xserver.displayManager.defaultSession = "none+i3";
-
-
- Every display manager in NixOS supports auto-login, here is an
- example using lightdm for a user alice:
-
-
-services.xserver.displayManager.lightdm.enable = true;
-services.xserver.displayManager.autoLogin.enable = true;
-services.xserver.displayManager.autoLogin.user = "alice";
-
-
-
- Intel Graphics drivers
-
- There are two choices for Intel Graphics drivers in X.org:
- modesetting (included in the xorg-server
- itself) and intel (provided by the package
- xf86-video-intel).
-
-
- The default and recommended is modesetting. It
- is a generic driver which uses the kernel
- mode
- setting (KMS) mechanism. It supports Glamor (2D graphics
- acceleration via OpenGL) and is actively maintained but may
- perform worse in some cases (like in old chipsets).
-
-
- The second driver, intel, is specific to Intel
- GPUs, but not recommended by most distributions: it lacks several
- modern features (for example, it doesn’t support Glamor) and the
- package hasn’t been officially updated since 2015.
-
-
- The results vary depending on the hardware, so you may have to try
- both drivers. Use the option
- to set one.
- The recommended configuration for modern systems is:
-
-
-services.xserver.videoDrivers = [ "modesetting" ];
-
-
- If you experience screen tearing no matter what, this
- configuration was reported to resolve the issue:
-
-
-services.xserver.videoDrivers = [ "intel" ];
-services.xserver.deviceSection = ''
- Option "DRI" "2"
- Option "TearFree" "true"
-'';
-
-
- Note that this will likely downgrade the performance compared to
- modesetting or intel with
- DRI 3 (default).
-
-
-
- Proprietary NVIDIA drivers
-
- NVIDIA provides a proprietary driver for its graphics cards that
- has better 3D performance than the X.org drivers. It is not
- enabled by default because it’s not free software. You can enable
- it as follows:
-
-
-services.xserver.videoDrivers = [ "nvidia" ];
-
-
- Or if you have an older card, you may have to use one of the
- legacy drivers:
-
-
-services.xserver.videoDrivers = [ "nvidiaLegacy390" ];
-services.xserver.videoDrivers = [ "nvidiaLegacy340" ];
-services.xserver.videoDrivers = [ "nvidiaLegacy304" ];
-
-
- You may need to reboot after enabling this driver to prevent a
- clash with other kernel modules.
-
-
-
- Proprietary AMD drivers
-
- AMD provides a proprietary driver for its graphics cards that is
- not enabled by default because it’s not Free Software, is often
- broken in nixpkgs and as of this writing doesn’t offer more
- features or performance. If you still want to use it anyway, you
- need to explicitly set:
-
-
-services.xserver.videoDrivers = [ "amdgpu-pro" ];
-
-
- You will need to reboot after enabling this driver to prevent a
- clash with other kernel modules.
-
-
-
- Touchpads
-
- Support for Synaptics touchpads (found in many laptops such as the
- Dell Latitude series) can be enabled as follows:
-
-
-services.xserver.libinput.enable = true;
-
-
- The driver has many options (see ).
- For instance, the following disables tap-to-click behavior:
-
-
-services.xserver.libinput.touchpad.tapping = false;
-
-
- Note: the use of services.xserver.synaptics is
- deprecated since NixOS 17.09.
-
-
-
- GTK/Qt themes
-
- GTK themes can be installed either to user profile or system-wide
- (via environment.systemPackages). To make Qt 5
- applications look similar to GTK ones, you can use the following
- configuration:
-
-
-qt.enable = true;
-qt.platformTheme = "gtk2";
-qt.style = "gtk2";
-
-
-
- Custom XKB layouts
-
- It is possible to install custom
-
- XKB keyboard layouts using the option
- services.xserver.extraLayouts.
-
-
- As a first example, we are going to create a layout based on the
- basic US layout, with an additional layer to type some greek
- symbols by pressing the right-alt key.
-
-
- Create a file called us-greek with the
- following content (under a directory called
- symbols; it’s an XKB peculiarity that will help
- with testing):
-
-
-xkb_symbols "us-greek"
-{
- include "us(basic)" // includes the base US keys
- include "level3(ralt_switch)" // configures right alt as a third level switch
-
- key <LatA> { [ a, A, Greek_alpha ] };
- key <LatB> { [ b, B, Greek_beta ] };
- key <LatG> { [ g, G, Greek_gamma ] };
- key <LatD> { [ d, D, Greek_delta ] };
- key <LatZ> { [ z, Z, Greek_zeta ] };
-};
-
-
- A minimal layout specification must include the following:
-
-
-services.xserver.extraLayouts.us-greek = {
- description = "US layout with alt-gr greek";
- languages = [ "eng" ];
- symbolsFile = /yourpath/symbols/us-greek;
-};
-
-
-
- The name (after extraLayouts.) should match
- the one given to the xkb_symbols block.
-
-
-
- Applying this customization requires rebuilding several packages,
- and a broken XKB file can lead to the X session crashing at login.
- Therefore, you’re strongly advised to test
- your layout before applying it:
-
-
-$ nix-shell -p xorg.xkbcomp
-$ setxkbmap -I/yourpath us-greek -print | xkbcomp -I/yourpath - $DISPLAY
-
-
- You can inspect the predefined XKB files for examples:
-
-
-$ echo "$(nix-build --no-out-link '<nixpkgs>' -A xorg.xkeyboardconfig)/etc/X11/xkb/"
-
-
- Once the configuration is applied, and you did a logout/login
- cycle, the layout should be ready to use. You can try it by e.g.
- running setxkbmap us-greek and then type
- <alt>+a (it may not get applied in your
- terminal straight away). To change the default, the usual
- services.xserver.layout option can still be
- used.
-
-
- A layout can have several other components besides
- xkb_symbols, for example we will define new
- keycodes for some multimedia key and bind these to some symbol.
-
-
- Use the xev utility from
- pkgs.xorg.xev to find the codes of the keys of
- interest, then create a media-key file to hold
- the keycodes definitions
-
-
-xkb_keycodes "media"
-{
- <volUp> = 123;
- <volDown> = 456;
-}
-
-
- Now use the newly define keycodes in media-sym:
-
-
-xkb_symbols "media"
-{
- key.type = "ONE_LEVEL";
- key <volUp> { [ XF86AudioLowerVolume ] };
- key <volDown> { [ XF86AudioRaiseVolume ] };
-}
-
-
- As before, to install the layout do
-
-
-services.xserver.extraLayouts.media = {
- description = "Multimedia keys remapping";
- languages = [ "eng" ];
- symbolsFile = /path/to/media-key;
- keycodesFile = /path/to/media-sym;
-};
-
-
-
- The function
- pkgs.writeText <filename> <content>
- can be useful if you prefer to keep the layout definitions
- inside the NixOS configuration.
-
-
-
- Unfortunately, the Xorg server does not (currently) support
- setting a keymap directly but relies instead on XKB rules to
- select the matching components (keycodes, types, …) of a layout.
- This means that components other than symbols won’t be loaded by
- default. As a workaround, you can set the keymap using
- setxkbmap at the start of the session with:
-
-
-services.xserver.displayManager.sessionCommands = "setxkbmap -keycodes media";
-
-
- If you are manually starting the X server, you should set the
- argument -xkbdir /etc/X11/xkb, otherwise X
- won’t find your layout files. For example with
- xinit run
-
-
-$ xinit -- -xkbdir /etc/X11/xkb
-
-
- To learn how to write layouts take a look at the XKB
- documentation
- . More example layouts can also be found
- here
- .
-
-
-
diff --git a/nixos/doc/manual/from_md/configuration/xfce.chapter.xml b/nixos/doc/manual/from_md/configuration/xfce.chapter.xml
deleted file mode 100644
index 22a5d9875ffe..000000000000
--- a/nixos/doc/manual/from_md/configuration/xfce.chapter.xml
+++ /dev/null
@@ -1,70 +0,0 @@
-
- Xfce Desktop Environment
-
- To enable the Xfce Desktop Environment, set
-
-
-services.xserver.desktopManager.xfce.enable = true;
-services.xserver.displayManager.defaultSession = "xfce";
-
-
- Optionally, picom can be enabled for nice
- graphical effects, some example settings:
-
-
-services.picom = {
- enable = true;
- fade = true;
- inactiveOpacity = 0.9;
- shadow = true;
- fadeDelta = 4;
-};
-
-
- Some Xfce programs are not installed automatically. To install them
- manually (system wide), put them into your
- from
- pkgs.xfce.
-
-
- Thunar
-
- Thunar (the Xfce file manager) is automatically enabled when Xfce
- is enabled. To enable Thunar without enabling Xfce, use the
- configuration option
- instead of simply adding pkgs.xfce.thunar to
- .
-
-
- If you’d like to add extra plugins to Thunar, add them to
- . You shouldn’t just
- add them to .
-
-
-
- Troubleshooting
-
- Even after enabling udisks2, volume management might not work.
- Thunar and/or the desktop takes time to show up. Thunar will spit
- out this kind of message on start (look at
- journalctl --user -b).
-
-
-Thunar:2410): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
-
-
- This is caused by some needed GNOME services not running. This is
- all fixed by enabling Launch GNOME services on
- startup in the Advanced tab of the Session and Startup
- settings panel. Alternatively, you can run this command to do the
- same thing.
-
-
-$ xfconf-query -c xfce4-session -p /compat/LaunchGNOME -s true
-
-
- It is necessary to log out and log in again for this to take
- effect.
-
-
-
diff --git a/nixos/doc/manual/from_md/contributing-to-this-manual.chapter.xml b/nixos/doc/manual/from_md/contributing-to-this-manual.chapter.xml
deleted file mode 100644
index 99dc5ce30b4b..000000000000
--- a/nixos/doc/manual/from_md/contributing-to-this-manual.chapter.xml
+++ /dev/null
@@ -1,52 +0,0 @@
-
- Contributing to this manual
-
- The
- DocBook
- and CommonMark sources of the NixOS manual are in the
- nixos/doc/manual
- subdirectory of the
- Nixpkgs
- repository.
-
-
- You can quickly check your edits with the following:
-
-
-$ cd /path/to/nixpkgs
-$ ./nixos/doc/manual/md-to-db.sh
-$ nix-build nixos/release.nix -A manual.x86_64-linux
-
-
- If the build succeeds, the manual will be in
- ./result/share/doc/nixos/index.html.
-
-
- Contributing to the man pages
-
-
- The man pages are written in
- DocBook
- which is XML.
-
-
- To see what your edits look like:
-
-
-$ cd /path/to/nixpkgs
-$ nix-build nixos/release.nix -A manpages.x86_64-linux
-
-
- You can then read the man page you edited by running
-
-
-$ man --manpath=result/share/man nixos-rebuild # Replace nixos-rebuild with the command whose manual you edited
-
-
- If you’re on a different architecture that’s supported by NixOS
- (check nixos/release.nix) then replace
- x86_64-linux with the architecture.
- nix-build will complain otherwise, but should
- also tell you which architecture you have + the supported ones.
-
-
diff --git a/nixos/doc/manual/from_md/development/activation-script.section.xml b/nixos/doc/manual/from_md/development/activation-script.section.xml
deleted file mode 100644
index 429b45c93def..000000000000
--- a/nixos/doc/manual/from_md/development/activation-script.section.xml
+++ /dev/null
@@ -1,150 +0,0 @@
-
- Activation script
-
- The activation script is a bash script called to activate the new
- configuration which resides in a NixOS system in
- $out/activate. Since its contents depend on your
- system configuration, the contents may differ. This chapter explains
- how the script works in general and some common NixOS snippets.
- Please be aware that the script is executed on every boot and system
- switch, so tasks that can be performed in other places should be
- performed there (for example letting a directory of a service be
- created by systemd using mechanisms like
- StateDirectory,
- CacheDirectory, … or if that’s not possible using
- preStart of the service).
-
-
- Activation scripts are defined as snippets using
- . They can either be
- a simple multiline string or an attribute set that can depend on
- other snippets. The builder for the activation script will take
- these dependencies into account and order the snippets accordingly.
- As a simple example:
-
-
-system.activationScripts.my-activation-script = {
- deps = [ "etc" ];
- # supportsDryActivation = true;
- text = ''
- echo "Hallo i bims"
- '';
-};
-
-
- This example creates an activation script snippet that is run after
- the etc snippet. The special variable
- supportsDryActivation can be set so the snippet
- is also run when nixos-rebuild dry-activate is
- run. To differentiate between real and dry activation, the
- $NIXOS_ACTION environment variable can be read
- which is set to dry-activate when a dry
- activation is done.
-
-
- An activation script can write to special files instructing
- switch-to-configuration to restart/reload units.
- The script will take these requests into account and will
- incorporate the unit configuration as described above. This means
- that the activation script will fake a modified unit
- file and switch-to-configuration will act
- accordingly. By doing so, configuration like
- systemd.services.<name>.restartIfChanged
- is respected. Since the activation script is run
- after services are already
- stopped,
- systemd.services.<name>.stopIfChanged
- cannot be taken into account anymore and the unit is always
- restarted instead of being stopped and started afterwards.
-
-
- The files that can be written to are
- /run/nixos/activation-restart-list and
- /run/nixos/activation-reload-list with their
- respective counterparts for dry activation being
- /run/nixos/dry-activation-restart-list and
- /run/nixos/dry-activation-reload-list. Those
- files can contain newline-separated lists of unit names where
- duplicates are being ignored. These files are not create
- automatically and activation scripts must take the possibility into
- account that they have to create them first.
-
-
- NixOS snippets
-
- There are some snippets NixOS enables by default because disabling
- them would most likely break your system. This section lists a few
- of them and what they do:
-
-
-
-
- binsh creates /bin/sh
- which points to the runtime shell
-
-
-
-
- etc sets up the contents of
- /etc, this includes systemd units and
- excludes /etc/passwd,
- /etc/group, and
- /etc/shadow (which are managed by the
- users snippet)
-
-
-
-
- hostname sets the system’s hostname in the
- kernel (not in /etc)
-
-
-
-
- modprobe sets the path to the
- modprobe binary for module auto-loading
-
-
-
-
- nix prepares the nix store and adds a
- default initial channel
-
-
-
-
- specialfs is responsible for mounting
- filesystems like /proc and
- sys
-
-
-
-
- users creates and removes users and groups
- by managing /etc/passwd,
- /etc/group and
- /etc/shadow. This also creates home
- directories
-
-
-
-
- usrbinenv creates
- /usr/bin/env
-
-
-
-
- var creates some directories in
- /var that are not service-specific
-
-
-
-
- wrappers creates setuid wrappers like
- ping and sudo
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/assertions.section.xml b/nixos/doc/manual/from_md/development/assertions.section.xml
deleted file mode 100644
index 13f04d5d1883..000000000000
--- a/nixos/doc/manual/from_md/development/assertions.section.xml
+++ /dev/null
@@ -1,58 +0,0 @@
-
- Warnings and Assertions
-
- When configuration problems are detectable in a module, it is a good
- idea to write an assertion or warning. Doing so provides clear
- feedback to the user and prevents errors after the build.
-
-
- Although Nix has the abort and
- builtins.trace
- functions
- to perform such tasks, they are not ideally suited for NixOS
- modules. Instead of these functions, you can declare your warnings
- and assertions using the NixOS module system.
-
-
- Warnings
-
- This is an example of using warnings.
-
-
-{ config, lib, ... }:
-{
- config = lib.mkIf config.services.foo.enable {
- warnings =
- if config.services.foo.bar
- then [ ''You have enabled the bar feature of the foo service.
- This is known to cause some specific problems in certain situations.
- '' ]
- else [];
- }
-}
-
-
-
- Assertions
-
- This example, extracted from the
- syslogd
- module shows how to use assertions.
- Since there can only be one active syslog daemon at a time, an
- assertion is useful to prevent such a broken system from being
- built.
-
-
-{ config, lib, ... }:
-{
- config = lib.mkIf config.services.syslogd.enable {
- assertions =
- [ { assertion = !config.services.rsyslogd.enable;
- message = "rsyslogd conflicts with syslogd";
- }
- ];
- }
-}
-
-
-
diff --git a/nixos/doc/manual/from_md/development/bootspec.chapter.xml b/nixos/doc/manual/from_md/development/bootspec.chapter.xml
deleted file mode 100644
index 9ecbe1d1beed..000000000000
--- a/nixos/doc/manual/from_md/development/bootspec.chapter.xml
+++ /dev/null
@@ -1,73 +0,0 @@
-
- Experimental feature: Bootspec
-
- Bootspec is a experimental feature, introduced in the
- RFC-0125
- proposal, the reference implementation can be found
- there
- in order to standardize bootloader support and advanced boot
- workflows such as SecureBoot and potentially more.
-
-
- You can enable the creation of bootspec documents through
- boot.bootspec.enable = true,
- which will prompt a warning until
- RFC-0125
- is officially merged.
-
-
- Schema
-
- The bootspec schema is versioned and validated against
- a CUE schema file
- which should considered as the source of truth for your
- applications.
-
-
- You will find the current version
- here.
-
-
-
- Extensions mechanism
-
- Bootspec cannot account for all usecases.
-
-
- For this purpose, Bootspec offers a generic extension facility
- boot.bootspec.extensions
- which can be used to inject any data needed for your usecases.
-
-
- An example for SecureBoot is to get the Nix store path to
- /etc/os-release in order to bake it into a
- unified kernel image:
-
-
-{ config, lib, ... }: {
- boot.bootspec.extensions = {
- "org.secureboot.osRelease" = config.environment.etc."os-release".source;
- };
-}
-
-
- To reduce incompatibility and prevent names from clashing between
- applications, it is highly
- recommended to use a unique namespace for your
- extensions.
-
-
-
- External bootloaders
-
- It is possible to enable your own bootloader through
- boot.loader.external.installHook
- which can wrap an existing bootloader.
-
-
- Currently, there is no good story to compose existing bootloaders
- to enrich their features, e.g. SecureBoot, etc. It will be
- necessary to reimplement or reuse existing parts.
-
-
-
diff --git a/nixos/doc/manual/from_md/development/building-parts.chapter.xml b/nixos/doc/manual/from_md/development/building-parts.chapter.xml
deleted file mode 100644
index 4df24cc95652..000000000000
--- a/nixos/doc/manual/from_md/development/building-parts.chapter.xml
+++ /dev/null
@@ -1,124 +0,0 @@
-
- Building Specific Parts of NixOS
-
- With the command nix-build, you can build
- specific parts of your NixOS configuration. This is done as follows:
-
-
-$ cd /path/to/nixpkgs/nixos
-$ nix-build -A config.option
-
-
- where option is a NixOS option with type
- derivation (i.e. something that can be built).
- Attributes of interest include:
-
-
-
-
- system.build.toplevel
-
-
-
- The top-level option that builds the entire NixOS system.
- Everything else in your configuration is indirectly pulled in
- by this option. This is what nixos-rebuild
- builds and what /run/current-system points
- to afterwards.
-
-
- A shortcut to build this is:
-
-
-$ nix-build -A system
-
-
-
-
-
- system.build.manual.manualHTML
-
-
-
- The NixOS manual.
-
-
-
-
-
- system.build.etc
-
-
-
- A tree of symlinks that form the static parts of
- /etc.
-
-
-
-
-
- system.build.initialRamdisk ,
- system.build.kernel
-
-
-
- The initial ramdisk and kernel of the system. This allows a
- quick way to test whether the kernel and the initial ramdisk
- boot correctly, by using QEMU’s -kernel and
- -initrd options:
-
-
-$ nix-build -A config.system.build.initialRamdisk -o initrd
-$ nix-build -A config.system.build.kernel -o kernel
-$ qemu-system-x86_64 -kernel ./kernel/bzImage -initrd ./initrd/initrd -hda /dev/null
-
-
-
-
-
- system.build.nixos-rebuild ,
- system.build.nixos-install ,
- system.build.nixos-generate-config
-
-
-
- These build the corresponding NixOS commands.
-
-
-
-
-
- systemd.units.unit-name.unit
-
-
-
- This builds the unit with the specified name. Note that since
- unit names contain dots (e.g.
- httpd.service), you need to put them
- between quotes, like this:
-
-
-$ nix-build -A 'config.systemd.units."httpd.service".unit'
-
-
- You can also test individual units, without rebuilding the
- whole system, by putting them in
- /run/systemd/system:
-
-
-$ cp $(nix-build -A 'config.systemd.units."httpd.service".unit')/httpd.service \
- /run/systemd/system/tmp-httpd.service
-# systemctl daemon-reload
-# systemctl start tmp-httpd.service
-
-
- Note that the unit must not have the same name as any unit in
- /etc/systemd/system since those take
- precedence over /run/systemd/system. That’s
- why the unit is installed as
- tmp-httpd.service here.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/freeform-modules.section.xml b/nixos/doc/manual/from_md/development/freeform-modules.section.xml
deleted file mode 100644
index c51bc76ff966..000000000000
--- a/nixos/doc/manual/from_md/development/freeform-modules.section.xml
+++ /dev/null
@@ -1,87 +0,0 @@
-
- Freeform modules
-
- Freeform modules allow you to define values for option paths that
- have not been declared explicitly. This can be used to add
- attribute-specific types to what would otherwise have to be
- attrsOf options in order to accept all attribute
- names.
-
-
- This feature can be enabled by using the attribute
- freeformType to define a freeform type. By doing
- this, all assignments without an associated option will be merged
- using the freeform type and combined into the resulting
- config set. Since this feature nullifies name
- checking for entire option trees, it is only recommended for use in
- submodules.
-
-
-
- Example: Freeform submodule
-
-
- The following shows a submodule assigning a freeform type that
- allows arbitrary attributes with str values below
- settings, but also declares an option for the
- settings.port attribute to have it type-checked
- and assign a default value. See
- Example: Declaring a
- type-checked settings attribute for a more
- complete example.
-
-
-{ lib, config, ... }: {
-
- options.settings = lib.mkOption {
- type = lib.types.submodule {
-
- freeformType = with lib.types; attrsOf str;
-
- # We want this attribute to be checked for the correct type
- options.port = lib.mkOption {
- type = lib.types.port;
- # Declaring the option also allows defining a default value
- default = 8080;
- };
-
- };
- };
-}
-
-
- And the following shows what such a module then allows
-
-
-{
- # Not a declared option, but the freeform type allows this
- settings.logLevel = "debug";
-
- # Not allowed because the the freeform type only allows strings
- # settings.enable = true;
-
- # Allowed because there is a port option declared
- settings.port = 80;
-
- # Not allowed because the port option doesn't allow strings
- # settings.port = "443";
-}
-
-
-
- Freeform attributes cannot depend on other attributes of the same
- set without infinite recursion:
-
-
-{
- # This throws infinite recursion encountered
- settings.logLevel = lib.mkIf (config.settings.port == 80) "debug";
-}
-
-
- To prevent this, declare options for all attributes that need to
- depend on others. For above example this means to declare
- logLevel to be an option.
-
-
-
diff --git a/nixos/doc/manual/from_md/development/importing-modules.section.xml b/nixos/doc/manual/from_md/development/importing-modules.section.xml
deleted file mode 100644
index 96e5e1bb16b8..000000000000
--- a/nixos/doc/manual/from_md/development/importing-modules.section.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
- Importing Modules
-
- Sometimes NixOS modules need to be used in configuration but exist
- outside of Nixpkgs. These modules can be imported:
-
-
-{ config, lib, pkgs, ... }:
-
-{
- imports =
- [ # Use a locally-available module definition in
- # ./example-module/default.nix
- ./example-module
- ];
-
- services.exampleModule.enable = true;
-}
-
-
- The environment variable NIXOS_EXTRA_MODULE_PATH
- is an absolute path to a NixOS module that is included alongside the
- Nixpkgs NixOS modules. Like any NixOS module, this module can import
- additional modules:
-
-
-# ./module-list/default.nix
-[
- ./example-module1
- ./example-module2
-]
-
-
-# ./extra-module/default.nix
-{ imports = import ./module-list.nix; }
-
-
-# NIXOS_EXTRA_MODULE_PATH=/absolute/path/to/extra-module
-{ config, lib, pkgs, ... }:
-
-{
- # No `imports` needed
-
- services.exampleModule1.enable = true;
-}
-
-
diff --git a/nixos/doc/manual/from_md/development/linking-nixos-tests-to-packages.section.xml b/nixos/doc/manual/from_md/development/linking-nixos-tests-to-packages.section.xml
deleted file mode 100644
index 666bbec6162b..000000000000
--- a/nixos/doc/manual/from_md/development/linking-nixos-tests-to-packages.section.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-
- Linking NixOS tests to packages
-
- You can link NixOS module tests to the packages that they exercised,
- so that the tests can be run automatically during code review when
- the package gets changed. This is
- described
- in the nixpkgs manual.
-
-
diff --git a/nixos/doc/manual/from_md/development/meta-attributes.section.xml b/nixos/doc/manual/from_md/development/meta-attributes.section.xml
deleted file mode 100644
index 64234f1cc0d7..000000000000
--- a/nixos/doc/manual/from_md/development/meta-attributes.section.xml
+++ /dev/null
@@ -1,97 +0,0 @@
-
- Meta Attributes
-
- Like Nix packages, NixOS modules can declare meta-attributes to
- provide extra information. Module meta attributes are defined in the
- meta.nix special module.
-
-
- meta is a top level attribute like
- options and config. Available
- meta-attributes are maintainers,
- doc, and buildDocsInSandbox.
-
-
- Each of the meta-attributes must be defined at most once per module
- file.
-
-
-{ config, lib, pkgs, ... }:
-{
- options = {
- ...
- };
-
- config = {
- ...
- };
-
- meta = {
- maintainers = with lib.maintainers; [ ericsagnes ];
- doc = ./default.md;
- buildDocsInSandbox = true;
- };
-}
-
-
-
-
- maintainers contains a list of the module
- maintainers.
-
-
-
-
- doc points to a valid
- Nixpkgs-flavored
- CommonMark file containing the module documentation. Its
- contents is automatically added to
- . Changes to a module
- documentation have to be checked to not break building the NixOS
- manual:
-
-
-$ nix-build nixos/release.nix -A manual.x86_64-linux
-
-
-
-
- buildDocsInSandbox indicates whether the
- option documentation for the module can be built in a derivation
- sandbox. This option is currently only honored for modules
- shipped by nixpkgs. User modules and modules taken from
- NIXOS_EXTRA_MODULE_PATH are always built
- outside of the sandbox, as has been the case in previous
- releases.
-
-
- Building NixOS option documentation in a sandbox allows caching
- of the built documentation, which greatly decreases the amount
- of time needed to evaluate a system configuration that has NixOS
- documentation enabled. The sandbox also restricts which
- attributes may be referenced by documentation attributes (such
- as option descriptions) to the options and
- lib module arguments and the
- pkgs.formats attribute of the
- pkgs argument, config and
- the rest of pkgs are disallowed and will
- cause doc build failures when used. This restriction is
- necessary because we cannot reproduce the full nixpkgs
- instantiation with configuration and overlays from a system
- configuration inside the sandbox. The options
- argument only includes options of modules that are also built
- inside the sandbox, referencing an option of a module that isn’t
- built in the sandbox is also forbidden.
-
-
- The default is true and should usually not be
- changed; set it to false only if the module
- requires access to pkgs in its documentation
- (e.g. because it loads information from a linked package to
- build an option type) or if its documentation depends on other
- modules that also aren’t sandboxed (e.g. by using types defined
- in the other module).
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/nixos-tests.chapter.xml b/nixos/doc/manual/from_md/development/nixos-tests.chapter.xml
deleted file mode 100644
index b9ff2269676c..000000000000
--- a/nixos/doc/manual/from_md/development/nixos-tests.chapter.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
- NixOS Tests
-
- When you add some feature to NixOS, you should write a test for it.
- NixOS tests are kept in the directory
- nixos/tests, and are executed (using Nix) by a
- testing framework that automatically starts one or more virtual
- machines containing the NixOS system(s) required for the test.
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/option-declarations.section.xml b/nixos/doc/manual/from_md/development/option-declarations.section.xml
deleted file mode 100644
index af05e61363e4..000000000000
--- a/nixos/doc/manual/from_md/development/option-declarations.section.xml
+++ /dev/null
@@ -1,345 +0,0 @@
-
- Option Declarations
-
- An option declaration specifies the name, type and description of a
- NixOS configuration option. It is invalid to define an option that
- hasn’t been declared in any module. An option declaration generally
- looks like this:
-
-
-options = {
- name = mkOption {
- type = type specification;
- default = default value;
- example = example value;
- description = lib.mdDoc "Description for use in the NixOS manual.";
- };
-};
-
-
- The attribute names within the name attribute
- path must be camel cased in general but should, as an exception,
- match the
-
- package attribute name when referencing a Nixpkgs package.
- For example, the option
- services.nix-serve.bindAddress references the
- nix-serve Nixpkgs package.
-
-
- The function mkOption accepts the following
- arguments.
-
-
-
-
- type
-
-
-
- The type of the option (see
- ). This argument is
- mandatory for nixpkgs modules. Setting this is highly
- recommended for the sake of documentation and type checking.
- In case it is not set, a fallback type with unspecified
- behavior is used.
-
-
-
-
-
- default
-
-
-
- The default value used if no value is defined by any module. A
- default is not required; but if a default is not given, then
- users of the module will have to define the value of the
- option, otherwise an error will be thrown.
-
-
-
-
-
- defaultText
-
-
-
- A textual representation of the default value to be rendered
- verbatim in the manual. Useful if the default value is a
- complex expression or depends on other values or packages. Use
- lib.literalExpression for a Nix expression,
- lib.literalMD for a plain English
- description in
- Nixpkgs-flavored
- Markdown format.
-
-
-
-
-
- example
-
-
-
- An example value that will be shown in the NixOS manual. You
- can use lib.literalExpression and
- lib.literalMD in the same way as in
- defaultText.
-
-
-
-
-
- description
-
-
-
- A textual description of the option, in
- Nixpkgs-flavored
- Markdown format, that will be included in the NixOS
- manual. During the migration process from DocBook it is
- necessary to mark descriptions written in CommonMark with
- lib.mdDoc. The description may still be
- written in DocBook (without any marker), but this is
- discouraged and will be deprecated in the future.
-
-
-
-
-
- Utility functions for common option patterns
-
- <literal>mkEnableOption</literal>
-
- Creates an Option attribute set for a boolean value option i.e
- an option to be toggled on or off.
-
-
- This function takes a single string argument, the name of the
- thing to be toggled.
-
-
- The option’s description is Whether to enable
- <name>..
-
-
- For example:
-
-
-
-lib.mkEnableOption (lib.mdDoc "magic")
-# is like
-lib.mkOption {
- type = lib.types.bool;
- default = false;
- example = true;
- description = lib.mdDoc "Whether to enable magic.";
-}
-
-
- <literal>mkPackageOption</literal>,
- <literal>mkPackageOptionMD</literal>
-
- Usage:
-
-
-mkPackageOption pkgs "name" { default = [ "path" "in" "pkgs" ]; example = "literal example"; }
-
-
- Creates an Option attribute set for an option that specifies
- the package a module should use for some purpose.
-
-
- Note: You shouldn’t
- necessarily make package options for all of your modules. You
- can always overwrite a specific package throughout nixpkgs by
- using
- nixpkgs
- overlays.
-
-
- The default package is specified as a list of strings
- representing its attribute path in nixpkgs. Because of this,
- you need to pass nixpkgs itself as the first argument.
-
-
- The second argument is the name of the option, used in the
- description The <name> package to use..
- You can also pass an example value, either a literal string or
- a package’s attribute path.
-
-
- You can omit the default path if the name of the option is
- also attribute path in nixpkgs.
-
-
- During the transition to CommonMark documentation
- mkPackageOption creates an option with a
- DocBook description attribute, once the transition is
- completed it will create a CommonMark description instead.
- mkPackageOptionMD always creates an option
- with a CommonMark description attribute and will be removed
- some time after the transition is completed.
-
-
-
- Examples:
-
-
-
-lib.mkPackageOptionMD pkgs "hello" { }
-# is like
-lib.mkOption {
- type = lib.types.package;
- default = pkgs.hello;
- defaultText = lib.literalExpression "pkgs.hello";
- description = lib.mdDoc "The hello package to use.";
-}
-
-
-
-lib.mkPackageOptionMD pkgs "GHC" {
- default = [ "ghc" ];
- example = "pkgs.haskell.packages.ghc92.ghc.withPackages (hkgs: [ hkgs.primes ])";
-}
-# is like
-lib.mkOption {
- type = lib.types.package;
- default = pkgs.ghc;
- defaultText = lib.literalExpression "pkgs.ghc";
- example = lib.literalExpression "pkgs.haskell.packages.ghc92.ghc.withPackages (hkgs: [ hkgs.primes ])";
- description = lib.mdDoc "The GHC package to use.";
-}
-
-
- Extensible Option Types
-
- Extensible option types is a feature that allow to extend
- certain types declaration through multiple module files.
- This feature only work with a restricted set of types,
- namely enum and
- submodules and any composed forms of
- them.
-
-
- Extensible option types can be used for
- enum options that affects multiple
- modules, or as an alternative to related
- enable options.
-
-
- As an example, we will take the case of display managers.
- There is a central display manager module for generic
- display manager options and a module file per display
- manager backend (sddm, gdm …).
-
-
- There are two approaches we could take with this module
- structure:
-
-
-
-
- Configuring the display managers independently by adding
- an enable option to every display manager module
- backend. (NixOS)
-
-
-
-
- Configuring the display managers in the central module
- by adding an option to select which display manager
- backend to use.
-
-
-
-
- Both approaches have problems.
-
-
- Making backends independent can quickly become hard to
- manage. For display managers, there can only be one enabled
- at a time, but the type system cannot enforce this
- restriction as there is no relation between each backend’s
- enable option. As a result, this
- restriction has to be done explicitly by adding assertions
- in each display manager backend module.
-
-
- On the other hand, managing the display manager backends in
- the central module will require changing the central module
- option every time a new backend is added or removed.
-
-
- By using extensible option types, it is possible to create a
- placeholder option in the central module
- (Example:
- Extensible type placeholder in the service module),
- and to extend it in each backend module
- (Example:
- Extending
- services.xserver.displayManager.enable in
- the gdm module,
- Example:
- Extending
- services.xserver.displayManager.enable in
- the sddm module).
-
-
- As a result, displayManager.enable option
- values can be added without changing the main service module
- file and the type system automatically enforces that there
- can only be a single display manager enabled.
-
-
-
- Example: Extensible type placeholder
- in the service module
-
-
-services.xserver.displayManager.enable = mkOption {
- description = "Display manager to use";
- type = with types; nullOr (enum [ ]);
-};
-
-
-
- Example: Extending
- services.xserver.displayManager.enable in
- the gdm module
-
-
-services.xserver.displayManager.enable = mkOption {
- type = with types; nullOr (enum [ "gdm" ]);
-};
-
-
-
- Example: Extending
- services.xserver.displayManager.enable in
- the sddm module
-
-
-services.xserver.displayManager.enable = mkOption {
- type = with types; nullOr (enum [ "sddm" ]);
-};
-
-
- The placeholder declaration is a standard
- mkOption declaration, but it is important
- that extensible option declarations only use the
- type argument.
-
-
- Extensible option types work with any of the composed
- variants of enum such as
- with types; nullOr (enum [ "foo" "bar" ])
- or
- with types; listOf (enum [ "foo" "bar" ]).
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/option-def.section.xml b/nixos/doc/manual/from_md/development/option-def.section.xml
deleted file mode 100644
index 87b290ec39c6..000000000000
--- a/nixos/doc/manual/from_md/development/option-def.section.xml
+++ /dev/null
@@ -1,132 +0,0 @@
-
- Option Definitions
-
- Option definitions are generally straight-forward bindings of values
- to option names, like
-
-
-config = {
- services.httpd.enable = true;
-};
-
-
- However, sometimes you need to wrap an option definition or set of
- option definitions in a property to achieve
- certain effects:
-
-
- Delaying Conditionals
-
- If a set of option definitions is conditional on the value of
- another option, you may need to use mkIf.
- Consider, for instance:
-
-
-config = if config.services.httpd.enable then {
- environment.systemPackages = [ ... ];
- ...
-} else {};
-
-
- This definition will cause Nix to fail with an infinite
- recursion error. Why? Because the value of
- config.services.httpd.enable depends on the
- value being constructed here. After all, you could also write the
- clearly circular and contradictory:
-
-
-config = if config.services.httpd.enable then {
- services.httpd.enable = false;
-} else {
- services.httpd.enable = true;
-};
-
-
- The solution is to write:
-
-
-config = mkIf config.services.httpd.enable {
- environment.systemPackages = [ ... ];
- ...
-};
-
-
- The special function mkIf causes the evaluation
- of the conditional to be pushed down into the
- individual definitions, as if you had written:
-
-
-config = {
- environment.systemPackages = if config.services.httpd.enable then [ ... ] else [];
- ...
-};
-
-
-
- Setting Priorities
-
- A module can override the definitions of an option in other
- modules by setting an override priority. All
- option definitions that do not have the lowest priority value are
- discarded. By default, option definitions have priority 100 and
- option defaults have priority 1500. You can specify an explicit
- priority by using mkOverride, e.g.
-
-
-services.openssh.enable = mkOverride 10 false;
-
-
- This definition causes all other definitions with priorities above
- 10 to be discarded. The function mkForce is
- equal to mkOverride 50, and
- mkDefault is equal to
- mkOverride 1000.
-
-
-
- Ordering Definitions
-
- It is also possible to influence the order in which the
- definitions for an option are merged by setting an order
- priority with mkOrder. The default
- order priority is 1000. The functions mkBefore
- and mkAfter are equal to
- mkOrder 500 and
- mkOrder 1500, respectively. As an example,
-
-
-hardware.firmware = mkBefore [ myFirmware ];
-
-
- This definition ensures that myFirmware comes
- before other unordered definitions in the final list value of
- hardware.firmware.
-
-
- Note that this is different from
- override
- priorities: setting an order does not affect whether the
- definition is included or not.
-
-
-
- Merging Configurations
-
- In conjunction with mkIf, it is sometimes
- useful for a module to return multiple sets of option definitions,
- to be merged together as if they were declared in separate
- modules. This can be done using mkMerge:
-
-
-config = mkMerge
- [ # Unconditional stuff.
- { environment.systemPackages = [ ... ];
- }
- # Conditional stuff.
- (mkIf config.services.bla.enable {
- environment.systemPackages = [ ... ];
- })
- ];
-
-
-
diff --git a/nixos/doc/manual/from_md/development/option-types.section.xml b/nixos/doc/manual/from_md/development/option-types.section.xml
deleted file mode 100644
index 363399b08661..000000000000
--- a/nixos/doc/manual/from_md/development/option-types.section.xml
+++ /dev/null
@@ -1,1148 +0,0 @@
-
- Options Types
-
- Option types are a way to put constraints on the values a module
- option can take. Types are also responsible of how values are merged
- in case of multiple value definitions.
-
-
- Basic types
-
- Basic types are the simplest available types in the module system.
- Basic types include multiple string types that mainly differ in
- how definition merging is handled.
-
-
-
-
- types.bool
-
-
-
- A boolean, its values can be true or
- false.
-
-
-
-
-
- types.path
-
-
-
- A filesystem path is anything that starts with a slash when
- coerced to a string. Even if derivations can be considered
- as paths, the more specific types.package
- should be preferred.
-
-
-
-
-
- types.package
-
-
-
- A top-level store path. This can be an attribute set
- pointing to a store path, like a derivation or a flake
- input.
-
-
-
-
-
- types.enum
- l
-
-
-
- One element of the list
- l, e.g.
- types.enum [ "left" "right" ].
- Multiple definitions cannot be merged.
-
-
-
-
-
- types.anything
-
-
-
- A type that accepts any value and recursively merges
- attribute sets together. This type is recommended when the
- option type is unknown.
-
-
-
- Example:
- types.anything Example
-
-
- Two definitions of this type like
-
-
-{
- str = lib.mkDefault "foo";
- pkg.hello = pkgs.hello;
- fun.fun = x: x + 1;
-}
-
-
-{
- str = lib.mkIf true "bar";
- pkg.gcc = pkgs.gcc;
- fun.fun = lib.mkForce (x: x + 2);
-}
-
-
- will get merged to
-
-
-{
- str = "bar";
- pkg.gcc = pkgs.gcc;
- pkg.hello = pkgs.hello;
- fun.fun = x: x + 2;
-}
-
-
-
-
-
- types.raw
-
-
-
- A type which doesn’t do any checking, merging or nested
- evaluation. It accepts a single arbitrary value that is not
- recursed into, making it useful for values coming from
- outside the module system, such as package sets or arbitrary
- data. Options of this type are still evaluated according to
- priorities and conditionals, so mkForce,
- mkIf and co. still work on the option
- value itself, but not for any value nested within it. This
- type should only be used when checking, merging and nested
- evaluation are not desirable.
-
-
-
-
-
- types.optionType
-
-
-
- The type of an option’s type. Its merging operation ensures
- that nested options have the correct file location
- annotated, and that if possible, multiple option definitions
- are correctly merged together. The main use case is as the
- type of the _module.freeformType option.
-
-
-
-
-
- types.attrs
-
-
-
- A free-form attribute set.
-
-
-
- This type will be deprecated in the future because it
- doesn’t recurse into attribute sets, silently drops
- earlier attribute definitions, and doesn’t discharge
- lib.mkDefault,
- lib.mkIf and co. For allowing arbitrary
- attribute sets, prefer
- types.attrsOf types.anything instead
- which doesn’t have these problems.
-
-
-
-
-
-
- Numeric types
-
-
-
- types.int
-
-
-
- A signed integer.
-
-
-
-
-
- types.ints.{s8, s16, s32}
-
-
-
- Signed integers with a fixed length (8, 16 or 32 bits).
- They go from −2^n/2 to 2^n/2−1 respectively (e.g.
- −128 to 127 for 8
- bits).
-
-
-
-
-
- types.ints.unsigned
-
-
-
- An unsigned integer (that is >= 0).
-
-
-
-
-
- types.ints.{u8, u16, u32}
-
-
-
- Unsigned integers with a fixed length (8, 16 or 32 bits).
- They go from 0 to 2^n−1 respectively (e.g.
- 0 to 255 for 8
- bits).
-
-
-
-
-
- types.ints.between
- lowest highest
-
-
-
- An integer between
- lowest and
- highest (both
- inclusive).
-
-
-
-
-
- types.ints.positive
-
-
-
- A positive integer (that is > 0).
-
-
-
-
-
- types.port
-
-
-
- A port number. This type is an alias to
- types.ints.u16.
-
-
-
-
-
- types.float
-
-
-
- A floating point number.
-
-
-
- Converting a floating point number to a string with
- toString or toJSON
- may result in
- precision
- loss.
-
-
-
-
-
-
- types.number
-
-
-
- Either a signed integer or a floating point number. No
- implicit conversion is done between the two types, and
- multiple equal definitions will only be merged if they
- have the same type.
-
-
-
-
-
- types.numbers.between
- lowest highest
-
-
-
- An integer or floating point number between
- lowest and
- highest (both
- inclusive).
-
-
-
-
-
- types.numbers.nonnegative
-
-
-
- A nonnegative integer or floating point number (that is
- >= 0).
-
-
-
-
-
- types.numbers.positive
-
-
-
- A positive integer or floating point number (that is >
- 0).
-
-
-
-
-
-
- String types
-
-
-
- types.str
-
-
-
- A string. Multiple definitions cannot be merged.
-
-
-
-
-
- types.separatedString
- sep
-
-
-
- A string. Multiple definitions are concatenated with
- sep, e.g.
- types.separatedString "|".
-
-
-
-
-
- types.lines
-
-
-
- A string. Multiple definitions are concatenated with a new
- line "\n".
-
-
-
-
-
- types.commas
-
-
-
- A string. Multiple definitions are concatenated with a
- comma ",".
-
-
-
-
-
- types.envVar
-
-
-
- A string. Multiple definitions are concatenated with a
- colon ":".
-
-
-
-
-
- types.strMatching
-
-
-
- A string matching a specific regular expression. Multiple
- definitions cannot be merged. The regular expression is
- processed using builtins.match.
-
-
-
-
-
-
-
- Submodule types
-
- Submodules are detailed in
- Submodule.
-
-
-
-
- types.submodule
- o
-
-
-
- A set of sub options
- o.
- o can be an
- attribute set, a function returning an attribute set, or a
- path to a file containing such a value. Submodules are used
- in composed types to create modular options. This is
- equivalent to
- types.submoduleWith { modules = toList o; shorthandOnlyDefinesConfig = true; }.
-
-
-
-
-
- types.submoduleWith {
- modules,
- specialArgs ? {},
- shorthandOnlyDefinesConfig
- ? false }
-
-
-
- Like types.submodule, but more flexible
- and with better defaults. It has parameters
-
-
-
-
- modules A list
- of modules to use by default for this submodule type.
- This gets combined with all option definitions to build
- the final list of modules that will be included.
-
-
-
- Only options defined with this argument are included
- in rendered documentation.
-
-
-
-
-
- specialArgs An
- attribute set of extra arguments to be passed to the
- module functions. The option
- _module.args should be used instead
- for most arguments since it allows overriding.
- specialArgs
- should only be used for arguments that can’t go through
- the module fixed-point, because of infinite recursion or
- other problems. An example is overriding the
- lib argument, because
- lib itself is used to define
- _module.args, which makes using
- _module.args to define it impossible.
-
-
-
-
- shorthandOnlyDefinesConfig
- Whether definitions of this type should default to the
- config section of a module (see
- Example: Structure of
- NixOS Modules) if it is an attribute set.
- Enabling this only has a benefit when the submodule
- defines an option named config or
- options. In such a case it would
- allow the option to be set with
- the-submodule.config = "value"
- instead of requiring
- the-submodule.config.config = "value".
- This is because only when modules
- don’t set the
- config or options
- keys, all keys are interpreted as option definitions in
- the config section. Enabling this
- option implicitly puts all attributes in the
- config section.
-
-
- With this option enabled, defining a
- non-config section requires using a
- function:
- the-submodule = { ... }: { options = { ... }; }.
-
-
-
-
-
-
-
- types.deferredModule
-
-
-
- Whereas submodule represents an option
- tree, deferredModule represents a module
- value, such as a module file or a configuration.
-
-
- It can be set multiple times.
-
-
- Module authors can use its value in
- imports, in
- submoduleWiths
- modules or in
- evalModules
- modules parameter, among other places.
-
-
- Note that imports must be evaluated
- before the module fixpoint. Because of this, deferred
- modules can only be imported into other
- fixpoints, such as submodules.
-
-
- One use case for this type is the type of a
- default module that allow the user to affect
- all submodules in an attrsOf submodule at
- once. This is more convenient and discoverable than
- expecting the module user to type-merge with the
- attrsOf submodule option.
-
-
-
-
-
-
- Composed types
-
- Composed types are types that take a type as parameter.
- listOf int and
- either int str are examples of composed types.
-
-
-
-
- types.listOf
- t
-
-
-
- A list of t type,
- e.g. types.listOf int. Multiple
- definitions are merged with list concatenation.
-
-
-
-
-
- types.attrsOf
- t
-
-
-
- An attribute set of where all the values are of
- t type. Multiple
- definitions result in the joined attribute set.
-
-
-
- This type is strict in its values,
- which in turn means attributes cannot depend on other
- attributes. See types.lazyAttrsOf for
- a lazy version.
-
-
-
-
-
-
- types.lazyAttrsOf
- t
-
-
-
- An attribute set of where all the values are of
- t type. Multiple
- definitions result in the joined attribute set. This is the
- lazy version of types.attrsOf , allowing
- attributes to depend on each other.
-
-
-
- This version does not fully support conditional
- definitions! With an option foo of this
- type and a definition
- foo.attr = lib.mkIf false 10,
- evaluating foo ? attr will return
- true even though it should be false.
- Accessing the value will then throw an error. For types
- t that have an
- emptyValue defined, that value will be
- returned instead of throwing an error. So if the type of
- foo.attr was
- lazyAttrsOf (nullOr int),
- null would be returned instead for the
- same mkIf false definition.
-
-
-
-
-
-
- types.nullOr
- t
-
-
-
- null or type
- t. Multiple
- definitions are merged according to type
- t.
-
-
-
-
-
- types.uniq
- t
-
-
-
- Ensures that type t
- cannot be merged. It is used to ensure option definitions
- are declared only once.
-
-
-
-
-
- types.unique
- { message = m }
- t
-
-
-
- Ensures that type t
- cannot be merged. Prints the message
- m, after the line
- The option <option path> is defined multiple times.
- and before a list of definition locations.
-
-
-
-
-
- types.either
- t1 t2
-
-
-
- Type t1 or type
- t2, e.g.
- with types; either int str. Multiple
- definitions cannot be merged.
-
-
-
-
-
- types.oneOf [
- t1 t2 … ]
-
-
-
- Type t1 or type
- t2 and so forth,
- e.g. with types; oneOf [ int str bool ].
- Multiple definitions cannot be merged.
-
-
-
-
-
- types.coercedTo
- from f to
-
-
-
- Type to or type
- from which will be
- coerced to type to
- using function f
- which takes an argument of type
- from and return a
- value of type to.
- Can be used to preserve backwards compatibility of an option
- if its type was changed.
-
-
-
-
-
-
- Submodule
-
- submodule is a very powerful type that defines
- a set of sub-options that are handled like a separate module.
-
-
- It takes a parameter o,
- that should be a set, or a function returning a set with an
- options key defining the sub-options. Submodule
- option definitions are type-checked accordingly to the
- options declarations. Of course, you can nest
- submodule option definitions for even higher modularity.
-
-
- The option set can be defined directly
- (Example: Directly defined
- submodule) or as reference
- (Example: Submodule defined
- as a reference).
-
-
- Note that even if your submodule’s options all have a default
- value, you will still need to provide a default value (e.g. an
- empty attribute set) if you want to allow users to leave it
- undefined.
-
-
-
- Example: Directly defined
- submodule
-
-
-options.mod = mkOption {
- description = "submodule example";
- type = with types; submodule {
- options = {
- foo = mkOption {
- type = int;
- };
- bar = mkOption {
- type = str;
- };
- };
- };
-};
-
-
-
- Example: Submodule defined as a
- reference
-
-
-let
- modOptions = {
- options = {
- foo = mkOption {
- type = int;
- };
- bar = mkOption {
- type = int;
- };
- };
- };
-in
-options.mod = mkOption {
- description = "submodule example";
- type = with types; submodule modOptions;
-};
-
-
- The submodule type is especially interesting
- when used with composed types like attrsOf or
- listOf. When composed with
- listOf
- (Example:
- Declaration of a list of submodules),
- submodule allows multiple definitions of the
- submodule option set
- (Example:
- Definition of a list of submodules).
-
-
-
- Example: Declaration of a list of
- submodules
-
-
-options.mod = mkOption {
- description = "submodule example";
- type = with types; listOf (submodule {
- options = {
- foo = mkOption {
- type = int;
- };
- bar = mkOption {
- type = str;
- };
- };
- });
-};
-
-
-
- Example: Definition of a list of
- submodules
-
-
-config.mod = [
- { foo = 1; bar = "one"; }
- { foo = 2; bar = "two"; }
-];
-
-
- When composed with attrsOf
- (Example:
- Declaration of attribute sets of submodules),
- submodule allows multiple named definitions of
- the submodule option set
- (Example:
- Definition of attribute sets of submodules).
-
-
-
- Example: Declaration of attribute sets of
- submodules
-
-
-options.mod = mkOption {
- description = "submodule example";
- type = with types; attrsOf (submodule {
- options = {
- foo = mkOption {
- type = int;
- };
- bar = mkOption {
- type = str;
- };
- };
- });
-};
-
-
-
- Example: Definition of attribute sets of
- submodules
-
-
-config.mod.one = { foo = 1; bar = "one"; };
-config.mod.two = { foo = 2; bar = "two"; };
-
-
-
- Extending types
-
- Types are mainly characterized by their check
- and merge functions.
-
-
-
-
- check
-
-
-
- The function to type check the value. Takes a value as
- parameter and return a boolean. It is possible to extend a
- type check with the addCheck function
- (Example: Adding a
- type check), or to fully override the check function
- (Example:
- Overriding a type check).
-
-
-
- Example: Adding a type
- check
-
-
-byte = mkOption {
- description = "An integer between 0 and 255.";
- type = types.addCheck types.int (x: x >= 0 && x <= 255);
-};
-
-
-
- Example: Overriding a type
- check
-
-
-nixThings = mkOption {
- description = "words that start with 'nix'";
- type = types.str // {
- check = (x: lib.hasPrefix "nix" x)
- };
-};
-
-
-
-
-
- merge
-
-
-
- Function to merge the options values when multiple values
- are set. The function takes two parameters,
- loc the option path as a list of strings,
- and defs the list of defined values as a
- list. It is possible to override a type merge function for
- custom needs.
-
-
-
-
-
-
- Custom types
-
- Custom types can be created with the
- mkOptionType function. As type creation
- includes some more complex topics such as submodule handling, it
- is recommended to get familiar with types.nix
- code before creating a new type.
-
-
- The only required parameter is name.
-
-
-
-
- name
-
-
-
- A string representation of the type function name.
-
-
-
-
-
- definition
-
-
-
- Description of the type used in documentation. Give
- information of the type and any of its arguments.
-
-
-
-
-
- check
-
-
-
- A function to type check the definition value. Takes the
- definition value as a parameter and returns a boolean
- indicating the type check result, true
- for success and false for failure.
-
-
-
-
-
- merge
-
-
-
- A function to merge multiple definitions values. Takes two
- parameters:
-
-
-
-
- loc
-
-
-
- The option path as a list of strings, e.g.
- ["boot" "loader "grub" "enable"].
-
-
-
-
-
- defs
-
-
-
- The list of sets of defined value
- and file where the value was
- defined, e.g.
- [ { file = "/foo.nix"; value = 1; } { file = "/bar.nix"; value = 2 } ].
- The merge function should return
- the merged value or throw an error in case the values
- are impossible or not meant to be merged.
-
-
-
-
-
-
-
-
- getSubOptions
-
-
-
- For composed types that can take a submodule as type
- parameter, this function generate sub-options documentation.
- It takes the current option prefix as a list and return the
- set of sub-options. Usually defined in a recursive manner by
- adding a term to the prefix, e.g.
- prefix: elemType.getSubOptions (prefix ++ ["prefix"])
- where
- "prefix"
- is the newly added prefix.
-
-
-
-
-
- getSubModules
-
-
-
- For composed types that can take a submodule as type
- parameter, this function should return the type parameters
- submodules. If the type parameter is called
- elemType, the function should just
- recursively look into submodules by returning
- elemType.getSubModules;.
-
-
-
-
-
- substSubModules
-
-
-
- For composed types that can take a submodule as type
- parameter, this function can be used to substitute the
- parameter of a submodule type. It takes a module as
- parameter and return the type with the submodule options
- substituted. It is usually defined as a type function call
- with a recursive call to substSubModules,
- e.g for a type composedType that take an
- elemtype type parameter, this function
- should be defined as
- m: composedType (elemType.substSubModules m).
-
-
-
-
-
- typeMerge
-
-
-
- A function to merge multiple type declarations. Takes the
- type to merge functor as parameter. A
- null return value means that type cannot
- be merged.
-
-
-
-
- f
-
-
-
- The type to merge functor.
-
-
-
-
-
- Note: There is a generic defaultTypeMerge
- that work with most of value and composed types.
-
-
-
-
-
- functor
-
-
-
- An attribute set representing the type. It is used for type
- operations and has the following keys:
-
-
-
-
- type
-
-
-
- The type function.
-
-
-
-
-
- wrapped
-
-
-
- Holds the type parameter for composed types.
-
-
-
-
-
- payload
-
-
-
- Holds the value parameter for value types. The types
- that have a payload are the
- enum,
- separatedString and
- submodule types.
-
-
-
-
-
- binOp
-
-
-
- A binary operation that can merge the payloads of two
- same types. Defined as a function that take two
- payloads as parameters and return the payloads merged.
-
-
-
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/replace-modules.section.xml b/nixos/doc/manual/from_md/development/replace-modules.section.xml
deleted file mode 100644
index d8aaf59df366..000000000000
--- a/nixos/doc/manual/from_md/development/replace-modules.section.xml
+++ /dev/null
@@ -1,70 +0,0 @@
-
- Replace Modules
-
- Modules that are imported can also be disabled. The option
- declarations, config implementation and the imports of a disabled
- module will be ignored, allowing another to take its place. This can
- be used to import a set of modules from another channel while
- keeping the rest of the system on a stable release.
-
-
- disabledModules is a top level attribute like
- imports, options and
- config. It contains a list of modules that will
- be disabled. This can either be the full path to the module or a
- string with the filename relative to the modules path (eg.
- <nixpkgs/nixos/modules> for nixos).
-
-
- This example will replace the existing postgresql module with the
- version defined in the nixos-unstable channel while keeping the rest
- of the modules and packages from the original nixos channel. This
- only overrides the module definition, this won’t use postgresql from
- nixos-unstable unless explicitly configured to do so.
-
-
-{ config, lib, pkgs, ... }:
-
-{
- disabledModules = [ "services/databases/postgresql.nix" ];
-
- imports =
- [ # Use postgresql service from nixos-unstable channel.
- # sudo nix-channel --add https://nixos.org/channels/nixos-unstable nixos-unstable
- <nixos-unstable/nixos/modules/services/databases/postgresql.nix>
- ];
-
- services.postgresql.enable = true;
-}
-
-
- This example shows how to define a custom module as a replacement
- for an existing module. Importing this module will disable the
- original module without having to know its implementation details.
-
-
-{ config, lib, pkgs, ... }:
-
-with lib;
-
-let
- cfg = config.programs.man;
-in
-
-{
- disabledModules = [ "services/programs/man.nix" ];
-
- options = {
- programs.man.enable = mkOption {
- type = types.bool;
- default = true;
- description = "Whether to enable manual pages.";
- };
- };
-
- config = mkIf cfg.enabled {
- warnings = [ "disabled manpages for production deployments." ];
- };
-}
-
-
diff --git a/nixos/doc/manual/from_md/development/running-nixos-tests-interactively.section.xml b/nixos/doc/manual/from_md/development/running-nixos-tests-interactively.section.xml
deleted file mode 100644
index 30aa24f26e63..000000000000
--- a/nixos/doc/manual/from_md/development/running-nixos-tests-interactively.section.xml
+++ /dev/null
@@ -1,104 +0,0 @@
-
- Running Tests interactively
-
- The test itself can be run interactively. This is particularly
- useful when developing or debugging a test:
-
-
-$ nix-build . -A nixosTests.login.driverInteractive
-$ ./result/bin/nixos-test-driver
-[...]
->>>
-
-
- You can then take any Python statement, e.g.
-
-
->>> start_all()
->>> test_script()
->>> machine.succeed("touch /tmp/foo")
->>> print(machine.succeed("pwd")) # Show stdout of command
-
-
- The function test_script executes the entire test
- script and drops you back into the test driver command line upon its
- completion. This allows you to inspect the state of the VMs after
- the test (e.g. to debug the test script).
-
-
- Shell access in interactive mode
-
- The function
- <yourmachine>.shell_interact() grants
- access to a shell running inside a virtual machine. To use it,
- replace <yourmachine> with the name of a
- virtual machine defined in the test, for example:
- machine.shell_interact(). Keep in mind that
- this shell may not display everything correctly as it is running
- within an interactive Python REPL, and logging output from the
- virtual machine may overwrite input and output from the guest
- shell:
-
-
->>> machine.shell_interact()
-machine: Terminal is ready (there is no initial prompt):
-$ hostname
-machine
-
-
- As an alternative, you can proxy the guest shell to a local TCP
- server by first starting a TCP server in a terminal using the
- command:
-
-
-$ socat 'READLINE,PROMPT=$ ' tcp-listen:4444,reuseaddr`
-
-
- In the terminal where the test driver is running, connect to this
- server by using:
-
-
->>> machine.shell_interact("tcp:127.0.0.1:4444")
-
-
- Once the connection is established, you can enter commands in the
- socat terminal where socat is running.
-
-
-
- Reuse VM state
-
- You can re-use the VM states coming from a previous run by setting
- the --keep-vm-state flag.
-
-
-$ ./result/bin/nixos-test-driver --keep-vm-state
-
-
- The machine state is stored in the
- $TMPDIR/vm-state-machinename directory.
-
-
-
- Interactive-only test configuration
-
- The .driverInteractive attribute combines the
- regular test configuration with definitions from the
- interactive
- submodule. This gives you a more usable, graphical, but
- slightly different configuration.
-
-
- You can add your own interactive-only test configuration by adding
- extra configuration to the
- interactive
- submodule.
-
-
- To interactively run only the regular configuration, build the
- <test>.driver attribute instead, and call
- it with the flag
- result/bin/nixos-test-driver --interactive.
-
-
-
diff --git a/nixos/doc/manual/from_md/development/running-nixos-tests.section.xml b/nixos/doc/manual/from_md/development/running-nixos-tests.section.xml
deleted file mode 100644
index 23abb546899f..000000000000
--- a/nixos/doc/manual/from_md/development/running-nixos-tests.section.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
- Running Tests
-
- You can run tests using nix-build. For example,
- to run the test
- login.nix,
- you do:
-
-
-$ cd /my/git/clone/of/nixpkgs
-$ nix-build -A nixosTests.login
-
-
- After building/downloading all required dependencies, this will
- perform a build that starts a QEMU/KVM virtual machine containing a
- NixOS system. The virtual machine mounts the Nix store of the host;
- this makes VM creation very fast, as no disk image needs to be
- created. Afterwards, you can view a log of the test:
-
-
-$ nix-store --read-log result
-
-
diff --git a/nixos/doc/manual/from_md/development/settings-options.section.xml b/nixos/doc/manual/from_md/development/settings-options.section.xml
deleted file mode 100644
index 898cd3b2b6e9..000000000000
--- a/nixos/doc/manual/from_md/development/settings-options.section.xml
+++ /dev/null
@@ -1,420 +0,0 @@
-
- Options for Program Settings
-
- Many programs have configuration files where program-specific
- settings can be declared. File formats can be separated into two
- categories:
-
-
-
-
- Nix-representable ones: These can trivially be mapped to a
- subset of Nix syntax. E.g. JSON is an example, since its values
- like {"foo":{"bar":10}}
- can be mapped directly to Nix:
- { foo = { bar = 10; }; }. Other examples are
- INI, YAML and TOML. The following section explains the
- convention for these settings.
-
-
-
-
- Non-nix-representable ones: These can’t be trivially mapped to a
- subset of Nix syntax. Most generic programming languages are in
- this group, e.g. bash, since the statement
- if true; then echo hi; fi doesn’t have a
- trivial representation in Nix.
-
-
- Currently there are no fixed conventions for these, but it is
- common to have a configFile option for
- setting the configuration file path directly. The default value
- of configFile can be an auto-generated file,
- with convenient options for controlling the contents. For
- example an option of type attrsOf str can be
- used for representing environment variables which generates a
- section like export FOO="foo".
- Often it can also be useful to also include an
- extraConfig option of type
- lines to allow arbitrary text after the
- autogenerated part of the file.
-
-
-
-
- Nix-representable Formats (JSON, YAML, TOML, INI, …)
-
- By convention, formats like this are handled with a generic
- settings option, representing the full program
- configuration as a Nix value. The type of this option should
- represent the format. The most common formats have a predefined
- type and string generator already declared under
- pkgs.formats:
-
-
-
-
- pkgs.formats.javaProperties {
- comment ?
- "Generated with Nix" }
-
-
-
- A function taking an attribute set with values
-
-
-
-
- comment
-
-
-
- A string to put at the start of the file in a comment.
- It can have multiple lines.
-
-
-
-
-
- It returns the type:
- attrsOf str and a function
- generate to build a Java
- .properties file, taking care of the
- correct escaping, etc.
-
-
-
-
-
- pkgs.formats.json { }
-
-
-
- A function taking an empty attribute set (for future
- extensibility) and returning a set with JSON-specific
- attributes type and
- generate as specified
- below.
-
-
-
-
-
- pkgs.formats.yaml { }
-
-
-
- A function taking an empty attribute set (for future
- extensibility) and returning a set with YAML-specific
- attributes type and
- generate as specified
- below.
-
-
-
-
-
- pkgs.formats.ini {
- listsAsDuplicateKeys ?
- false, listToValue ?
- null, ... }
-
-
-
- A function taking an attribute set with values
-
-
-
-
- listsAsDuplicateKeys
-
-
-
- A boolean for controlling whether list values can be
- used to represent duplicate INI keys
-
-
-
-
-
- listToValue
-
-
-
- A function for turning a list of values into a single
- value.
-
-
-
-
-
- It returns a set with INI-specific attributes
- type and generate as
- specified below.
-
-
-
-
-
- pkgs.formats.toml { }
-
-
-
- A function taking an empty attribute set (for future
- extensibility) and returning a set with TOML-specific
- attributes type and
- generate as specified
- below.
-
-
-
-
-
- pkgs.formats.elixirConf { elixir ? pkgs.elixir }
-
-
-
- A function taking an attribute set with values
-
-
-
-
- elixir
-
-
-
- The Elixir package which will be used to format the
- generated output
-
-
-
-
-
- It returns a set with Elixir-Config-specific attributes
- type, lib, and
- generate as specified
- below.
-
-
- The lib attribute contains functions to
- be used in settings, for generating special Elixir values:
-
-
-
-
- mkRaw elixirCode
-
-
-
- Outputs the given string as raw Elixir code
-
-
-
-
-
- mkGetEnv { envVariable, fallback ? null }
-
-
-
- Makes the configuration fetch an environment variable
- at runtime
-
-
-
-
-
- mkAtom atom
-
-
-
- Outputs the given string as an Elixir atom, instead of
- the default Elixir binary string. Note: lowercase
- atoms still needs to be prefixed with
- :
-
-
-
-
-
- mkTuple array
-
-
-
- Outputs the given array as an Elixir tuple, instead of
- the default Elixir list
-
-
-
-
-
- mkMap attrset
-
-
-
- Outputs the given attribute set as an Elixir map,
- instead of the default Elixir keyword list
-
-
-
-
-
-
-
-
- These functions all return an attribute set with these values:
-
-
-
-
- type
-
-
-
- A module system type representing a value of the format
-
-
-
-
-
- lib
-
-
-
- Utility functions for convenience, or special interactions
- with the format. This attribute is optional. It may contain
- inside a types attribute containing types
- specific to this format.
-
-
-
-
-
- generate
- filename jsonValue
-
-
-
- A function that can render a value of the format to a file.
- Returns a file path.
-
-
-
- This function puts the value contents in the Nix store. So
- this should be avoided for secrets.
-
-
-
-
-
-
-
- Example: Module with conventional
- settings option
-
-
- The following shows a module for an example program that uses a
- JSON configuration file. It demonstrates how above values can be
- used, along with some other related best practices. See the
- comments for explanations.
-
-
-{ options, config, lib, pkgs, ... }:
-let
- cfg = config.services.foo;
- # Define the settings format used for this program
- settingsFormat = pkgs.formats.json {};
-in {
-
- options.services.foo = {
- enable = lib.mkEnableOption "foo service";
-
- settings = lib.mkOption {
- # Setting this type allows for correct merging behavior
- type = settingsFormat.type;
- default = {};
- description = ''
- Configuration for foo, see
- <link xlink:href="https://example.com/docs/foo"/>
- for supported settings.
- '';
- };
- };
-
- config = lib.mkIf cfg.enable {
- # We can assign some default settings here to make the service work by just
- # enabling it. We use `mkDefault` for values that can be changed without
- # problems
- services.foo.settings = {
- # Fails at runtime without any value set
- log_level = lib.mkDefault "WARN";
-
- # We assume systemd's `StateDirectory` is used, so we require this value,
- # therefore no mkDefault
- data_path = "/var/lib/foo";
-
- # Since we use this to create a user we need to know the default value at
- # eval time
- user = lib.mkDefault "foo";
- };
-
- environment.etc."foo.json".source =
- # The formats generator function takes a filename and the Nix value
- # representing the format value and produces a filepath with that value
- # rendered in the format
- settingsFormat.generate "foo-config.json" cfg.settings;
-
- # We know that the `user` attribute exists because we set a default value
- # for it above, allowing us to use it without worries here
- users.users.${cfg.settings.user} = { isSystemUser = true; };
-
- # ...
- };
-}
-
-
- Option declarations for attributes
-
- Some settings attributes may deserve some
- extra care. They may need a different type, default or merging
- behavior, or they are essential options that should show their
- documentation in the manual. This can be done using
- .
-
-
- We extend above example using freeform modules to declare an
- option for the port, which will enforce it to be a valid integer
- and make it show up in the manual.
-
-
-
- Example: Declaring a type-checked
- settings attribute
-
-
-settings = lib.mkOption {
- type = lib.types.submodule {
-
- freeformType = settingsFormat.type;
-
- # Declare an option for the port such that the type is checked and this option
- # is shown in the manual.
- options.port = lib.mkOption {
- type = lib.types.port;
- default = 8080;
- description = ''
- Which port this service should listen on.
- '';
- };
-
- };
- default = {};
- description = ''
- Configuration for Foo, see
- <link xlink:href="https://example.com/docs/foo"/>
- for supported values.
- '';
-};
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/sources.chapter.xml b/nixos/doc/manual/from_md/development/sources.chapter.xml
deleted file mode 100644
index aac18c9d06c8..000000000000
--- a/nixos/doc/manual/from_md/development/sources.chapter.xml
+++ /dev/null
@@ -1,90 +0,0 @@
-
- Getting the Sources
-
- By default, NixOS’s nixos-rebuild command uses
- the NixOS and Nixpkgs sources provided by the
- nixos channel (kept in
- /nix/var/nix/profiles/per-user/root/channels/nixos).
- To modify NixOS, however, you should check out the latest sources
- from Git. This is as follows:
-
-
-$ git clone https://github.com/NixOS/nixpkgs
-$ cd nixpkgs
-$ git remote update origin
-
-
- This will check out the latest Nixpkgs sources to
- ./nixpkgs the NixOS sources to
- ./nixpkgs/nixos. (The NixOS source tree lives in
- a subdirectory of the Nixpkgs repository.) The
- nixpkgs repository has branches that correspond
- to each Nixpkgs/NixOS channel (see
- for more information about channels). Thus, the Git branch
- origin/nixos-17.03 will contain the latest built
- and tested version available in the nixos-17.03
- channel.
-
-
- It’s often inconvenient to develop directly on the master branch,
- since if somebody has just committed (say) a change to GCC, then the
- binary cache may not have caught up yet and you’ll have to rebuild
- everything from source. So you may want to create a local branch
- based on your current NixOS version:
-
-
-$ nixos-version
-17.09pre104379.6e0b727 (Hummingbird)
-
-$ git checkout -b local 6e0b727
-
-
- Or, to base your local branch on the latest version available in a
- NixOS channel:
-
-
-$ git remote update origin
-$ git checkout -b local origin/nixos-17.03
-
-
- (Replace nixos-17.03 with the name of the channel
- you want to use.) You can use git merge or
- git rebase to keep your local branch in sync with
- the channel, e.g.
-
-
-$ git remote update origin
-$ git merge origin/nixos-17.03
-
-
- You can use git cherry-pick to copy commits from
- your local branch to the upstream branch.
-
-
- If you want to rebuild your system using your (modified) sources,
- you need to tell nixos-rebuild about them using
- the -I flag:
-
-
-# nixos-rebuild switch -I nixpkgs=/my/sources/nixpkgs
-
-
- If you want nix-env to use the expressions in
- /my/sources, use
- nix-env -f /my/sources/nixpkgs, or change the
- default by adding a symlink in ~/.nix-defexpr:
-
-
-$ ln -s /my/sources/nixpkgs ~/.nix-defexpr/nixpkgs
-
-
- You may want to delete the symlink
- ~/.nix-defexpr/channels_root to prevent root’s
- NixOS channel from clashing with your own tree (this may break the
- command-not-found utility though). If you want to go back to the
- default state, you may just remove the
- ~/.nix-defexpr directory completely, log out and
- log in again and it should have been recreated with a link to the
- root channels.
-
-
diff --git a/nixos/doc/manual/from_md/development/testing-installer.chapter.xml b/nixos/doc/manual/from_md/development/testing-installer.chapter.xml
deleted file mode 100644
index 286d49f3c291..000000000000
--- a/nixos/doc/manual/from_md/development/testing-installer.chapter.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
- Testing the Installer
-
- Building, burning, and booting from an installation CD is rather
- tedious, so here is a quick way to see if the installer works
- properly:
-
-
-# mount -t tmpfs none /mnt
-# nixos-generate-config --root /mnt
-$ nix-build '<nixpkgs/nixos>' -A config.system.build.nixos-install
-# ./result/bin/nixos-install
-
-
- To start a login shell in the new NixOS installation in
- /mnt:
-
-
-$ nix-build '<nixpkgs/nixos>' -A config.system.build.nixos-enter
-# ./result/bin/nixos-enter
-
-
diff --git a/nixos/doc/manual/from_md/development/unit-handling.section.xml b/nixos/doc/manual/from_md/development/unit-handling.section.xml
deleted file mode 100644
index 4c980e1213a8..000000000000
--- a/nixos/doc/manual/from_md/development/unit-handling.section.xml
+++ /dev/null
@@ -1,131 +0,0 @@
-
- Unit handling
-
- To figure out what units need to be
- started/stopped/restarted/reloaded, the script first checks the
- current state of the system, similar to what
- systemctl list-units shows. For each of the
- units, the script goes through the following checks:
-
-
-
-
- Is the unit file still in the new system? If not,
- stop the service unless it
- sets X-StopOnRemoval in the
- [Unit] section to false.
-
-
-
-
- Is it a .target unit? If so,
- start it unless it sets
- RefuseManualStart in the
- [Unit] section to true or
- X-OnlyManualStart in the
- [Unit] section to true.
- Also stop the unit again
- unless it sets X-StopOnReconfiguration to
- false.
-
-
-
-
- Are the contents of the unit files different? They are compared
- by parsing them and comparing their contents. If they are
- different but only X-Reload-Triggers in the
- [Unit] section is changed,
- reload the unit. The NixOS
- module system allows setting these triggers with the option
- systemd.services.<name>.reloadTriggers.
- There are some additional keys in the [Unit]
- section that are ignored as well. If the unit files differ in
- any way, the following actions are performed:
-
-
-
-
- .path and .slice units
- are ignored. There is no need to restart them since changes
- in their values are applied by systemd when systemd is
- reloaded.
-
-
-
-
- .mount units are
- reloaded. These mostly
- come from the /etc/fstab parser.
-
-
-
-
- .socket units are currently ignored. This
- is to be fixed at a later point.
-
-
-
-
- The rest of the units (mostly .service
- units) are then reloaded
- if X-ReloadIfChanged in the
- [Service] section is set to
- true (exposed via
- systemd.services.<name>.reloadIfChanged).
- A little exception is done for units that were deactivated
- in the meantime, for example because they require a unit
- that got stopped before. These are
- started instead of
- reloaded.
-
-
-
-
- If the reload flag is not set, some more flags decide if the
- unit is skipped. These flags are
- X-RestartIfChanged in the
- [Service] section (exposed via
- systemd.services.<name>.restartIfChanged),
- RefuseManualStop in the
- [Unit] section, and
- X-OnlyManualStart in the
- [Unit] section.
-
-
-
-
- Further behavior depends on the unit having
- X-StopIfChanged in the
- [Service] section set to
- true (exposed via
- systemd.services.<name>.stopIfChanged).
- This is set to true by default and must
- be explicitly turned off if not wanted. If the flag is
- enabled, the unit is
- stopped and then
- started. If not, the unit
- is restarted. The goal of
- the flag is to make sure that the new unit never runs in the
- old environment which is still in place before the
- activation script is run. This behavior is different when
- the service is socket-activated, as outlined in the
- following steps.
-
-
-
-
- The last thing that is taken into account is whether the
- unit is a service and socket-activated. If
- X-StopIfChanged is
- not set, the service is
- restarted with the
- others. If it is set, both the service and the socket are
- stopped and the socket is
- started, leaving socket
- activation to start the service when it’s needed.
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/what-happens-during-a-system-switch.chapter.xml b/nixos/doc/manual/from_md/development/what-happens-during-a-system-switch.chapter.xml
deleted file mode 100644
index 66ba792ddacb..000000000000
--- a/nixos/doc/manual/from_md/development/what-happens-during-a-system-switch.chapter.xml
+++ /dev/null
@@ -1,122 +0,0 @@
-
- What happens during a system switch?
-
- Running nixos-rebuild switch is one of the more
- common tasks under NixOS. This chapter explains some of the
- internals of this command to make it simpler for new module
- developers to configure their units correctly and to make it easier
- to understand what is happening and why for curious administrators.
-
-
- nixos-rebuild, like many deployment solutions,
- calls switch-to-configuration which resides in a
- NixOS system at $out/bin/switch-to-configuration.
- The script is called with the action that is to be performed like
- switch, test,
- boot. There is also the
- dry-activate action which does not really perform
- the actions but rather prints what it would do if you called it with
- test. This feature can be used to check what
- service states would be changed if the configuration was switched
- to.
-
-
- If the action is switch or
- boot, the bootloader is updated first so the
- configuration will be the next one to boot. Unless
- NIXOS_NO_SYNC is set to 1,
- /nix/store is synced to disk.
-
-
- If the action is switch or
- test, the currently running system is inspected
- and the actions to switch to the new system are calculated. This
- process takes two data sources into account:
- /etc/fstab and the current systemd status. Mounts
- and swaps are read from /etc/fstab and the
- corresponding actions are generated. If a new mount is added, for
- example, the proper .mount unit is marked to be
- started. The current systemd state is inspected, the difference
- between the current system and the desired configuration is
- calculated and actions are generated to get to this state. There are
- a lot of nuances that can be controlled by the units which are
- explained here.
-
-
- After calculating what should be done, the actions are carried out.
- The order of actions is always the same:
-
-
-
-
- Stop units (systemctl stop)
-
-
-
-
- Run activation script ($out/activate)
-
-
-
-
- See if the activation script requested more units to restart
-
-
-
-
- Restart systemd if needed
- (systemd daemon-reexec)
-
-
-
-
- Forget about the failed state of units
- (systemctl reset-failed)
-
-
-
-
- Reload systemd (systemctl daemon-reload)
-
-
-
-
- Reload systemd user instances
- (systemctl --user daemon-reload)
-
-
-
-
- Set up tmpfiles (systemd-tmpfiles --create)
-
-
-
-
- Reload units (systemctl reload)
-
-
-
-
- Restart units (systemctl restart)
-
-
-
-
- Start units (systemctl start)
-
-
-
-
- Inspect what changed during these actions and print units that
- failed and that were newly started
-
-
-
-
- Most of these actions are either self-explaining but some of them
- have to do with our units or the activation script. For this reason,
- these topics are explained in the next sections.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/writing-documentation.chapter.xml b/nixos/doc/manual/from_md/development/writing-documentation.chapter.xml
deleted file mode 100644
index 0d8a33df2069..000000000000
--- a/nixos/doc/manual/from_md/development/writing-documentation.chapter.xml
+++ /dev/null
@@ -1,144 +0,0 @@
-
- Writing NixOS Documentation
-
- As NixOS grows, so too does the need for a catalogue and explanation
- of its extensive functionality. Collecting pertinent information
- from disparate sources and presenting it in an accessible style
- would be a worthy contribution to the project.
-
-
- Building the Manual
-
- The DocBook sources of the
- are in the
- nixos/doc/manual
- subdirectory of the Nixpkgs repository.
-
-
- You can quickly validate your edits with make:
-
-
-$ cd /path/to/nixpkgs/nixos/doc/manual
-$ nix-shell
-nix-shell$ make
-
-
- Once you are done making modifications to the manual, it’s
- important to build it before committing. You can do that as
- follows:
-
-
-nix-build nixos/release.nix -A manual.x86_64-linux
-
-
- When this command successfully finishes, it will tell you where
- the manual got generated. The HTML will be accessible through the
- result symlink at
- ./result/share/doc/nixos/index.html.
-
-
-
- Editing DocBook XML
-
- For general information on how to write in DocBook, see
- DocBook
- 5: The Definitive Guide.
-
-
- Emacs nXML Mode is very helpful for editing DocBook XML because it
- validates the document as you write, and precisely locates errors.
- To use it, see .
-
-
- Pandoc can generate
- DocBook XML from a multitude of formats, which makes a good
- starting point. Here is an example of Pandoc invocation to convert
- GitHub-Flavoured MarkDown to DocBook 5 XML:
-
-
-pandoc -f markdown_github -t docbook5 docs.md -o my-section.md
-
-
- Pandoc can also quickly convert a single
- section.xml to HTML, which is helpful when
- drafting.
-
-
- Sometimes writing valid DocBook is simply too difficult. In this
- case, submit your documentation updates in a
- GitHub
- Issue and someone will handle the conversion to XML for
- you.
-
-
-
- Creating a Topic
-
- You can use an existing topic as a basis for the new topic or
- create a topic from scratch.
-
-
- Keep the following guidelines in mind when you create and add a
- topic:
-
-
-
-
- The NixOS
- book
- element is in nixos/doc/manual/manual.xml.
- It includes several
- parts
- which are in subdirectories.
-
-
-
-
- Store the topic file in the same directory as the
- part to which it belongs. If your topic is
- about configuring a NixOS module, then the XML file can be
- stored alongside the module definition nix
- file.
-
-
-
-
- If you include multiple words in the file name, separate the
- words with a dash. For example:
- ipv6-config.xml.
-
-
-
-
- Make sure that the xml:id value is unique.
- You can use abbreviations if the ID is too long. For example:
- nixos-config.
-
-
-
-
- Determine whether your topic is a chapter or a section. If you
- are unsure, open an existing topic file and check whether the
- main element is chapter or section.
-
-
-
-
-
- Adding a Topic to the Book
-
- Open the parent XML file and add an xi:include
- element to the list of chapters with the file name of the topic
- that you created. If you created a section, you
- add the file to the chapter file. If you
- created a chapter, you add the file to the
- part file.
-
-
- If the topic is about configuring a NixOS module, it can be
- automatically included in the manual by using the
- meta.doc attribute. See
- for an explanation.
-
-
-
diff --git a/nixos/doc/manual/from_md/development/writing-modules.chapter.xml b/nixos/doc/manual/from_md/development/writing-modules.chapter.xml
deleted file mode 100644
index 35e94845c97e..000000000000
--- a/nixos/doc/manual/from_md/development/writing-modules.chapter.xml
+++ /dev/null
@@ -1,245 +0,0 @@
-
- Writing NixOS Modules
-
- NixOS has a modular system for declarative configuration. This
- system combines multiple modules to produce the
- full system configuration. One of the modules that constitute the
- configuration is /etc/nixos/configuration.nix.
- Most of the others live in the
- nixos/modules
- subdirectory of the Nixpkgs tree.
-
-
- Each NixOS module is a file that handles one logical aspect of the
- configuration, such as a specific kind of hardware, a service, or
- network settings. A module configuration does not have to handle
- everything from scratch; it can use the functionality provided by
- other modules for its implementation. Thus a module can
- declare options that can be used by other
- modules, and conversely can define options
- provided by other modules in its own implementation. For example,
- the module
- pam.nix
- declares the option security.pam.services that
- allows other modules (e.g.
- sshd.nix)
- to define PAM services; and it defines the option
- environment.etc (declared by
- etc.nix)
- to cause files to be created in /etc/pam.d.
-
-
- In , we saw the following
- structure of NixOS modules:
-
-
-{ config, pkgs, ... }:
-
-{ option definitions
-}
-
-
- This is actually an abbreviated form of module
- that only defines options, but does not declare any. The structure
- of full NixOS modules is shown in
- Example: Structure of NixOS
- Modules.
-
-
-
- Example: Structure of NixOS
- Modules
-
-
-{ config, pkgs, ... }:
-
-{
- imports =
- [ paths of other modules
- ];
-
- options = {
- option declarations
- };
-
- config = {
- option definitions
- };
-}
-
-
- The meaning of each part is as follows.
-
-
-
-
- The first line makes the current Nix expression a function. The
- variable pkgs contains Nixpkgs (by default,
- it takes the nixpkgs entry of
- NIX_PATH, see the
- Nix
- manual for further details), while
- config contains the full system
- configuration. This line can be omitted if there is no reference
- to pkgs and config inside
- the module.
-
-
-
-
- This imports list enumerates the paths to
- other NixOS modules that should be included in the evaluation of
- the system configuration. A default set of modules is defined in
- the file modules/module-list.nix. These don’t
- need to be added in the import list.
-
-
-
-
- The attribute options is a nested set of
- option declarations (described below).
-
-
-
-
- The attribute config is a nested set of
- option definitions (also described below).
-
-
-
-
- Example: NixOS Module for the
- locate Service shows a module that handles the
- regular update of the locate database, an index of
- all files in the file system. This module declares two options that
- can be defined by other modules (typically the user’s
- configuration.nix):
- services.locate.enable (whether the database
- should be updated) and services.locate.interval
- (when the update should be done). It implements its functionality by
- defining two options declared by other modules:
- systemd.services (the set of all systemd
- services) and systemd.timers (the list of
- commands to be executed periodically by systemd).
-
-
- Care must be taken when writing systemd services using
- Exec* directives. By default systemd performs
- substitution on %<char> specifiers in these
- directives, expands environment variables from
- $FOO and ${FOO}, splits
- arguments on whitespace, and splits commands on
- ;. All of these must be escaped to avoid
- unexpected substitution or splitting when interpolating into an
- Exec* directive, e.g. when using an
- extraArgs option to pass additional arguments to
- the service. The functions
- utils.escapeSystemdExecArg and
- utils.escapeSystemdExecArgs are provided for
- this, see Example: Escaping in
- Exec directives for an example. When using these functions
- system environment substitution should not be
- disabled explicitly.
-
-
-
- Example: NixOS Module for the
- locate Service
-
-
-{ config, lib, pkgs, ... }:
-
-with lib;
-
-let
- cfg = config.services.locate;
-in {
- options.services.locate = {
- enable = mkOption {
- type = types.bool;
- default = false;
- description = ''
- If enabled, NixOS will periodically update the database of
- files used by the locate command.
- '';
- };
-
- interval = mkOption {
- type = types.str;
- default = "02:15";
- example = "hourly";
- description = ''
- Update the locate database at this interval. Updates by
- default at 2:15 AM every day.
-
- The format is described in
- systemd.time(7).
- '';
- };
-
- # Other options omitted for documentation
- };
-
- config = {
- systemd.services.update-locatedb =
- { description = "Update Locate Database";
- path = [ pkgs.su ];
- script =
- ''
- mkdir -m 0755 -p $(dirname ${toString cfg.output})
- exec updatedb \
- --localuser=${cfg.localuser} \
- ${optionalString (!cfg.includeStore) "--prunepaths='/nix/store'"} \
- --output=${toString cfg.output} ${concatStringsSep " " cfg.extraFlags}
- '';
- };
-
- systemd.timers.update-locatedb = mkIf cfg.enable
- { description = "Update timer for locate database";
- partOf = [ "update-locatedb.service" ];
- wantedBy = [ "timers.target" ];
- timerConfig.OnCalendar = cfg.interval;
- };
- };
-}
-
-
-
- Example: Escaping in Exec
- directives
-
-
-{ config, lib, pkgs, utils, ... }:
-
-with lib;
-
-let
- cfg = config.services.echo;
- echoAll = pkgs.writeScript "echo-all" ''
- #! ${pkgs.runtimeShell}
- for s in "$@"; do
- printf '%s\n' "$s"
- done
- '';
- args = [ "a%Nything" "lang=\${LANG}" ";" "/bin/sh -c date" ];
-in {
- systemd.services.echo =
- { description = "Echo to the journal";
- wantedBy = [ "multi-user.target" ];
- serviceConfig.Type = "oneshot";
- serviceConfig.ExecStart = ''
- ${echoAll} ${utils.escapeSystemdExecArgs args}
- '';
- };
-}
-
-
-
-
-
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/development/writing-nixos-tests.section.xml b/nixos/doc/manual/from_md/development/writing-nixos-tests.section.xml
deleted file mode 100644
index 308f7c6fb0f6..000000000000
--- a/nixos/doc/manual/from_md/development/writing-nixos-tests.section.xml
+++ /dev/null
@@ -1,782 +0,0 @@
-
- Writing Tests
-
- A NixOS test is a module that has the following structure:
-
-
-{
-
- # One or more machines:
- nodes =
- { machine =
- { config, pkgs, ... }: { … };
- machine2 =
- { config, pkgs, ... }: { … };
- …
- };
-
- testScript =
- ''
- Python code…
- '';
-}
-
-
- We refer to the whole test above as a test module, whereas the
- values in
- nodes.<name>
- are NixOS modules themselves.
-
-
- The option
- testScript
- is a piece of Python code that executes the test (described below).
- During the test, it will start one or more virtual machines, the
- configuration of which is described by the option
- nodes.
-
-
- An example of a single-node test is
- login.nix.
- It only needs a single machine to test whether users can log in on
- the virtual console, whether device ownership is correctly
- maintained when switching between consoles, and so on. An
- interesting multi-node test is
- nfs/simple.nix.
- It uses two client nodes to test correct locking across server
- crashes.
-
-
- Calling a test
-
- Tests are invoked differently depending on whether the test is
- part of NixOS or lives in a different project.
-
-
- Testing within NixOS
-
- Tests that are part of NixOS are added to
- nixos/tests/all-tests.nix.
-
-
- hostname = runTest ./hostname.nix;
-
-
- Overrides can be added by defining an anonymous module in
- all-tests.nix.
-
-
- hostname = runTest {
- imports = [ ./hostname.nix ];
- defaults.networking.firewall.enable = false;
- };
-
-
- You can run a test with attribute name
- hostname in
- nixos/tests/all-tests.nix by invoking:
-
-
-cd /my/git/clone/of/nixpkgs
-nix-build -A nixosTests.hostname
-
-
-
- Testing outside the NixOS project
-
- Outside the nixpkgs repository, you can
- instantiate the test by first importing the NixOS library,
-
-
-let nixos-lib = import (nixpkgs + "/nixos/lib") { };
-in
-
-nixos-lib.runTest {
- imports = [ ./test.nix ];
- hostPkgs = pkgs; # the Nixpkgs package set used outside the VMs
- defaults.services.foo.package = mypkg;
-}
-
-
- runTest returns a derivation that runs the
- test.
-
-
-
-
- Configuring the nodes
-
- There are a few special NixOS options for test VMs:
-
-
-
-
- virtualisation.memorySize
-
-
-
- The memory of the VM in megabytes.
-
-
-
-
-
- virtualisation.vlans
-
-
-
- The virtual networks to which the VM is connected. See
- nat.nix
- for an example.
-
-
-
-
-
- virtualisation.writableStore
-
-
-
- By default, the Nix store in the VM is not writable. If you
- enable this option, a writable union file system is mounted
- on top of the Nix store to make it appear writable. This is
- necessary for tests that run Nix operations that modify the
- store.
-
-
-
-
-
- For more options, see the module
- qemu-vm.nix.
-
-
- The test script is a sequence of Python statements that perform
- various actions, such as starting VMs, executing commands in the
- VMs, and so on. Each virtual machine is represented as an object
- stored in the variable name if this is also the
- identifier of the machine in the declarative config. If you
- specified a node nodes.machine, the following
- example starts the machine, waits until it has finished booting,
- then executes a command and checks that the output is more-or-less
- correct:
-
-
-machine.start()
-machine.wait_for_unit("default.target")
-if not "Linux" in machine.succeed("uname"):
- raise Exception("Wrong OS")
-
-
- The first line is technically unnecessary; machines are implicitly
- started when you first execute an action on them (such as
- wait_for_unit or succeed).
- If you have multiple machines, you can speed up the test by
- starting them in parallel:
-
-
-start_all()
-
-
-
- Machine objects
-
- The following methods are available on machine objects:
-
-
-
-
- start
-
-
-
- Start the virtual machine. This method is asynchronous — it
- does not wait for the machine to finish booting.
-
-
-
-
-
- shutdown
-
-
-
- Shut down the machine, waiting for the VM to exit.
-
-
-
-
-
- crash
-
-
-
- Simulate a sudden power failure, by telling the VM to exit
- immediately.
-
-
-
-
-
- block
-
-
-
- Simulate unplugging the Ethernet cable that connects the
- machine to the other machines.
-
-
-
-
-
- unblock
-
-
-
- Undo the effect of block.
-
-
-
-
-
- screenshot
-
-
-
- Take a picture of the display of the virtual machine, in PNG
- format. The screenshot is linked from the HTML log.
-
-
-
-
-
- get_screen_text_variants
-
-
-
- Return a list of different interpretations of what is
- currently visible on the machine’s screen using optical
- character recognition. The number and order of the
- interpretations is not specified and is subject to change,
- but if no exception is raised at least one will be returned.
-
-
-
- This requires
- enableOCR
- to be set to true.
-
-
-
-
-
-
- get_screen_text
-
-
-
- Return a textual representation of what is currently visible
- on the machine’s screen using optical character recognition.
-
-
-
- This requires
- enableOCR
- to be set to true.
-
-
-
-
-
-
- send_monitor_command
-
-
-
- Send a command to the QEMU monitor. This is rarely used, but
- allows doing stuff such as attaching virtual USB disks to a
- running machine.
-
-
-
-
-
- send_key
-
-
-
- Simulate pressing keys on the virtual keyboard, e.g.,
- send_key("ctrl-alt-delete").
-
-
-
-
-
- send_chars
-
-
-
- Simulate typing a sequence of characters on the virtual
- keyboard, e.g.,
- send_chars("foobar\n") will
- type the string foobar followed by the
- Enter key.
-
-
-
-
-
- send_console
-
-
-
- Send keys to the kernel console. This allows interaction
- with the systemd emergency mode, for example. Takes a string
- that is sent, e.g.,
- send_console("\n\nsystemctl default\n").
-
-
-
-
-
- execute
-
-
-
- Execute a shell command, returning a list
- (status, stdout).
-
-
- Commands are run with set -euo pipefail
- set:
-
-
-
-
- If several commands are separated by
- ; and one fails, the command as a
- whole will fail.
-
-
-
-
- For pipelines, the last non-zero exit status will be
- returned (if there is one; otherwise zero will be
- returned).
-
-
-
-
- Dereferencing unset variables fails the command.
-
-
-
-
- It will wait for stdout to be closed.
-
-
-
-
- If the command detaches, it must close stdout, as
- execute will wait for this to consume all
- output reliably. This can be achieved by redirecting stdout
- to stderr >&2, to
- /dev/console,
- /dev/null or a file. Examples of
- detaching commands are sleep 365d &,
- where the shell forks a new process that can write to stdout
- and xclip -i, where the
- xclip command itself forks without
- closing stdout.
-
-
- Takes an optional parameter check_return
- that defaults to True. Setting this
- parameter to False will not check for the
- return code and return -1 instead. This can be used for
- commands that shut down the VM and would therefore break the
- pipe that would be used for retrieving the return code.
-
-
- A timeout for the command can be specified (in seconds)
- using the optional timeout parameter,
- e.g., execute(cmd, timeout=10) or
- execute(cmd, timeout=None). The default
- is 900 seconds.
-
-
-
-
-
- succeed
-
-
-
- Execute a shell command, raising an exception if the exit
- status is not zero, otherwise returning the standard output.
- Similar to execute, except that the
- timeout is None by default. See
- execute for details on command execution.
-
-
-
-
-
- fail
-
-
-
- Like succeed, but raising an exception if
- the command returns a zero status.
-
-
-
-
-
- wait_until_succeeds
-
-
-
- Repeat a shell command with 1-second intervals until it
- succeeds. Has a default timeout of 900 seconds which can be
- modified, e.g.
- wait_until_succeeds(cmd, timeout=10). See
- execute for details on command execution.
-
-
-
-
-
- wait_until_fails
-
-
-
- Like wait_until_succeeds, but repeating
- the command until it fails.
-
-
-
-
-
- wait_for_unit
-
-
-
- Wait until the specified systemd unit has reached the
- active state.
-
-
-
-
-
- wait_for_file
-
-
-
- Wait until the specified file exists.
-
-
-
-
-
- wait_for_open_port
-
-
-
- Wait until a process is listening on the given TCP port and
- IP address (default localhost).
-
-
-
-
-
- wait_for_closed_port
-
-
-
- Wait until nobody is listening on the given TCP port and IP
- address (default localhost).
-
-
-
-
-
- wait_for_x
-
-
-
- Wait until the X11 server is accepting connections.
-
-
-
-
-
- wait_for_text
-
-
-
- Wait until the supplied regular expressions matches the
- textual contents of the screen by using optical character
- recognition (see get_screen_text and
- get_screen_text_variants).
-
-
-
- This requires
- enableOCR
- to be set to true.
-
-
-
-
-
-
- wait_for_console_text
-
-
-
- Wait until the supplied regular expressions match a line of
- the serial console output. This method is useful when OCR is
- not possible or accurate enough.
-
-
-
-
-
- wait_for_window
-
-
-
- Wait until an X11 window has appeared whose name matches the
- given regular expression, e.g.,
- wait_for_window("Terminal").
-
-
-
-
-
- copy_from_host
-
-
-
- Copies a file from host to machine, e.g.,
- copy_from_host("myfile", "/etc/my/important/file").
-
-
- The first argument is the file on the host. The file needs
- to be accessible while building the nix derivation. The
- second argument is the location of the file on the machine.
-
-
-
-
-
- systemctl
-
-
-
- Runs systemctl commands with optional
- support for systemctl --user
-
-
-machine.systemctl("list-jobs --no-pager") # runs `systemctl list-jobs --no-pager`
-machine.systemctl("list-jobs --no-pager", "any-user") # spawns a shell for `any-user` and runs `systemctl --user list-jobs --no-pager`
-
-
-
-
-
- shell_interact
-
-
-
- Allows you to directly interact with the guest shell. This
- should only be used during test development, not in
- production tests. Killing the interactive session with
- Ctrl-d or Ctrl-c also
- ends the guest session.
-
-
-
-
-
- console_interact
-
-
-
- Allows you to directly interact with QEMU’s stdin. This
- should only be used during test development, not in
- production tests. Output from QEMU is only read line-wise.
- Ctrl-c kills QEMU and
- Ctrl-d closes console and returns to the
- test runner.
-
-
-
-
-
- To test user units declared by
- systemd.user.services the optional
- user argument can be used:
-
-
-machine.start()
-machine.wait_for_x()
-machine.wait_for_unit("xautolock.service", "x-session-user")
-
-
- This applies to systemctl,
- get_unit_info,
- wait_for_unit, start_job and
- stop_job.
-
-
- For faster dev cycles it’s also possible to disable the
- code-linters (this shouldn’t be committed though):
-
-
-{
- skipLint = true;
- nodes.machine =
- { config, pkgs, ... }:
- { configuration…
- };
-
- testScript =
- ''
- Python code…
- '';
-}
-
-
- This will produce a Nix warning at evaluation time. To fully
- disable the linter, wrap the test script in comment directives to
- disable the Black linter directly (again, don’t commit this within
- the Nixpkgs repository):
-
-
- testScript =
- ''
- # fmt: off
- Python code…
- # fmt: on
- '';
-
-
- Similarly, the type checking of test scripts can be disabled in
- the following way:
-
-
-{
- skipTypeCheck = true;
- nodes.machine =
- { config, pkgs, ... }:
- { configuration…
- };
-}
-
-
-
- Failing tests early
-
- To fail tests early when certain invariants are no longer met
- (instead of waiting for the build to time out), the decorator
- polling_condition is provided. For example, if
- we are testing a program foo that should not
- quit after being started, we might write the following:
-
-
-@polling_condition
-def foo_running():
- machine.succeed("pgrep -x foo")
-
-
-machine.succeed("foo --start")
-machine.wait_until_succeeds("pgrep -x foo")
-
-with foo_running:
- ... # Put `foo` through its paces
-
-
- polling_condition takes the following
- (optional) arguments:
-
-
-
-
- seconds_interval
-
-
-
- specifies how often the condition should be polled:
-
-
-
-
-
-@polling_condition(seconds_interval=10)
-def foo_running():
- machine.succeed("pgrep -x foo")
-
-
-
-
- description
-
-
-
- is used in the log when the condition is checked. If this is
- not provided, the description is pulled from the docstring
- of the function. These two are therefore equivalent:
-
-
-
-
-
-@polling_condition
-def foo_running():
- "check that foo is running"
- machine.succeed("pgrep -x foo")
-
-
-@polling_condition(description="check that foo is running")
-def foo_running():
- machine.succeed("pgrep -x foo")
-
-
-
- Adding Python packages to the test script
-
- When additional Python libraries are required in the test script,
- they can be added using the parameter
- extraPythonPackages. For example, you could add
- numpy like this:
-
-
-{
- extraPythonPackages = p: [ p.numpy ];
-
- nodes = { };
-
- # Type checking on extra packages doesn't work yet
- skipTypeCheck = true;
-
- testScript = ''
- import numpy as np
- assert str(np.zeros(4) == "array([0., 0., 0., 0.])")
- '';
-}
-
-
- In that case, numpy is chosen from the generic
- python3Packages.
-
-
-
- Test Options Reference
-
- The following options can be used when writing tests.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/installation/building-nixos.chapter.xml b/nixos/doc/manual/from_md/installation/building-nixos.chapter.xml
deleted file mode 100644
index 0e46c1d48ca6..000000000000
--- a/nixos/doc/manual/from_md/installation/building-nixos.chapter.xml
+++ /dev/null
@@ -1,111 +0,0 @@
-
- Building a NixOS (Live) ISO
-
- Default live installer configurations are available inside
- nixos/modules/installer/cd-dvd. For building
- other system images,
- nixos-generators
- is a good place to start looking at.
-
-
- You have two options:
-
-
-
-
- Use any of those default configurations as is
-
-
-
-
- Combine them with (any of) your host config(s)
-
-
-
-
- System images, such as the live installer ones, know how to enforce
- configuration settings on which they immediately depend in order to
- work correctly.
-
-
- However, if you are confident, you can opt to override those
- enforced values with mkForce.
-
-
- Practical Instructions
-
- To build an ISO image for the channel
- nixos-unstable:
-
-
-$ git clone https://github.com/NixOS/nixpkgs.git
-$ cd nixpkgs/nixos
-$ git switch nixos-unstable
-$ nix-build -A config.system.build.isoImage -I nixos-config=modules/installer/cd-dvd/installation-cd-minimal.nix default.nix
-
-
- To check the content of an ISO image, mount it like so:
-
-
-# mount -o loop -t iso9660 ./result/iso/cd.iso /mnt/iso
-
-
-
- Additional drivers or firmware
-
- If you need additional (non-distributable) drivers or firmware in
- the installer, you might want to extend these configurations.
-
-
- For example, to build the GNOME graphical installer ISO, but with
- support for certain WiFi adapters present in some MacBooks, you
- can create the following file at
- modules/installer/cd-dvd/installation-cd-graphical-gnome-macbook.nix:
-
-
-{ config, ... }:
-
-{
- imports = [ ./installation-cd-graphical-gnome.nix ];
-
- boot.initrd.kernelModules = [ "wl" ];
-
- boot.kernelModules = [ "kvm-intel" "wl" ];
- boot.extraModulePackages = [ config.boot.kernelPackages.broadcom_sta ];
-}
-
-
- Then build it like in the example above:
-
-
-$ git clone https://github.com/NixOS/nixpkgs.git
-$ cd nixpkgs/nixos
-$ export NIXPKGS_ALLOW_UNFREE=1
-$ nix-build -A config.system.build.isoImage -I nixos-config=modules/installer/cd-dvd/installation-cd-graphical-gnome-macbook.nix default.nix
-
-
-
- Technical Notes
-
- The config value enforcement is implemented via
- mkImageMediaOverride = mkOverride 60; and
- therefore primes over simple value assignments, but also yields to
- mkForce.
-
-
- This property allows image designers to implement in semantically
- correct ways those configuration values upon which the correct
- functioning of the image depends.
-
-
- For example, the iso base image overrides those file systems which
- it needs at a minimum for correct functioning, while the installer
- base image overrides the entire file system layout because there
- can’t be any other guarantees on a live medium than those given by
- the live medium itself. The latter is especially true before
- formatting the target block device(s). On the other hand, the
- netboot iso only overrides its minimum dependencies since netboot
- images are always made-to-target.
-
-
-
diff --git a/nixos/doc/manual/from_md/installation/changing-config.chapter.xml b/nixos/doc/manual/from_md/installation/changing-config.chapter.xml
deleted file mode 100644
index 727c61c45d27..000000000000
--- a/nixos/doc/manual/from_md/installation/changing-config.chapter.xml
+++ /dev/null
@@ -1,117 +0,0 @@
-
- Changing the Configuration
-
- The file /etc/nixos/configuration.nix contains
- the current configuration of your machine. Whenever you’ve
- changed something in that
- file, you should do
-
-
-# nixos-rebuild switch
-
-
- to build the new configuration, make it the default configuration
- for booting, and try to realise the configuration in the running
- system (e.g., by restarting system services).
-
-
-
- This command doesn’t start/stop
- user services
- automatically. nixos-rebuild only runs a
- daemon-reload for each user with running user
- services.
-
-
-
-
- These commands must be executed as root, so you should either run
- them from a root shell or by prefixing them with
- sudo -i.
-
-
-
- You can also do
-
-
-# nixos-rebuild test
-
-
- to build the configuration and switch the running system to it, but
- without making it the boot default. So if (say) the configuration
- locks up your machine, you can just reboot to get back to a working
- configuration.
-
-
- There is also
-
-
-# nixos-rebuild boot
-
-
- to build the configuration and make it the boot default, but not
- switch to it now (so it will only take effect after the next
- reboot).
-
-
- You can make your configuration show up in a different submenu of
- the GRUB 2 boot screen by giving it a different profile
- name, e.g.
-
-
-# nixos-rebuild switch -p test
-
-
- which causes the new configuration (and previous ones created using
- -p test) to show up in the GRUB submenu
- NixOS - Profile test. This can be
- useful to separate test configurations from stable
- configurations.
-
-
- Finally, you can do
-
-
-$ nixos-rebuild build
-
-
- to build the configuration but nothing more. This is useful to see
- whether everything compiles cleanly.
-
-
- If you have a machine that supports hardware virtualisation, you can
- also test the new configuration in a sandbox by building and running
- a QEMU virtual machine that contains the
- desired configuration. Just do
-
-
-$ nixos-rebuild build-vm
-$ ./result/bin/run-*-vm
-
-
- The VM does not have any data from your host system, so your
- existing user accounts and home directories will not be available
- unless you have set mutableUsers = false. Another
- way is to temporarily add the following to your configuration:
-
-
-users.users.your-user.initialHashedPassword = "test";
-
-
- Important: delete the $hostname.qcow2 file if
- you have started the virtual machine at least once without the right
- users, otherwise the changes will not get picked up. You can forward
- ports on the host to the guest. For instance, the following will
- forward host port 2222 to guest port 22 (SSH):
-
-
-$ QEMU_NET_OPTS="hostfwd=tcp::2222-:22" ./result/bin/run-*-vm
-
-
- allowing you to log in via SSH (assuming you have set the
- appropriate passwords or SSH authorized keys):
-
-
-$ ssh -p 2222 localhost
-
-
diff --git a/nixos/doc/manual/from_md/installation/installing-behind-a-proxy.section.xml b/nixos/doc/manual/from_md/installation/installing-behind-a-proxy.section.xml
deleted file mode 100644
index 00b4e8766718..000000000000
--- a/nixos/doc/manual/from_md/installation/installing-behind-a-proxy.section.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
- Installing behind a proxy
-
- To install NixOS behind a proxy, do the following before running
- nixos-install.
-
-
-
-
- Update proxy configuration in
- /mnt/etc/nixos/configuration.nix to keep the
- internet accessible after reboot.
-
-
-networking.proxy.default = "http://user:password@proxy:port/";
-networking.proxy.noProxy = "127.0.0.1,localhost,internal.domain";
-
-
-
-
- Setup the proxy environment variables in the shell where you are
- running nixos-install.
-
-
-# proxy_url="http://user:password@proxy:port/"
-# export http_proxy="$proxy_url"
-# export HTTP_PROXY="$proxy_url"
-# export https_proxy="$proxy_url"
-# export HTTPS_PROXY="$proxy_url"
-
-
-
-
-
- If you are switching networks with different proxy configurations,
- use the specialisation option in
- configuration.nix to switch proxies at runtime.
- Refer to for more information.
-
-
-
diff --git a/nixos/doc/manual/from_md/installation/installing-from-other-distro.section.xml b/nixos/doc/manual/from_md/installation/installing-from-other-distro.section.xml
deleted file mode 100644
index 5f18d528d32d..000000000000
--- a/nixos/doc/manual/from_md/installation/installing-from-other-distro.section.xml
+++ /dev/null
@@ -1,388 +0,0 @@
-
- Installing from another Linux distribution
-
- Because Nix (the package manager) & Nixpkgs (the Nix packages
- collection) can both be installed on any (most?) Linux
- distributions, they can be used to install NixOS in various creative
- ways. You can, for instance:
-
-
-
-
- Install NixOS on another partition, from your existing Linux
- distribution (without the use of a USB or optical device!)
-
-
-
-
- Install NixOS on the same partition (in place!), from your
- existing non-NixOS Linux distribution using
- NIXOS_LUSTRATE.
-
-
-
-
- Install NixOS on your hard drive from the Live CD of any Linux
- distribution.
-
-
-
-
- The first steps to all these are the same:
-
-
-
-
- Install the Nix package manager:
-
-
- Short version:
-
-
-$ curl -L https://nixos.org/nix/install | sh
-$ . $HOME/.nix-profile/etc/profile.d/nix.sh # …or open a fresh shell
-
-
- More details in the
-
- Nix manual
-
-
-
-
- Switch to the NixOS channel:
-
-
- If you’ve just installed Nix on a non-NixOS distribution, you
- will be on the nixpkgs channel by default.
-
-
-$ nix-channel --list
-nixpkgs https://nixos.org/channels/nixpkgs-unstable
-
-
- As that channel gets released without running the NixOS tests,
- it will be safer to use the nixos-* channels
- instead:
-
-
-$ nix-channel --add https://nixos.org/channels/nixos-version nixpkgs
-
-
- You may want to throw in a
- nix-channel --update for good measure.
-
-
-
-
- Install the NixOS installation tools:
-
-
- You’ll need nixos-generate-config and
- nixos-install, but this also makes some man
- pages and nixos-enter available, just in case
- you want to chroot into your NixOS partition. NixOS installs
- these by default, but you don’t have NixOS yet..
-
-
-$ nix-env -f '<nixpkgs>' -iA nixos-install-tools
-
-
-
-
-
- The following 5 steps are only for installing NixOS to another
- partition. For installing NixOS in place using
- NIXOS_LUSTRATE, skip ahead.
-
-
-
- Prepare your target partition:
-
-
- At this point it is time to prepare your target partition.
- Please refer to the partitioning, file-system creation, and
- mounting steps of
-
-
- If you’re about to install NixOS in place using
- NIXOS_LUSTRATE there is nothing to do for
- this step.
-
-
-
-
- Generate your NixOS configuration:
-
-
-$ sudo `which nixos-generate-config` --root /mnt
-
-
- You’ll probably want to edit the configuration files. Refer to
- the nixos-generate-config step in
- for more information.
-
-
- Consider setting up the NixOS bootloader to give you the ability
- to boot on your existing Linux partition. For instance, if
- you’re using GRUB and your existing distribution is running
- Ubuntu, you may want to add something like this to your
- configuration.nix:
-
-
-boot.loader.grub.extraEntries = ''
- menuentry "Ubuntu" {
- search --set=ubuntu --fs-uuid 3cc3e652-0c1f-4800-8451-033754f68e6e
- configfile "($ubuntu)/boot/grub/grub.cfg"
- }
-'';
-
-
- (You can find the appropriate UUID for your partition in
- /dev/disk/by-uuid)
-
-
-
-
- Create the nixbld group and user on your
- original distribution:
-
-
-$ sudo groupadd -g 30000 nixbld
-$ sudo useradd -u 30000 -g nixbld -G nixbld nixbld
-
-
-
-
- Download/build/install NixOS:
-
-
-
- Once you complete this step, you might no longer be able to
- boot on existing systems without the help of a rescue USB
- drive or similar.
-
-
-
-
- On some distributions there are separate PATHS for programs
- intended only for root. In order for the installation to
- succeed, you might have to use
- PATH="$PATH:/usr/sbin:/sbin" in
- the following command.
-
-
-
-$ sudo PATH="$PATH" NIX_PATH="$NIX_PATH" `which nixos-install` --root /mnt
-
-
- Again, please refer to the nixos-install step
- in for more information.
-
-
- That should be it for installation to another partition!
-
-
-
-
- Optionally, you may want to clean up your non-NixOS
- distribution:
-
-
-$ sudo userdel nixbld
-$ sudo groupdel nixbld
-
-
- If you do not wish to keep the Nix package manager installed
- either, run something like
- sudo rm -rv ~/.nix-* /nix and remove the line
- that the Nix installer added to your
- ~/.profile.
-
-
-
-
-
- The following steps are only for installing NixOS in place
- using NIXOS_LUSTRATE:
-
-
-
- Generate your NixOS configuration:
-
-
-$ sudo `which nixos-generate-config`
-
-
- Note that this will place the generated configuration files in
- /etc/nixos. You’ll probably want to edit the
- configuration files. Refer to the
- nixos-generate-config step in
- for more information.
-
-
- You’ll likely want to set a root password for your first boot
- using the configuration files because you won’t have a chance to
- enter a password until after you reboot. You can initialize the
- root password to an empty one with this line: (and of course
- don’t forget to set one once you’ve rebooted or to lock the
- account with sudo passwd -l root if you use
- sudo)
-
-
-users.users.root.initialHashedPassword = "";
-
-
-
-
- Build the NixOS closure and install it in the
- system profile:
-
-
-$ nix-env -p /nix/var/nix/profiles/system -f '<nixpkgs/nixos>' -I nixos-config=/etc/nixos/configuration.nix -iA system
-
-
-
-
- Change ownership of the /nix tree to root
- (since your Nix install was probably single user):
-
-
-$ sudo chown -R 0:0 /nix
-
-
-
-
- Set up the /etc/NIXOS and
- /etc/NIXOS_LUSTRATE files:
-
-
- /etc/NIXOS officializes that this is now a
- NixOS partition (the bootup scripts require its presence).
-
-
- /etc/NIXOS_LUSTRATE tells the NixOS bootup
- scripts to move everything that’s in the
- root partition to /old-root. This will move
- your existing distribution out of the way in the very early
- stages of the NixOS bootup. There are exceptions (we do need to
- keep NixOS there after all), so the NixOS lustrate process will
- not touch:
-
-
-
-
- The /nix directory
-
-
-
-
- The /boot directory
-
-
-
-
- Any file or directory listed in
- /etc/NIXOS_LUSTRATE (one per line)
-
-
-
-
-
- Support for NIXOS_LUSTRATE was added in
- NixOS 16.09. The act of lustrating refers to
- the wiping of the existing distribution. Creating
- /etc/NIXOS_LUSTRATE can also be used on
- NixOS to remove all mutable files from your root partition
- (anything that’s not in /nix or
- /boot gets lustrated on the
- next boot.
-
-
- lustrate /ˈlʌstreɪt/ verb.
-
-
- purify by expiatory sacrifice, ceremonial washing, or some
- other ritual action.
-
-
-
- Let’s create the files:
-
-
-$ sudo touch /etc/NIXOS
-$ sudo touch /etc/NIXOS_LUSTRATE
-
-
- Let’s also make sure the NixOS configuration files are kept once
- we reboot on NixOS:
-
-
-$ echo etc/nixos | sudo tee -a /etc/NIXOS_LUSTRATE
-
-
-
-
- Finally, move the /boot directory of your
- current distribution out of the way (the lustrate process will
- take care of the rest once you reboot, but this one must be
- moved out now because NixOS needs to install its own boot files:
-
-
-
- Once you complete this step, your current distribution will no
- longer be bootable! If you didn’t get all the NixOS
- configuration right, especially those settings pertaining to
- boot loading and root partition, NixOS may not be bootable
- either. Have a USB rescue device ready in case this happens.
-
-
-
-$ sudo mv -v /boot /boot.bak &&
-sudo /nix/var/nix/profiles/system/bin/switch-to-configuration boot
-
-
- Cross your fingers, reboot, hopefully you should get a NixOS
- prompt!
-
-
-
-
- If for some reason you want to revert to the old distribution,
- you’ll need to boot on a USB rescue disk and do something along
- these lines:
-
-
-# mkdir root
-# mount /dev/sdaX root
-# mkdir root/nixos-root
-# mv -v root/* root/nixos-root/
-# mv -v root/nixos-root/old-root/* root/
-# mv -v root/boot.bak root/boot # We had renamed this by hand earlier
-# umount root
-# reboot
-
-
- This may work as is or you might also need to reinstall the boot
- loader.
-
-
- And of course, if you’re happy with NixOS and no longer need the
- old distribution:
-
-
-sudo rm -rf /old-root
-
-
-
-
- It’s also worth noting that this whole process can be automated.
- This is especially useful for Cloud VMs, where provider do not
- provide NixOS. For instance,
- nixos-infect
- uses the lustrate process to convert Digital Ocean droplets to
- NixOS from other distributions automatically.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/installation/installing-kexec.section.xml b/nixos/doc/manual/from_md/installation/installing-kexec.section.xml
deleted file mode 100644
index 40a697c74096..000000000000
--- a/nixos/doc/manual/from_md/installation/installing-kexec.section.xml
+++ /dev/null
@@ -1,94 +0,0 @@
-
- <quote>Booting</quote> into NixOS via kexec
-
- In some cases, your system might already be booted into/preinstalled
- with another Linux distribution, and booting NixOS by attaching an
- installation image is quite a manual process.
-
-
- This is particularly useful for (cloud) providers where you can’t
- boot a custom image, but get some Debian or Ubuntu installation.
-
-
- In these cases, it might be easier to use kexec
- to jump into NixOS from the running system, which
- only assumes bash and kexec to
- be installed on the machine.
-
-
- Note that kexec may not work correctly on some hardware, as devices
- are not fully re-initialized in the process. In practice, this
- however is rarely the case.
-
-
- To build the necessary files from your current version of nixpkgs,
- you can run:
-
-
-nix-build -A kexec.x86_64-linux '<nixpkgs/nixos/release.nix>'
-
-
- This will create a result directory containing
- the following:
-
-
-
-
- bzImage (the Linux kernel)
-
-
-
-
- initrd (the initrd file)
-
-
-
-
- kexec-boot (a shellscript invoking
- kexec)
-
-
-
-
- These three files are meant to be copied over to the other already
- running Linux Distribution.
-
-
- Note its symlinks pointing elsewhere, so cd in,
- and use scp * root@$destination to copy it over,
- rather than rsync.
-
-
- Once you finished copying, execute kexec-boot
- on the destination, and after some seconds, the
- machine should be booting into an (ephemeral) NixOS installation
- medium.
-
-
- In case you want to describe your own system closure to kexec into,
- instead of the default installer image, you can build your own
- configuration.nix:
-
-
-{ modulesPath, ... }: {
- imports = [
- (modulesPath + "/installer/netboot/netboot-minimal.nix")
- ];
-
- services.openssh.enable = true;
- users.users.root.openssh.authorizedKeys.keys = [
- "my-ssh-pubkey"
- ];
-}
-
-
-nix-build '<nixpkgs/nixos>' \
- --arg configuration ./configuration.nix
- --attr config.system.build.kexecTree
-
-
- Make sure your configuration.nix does still
- import netboot-minimal.nix (or
- netboot-base.nix).
-
-
diff --git a/nixos/doc/manual/from_md/installation/installing-pxe.section.xml b/nixos/doc/manual/from_md/installation/installing-pxe.section.xml
deleted file mode 100644
index 94172de65ea0..000000000000
--- a/nixos/doc/manual/from_md/installation/installing-pxe.section.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
- Booting from the <quote>netboot</quote> media (PXE)
-
- Advanced users may wish to install NixOS using an existing PXE or
- iPXE setup.
-
-
- These instructions assume that you have an existing PXE or iPXE
- infrastructure and simply want to add the NixOS installer as another
- option. To build the necessary files from your current version of
- nixpkgs, you can run:
-
-
-nix-build -A netboot.x86_64-linux '<nixpkgs/nixos/release.nix>'
-
-
- This will create a result directory containing: *
- bzImage – the Linux kernel *
- initrd – the initrd file *
- netboot.ipxe – an example ipxe script
- demonstrating the appropriate kernel command line arguments for this
- image
-
-
- If you’re using plain PXE, configure your boot loader to use the
- bzImage and initrd files and
- have it provide the same kernel command line arguments found in
- netboot.ipxe.
-
-
- If you’re using iPXE, depending on how your HTTP/FTP/etc. server is
- configured you may be able to use netboot.ipxe
- unmodified, or you may need to update the paths to the files to
- match your server’s directory layout.
-
-
- In the future we may begin making these files available as build
- products from hydra at which point we will update this documentation
- with instructions on how to obtain them either for placing on a
- dedicated TFTP server or to boot them directly over the internet.
-
-
diff --git a/nixos/doc/manual/from_md/installation/installing-usb.section.xml b/nixos/doc/manual/from_md/installation/installing-usb.section.xml
deleted file mode 100644
index cb0fd95bc7c5..000000000000
--- a/nixos/doc/manual/from_md/installation/installing-usb.section.xml
+++ /dev/null
@@ -1,135 +0,0 @@
-
- Booting from a USB flash drive
-
- The image has to be written verbatim to the USB flash drive for it
- to be bootable on UEFI and BIOS systems. Here are the recommended
- tools to do that.
-
-
- Creating bootable USB flash drive with a graphical
- tool
-
- Etcher is a popular and user-friendly tool. It works on Linux,
- Windows and macOS.
-
-
- Download it from
- balena.io,
- start the program, select the downloaded NixOS ISO, then select
- the USB flash drive and flash it.
-
-
-
- Etcher reports errors and usage statistics by default, which can
- be disabled in the settings.
-
-
-
- An alternative is
- USBImager,
- which is very simple and does not connect to the internet.
- Download the version with write-only (wo) interface for your
- system. Start the program, select the image, select the USB flash
- drive and click Write.
-
-
-
- Creating bootable USB flash drive from a Terminal on
- Linux
-
-
-
- Plug in the USB flash drive.
-
-
-
-
- Find the corresponding device with lsblk.
- You can distinguish them by their size.
-
-
-
-
- Make sure all partitions on the device are properly unmounted.
- Replace sdX with your device (e.g.
- sdb).
-
-
-
-
-sudo umount /dev/sdX*
-
-
-
-
- Then use the dd utility to write the image
- to the USB flash drive.
-
-
-
-
-sudo dd if=<path-to-image> of=/dev/sdX bs=4M conv=fsync
-
-
-
- Creating bootable USB flash drive from a Terminal on
- macOS
-
-
-
- Plug in the USB flash drive.
-
-
-
-
- Find the corresponding device with
- diskutil list. You can distinguish them by
- their size.
-
-
-
-
- Make sure all partitions on the device are properly unmounted.
- Replace diskX with your device (e.g.
- disk1).
-
-
-
-
-diskutil unmountDisk diskX
-
-
-
-
- Then use the dd utility to write the image
- to the USB flash drive.
-
-
-
-
-sudo dd if=<path-to-image> of=/dev/rdiskX bs=4m
-
-
- After dd completes, a GUI dialog The
- disk you inserted was not readable by this computer will
- pop up, which can be ignored.
-
-
-
- Using the rawrdiskX device
- instead of diskX with dd completes in minutes
- instead of hours.
-
-
-
-
-
- Eject the disk when it is finished.
-
-
-
-
-diskutil eject /dev/diskX
-
-
-
diff --git a/nixos/doc/manual/from_md/installation/installing-virtualbox-guest.section.xml b/nixos/doc/manual/from_md/installation/installing-virtualbox-guest.section.xml
deleted file mode 100644
index e43508185299..000000000000
--- a/nixos/doc/manual/from_md/installation/installing-virtualbox-guest.section.xml
+++ /dev/null
@@ -1,92 +0,0 @@
-
- Installing in a VirtualBox guest
-
- Installing NixOS into a VirtualBox guest is convenient for users who
- want to try NixOS without installing it on bare metal. If you want
- to use a pre-made VirtualBox appliance, it is available at
- the
- downloads page. If you want to set up a VirtualBox guest
- manually, follow these instructions:
-
-
-
-
- Add a New Machine in VirtualBox with OS Type Linux /
- Other Linux
-
-
-
-
- Base Memory Size: 768 MB or higher.
-
-
-
-
- New Hard Disk of 8 GB or higher.
-
-
-
-
- Mount the CD-ROM with the NixOS ISO (by clicking on CD/DVD-ROM)
-
-
-
-
- Click on Settings / System / Processor and enable PAE/NX
-
-
-
-
- Click on Settings / System / Acceleration and enable
- VT-x/AMD-V acceleration
-
-
-
-
- Click on Settings / Display / Screen and select VMSVGA as
- Graphics Controller
-
-
-
-
- Save the settings, start the virtual machine, and continue
- installation like normal
-
-
-
-
- There are a few modifications you should make in configuration.nix.
- Enable booting:
-
-
-boot.loader.grub.device = "/dev/sda";
-
-
- Also remove the fsck that runs at startup. It will always fail to
- run, stopping your boot until you press *.
-
-
-boot.initrd.checkJournalingFS = false;
-
-
- Shared folders can be given a name and a path in the host system in
- the VirtualBox settings (Machine / Settings / Shared Folders, then
- click on the Add icon). Add the following to the
- /etc/nixos/configuration.nix to auto-mount them.
- If you do not add "nofail", the system
- will not boot properly.
-
-
-{ config, pkgs, ...} :
-{
- fileSystems."/virtualboxshare" = {
- fsType = "vboxsf";
- device = "nameofthesharedfolder";
- options = [ "rw" "nofail" ];
- };
-}
-
-
- The folder will be available directly under the root directory.
-
-
diff --git a/nixos/doc/manual/from_md/installation/installing.chapter.xml b/nixos/doc/manual/from_md/installation/installing.chapter.xml
deleted file mode 100644
index 5654eb424fc3..000000000000
--- a/nixos/doc/manual/from_md/installation/installing.chapter.xml
+++ /dev/null
@@ -1,887 +0,0 @@
-
- Installing NixOS
-
- Booting from the install medium
-
- To begin the installation, you have to boot your computer from the
- install drive.
-
-
-
-
- Plug in the install drive. Then turn on or restart your
- computer.
-
-
-
-
- Open the boot menu by pressing the appropriate key, which is
- usually shown on the display on early boot. Select the USB
- flash drive (the option usually contains the word
- USB). If you choose the incorrect drive, your
- computer will likely continue to boot as normal. In that case
- restart your computer and pick a different drive.
-
-
-
- The key to open the boot menu is different across computer
- brands and even models. It can be F12, but
- also F1, F9,
- F10, Enter,
- Del, Esc or another
- function key. If you are unsure and don’t see it on the
- early boot screen, you can search online for your computers
- brand, model followed by boot from usb. The
- computer might not even have that feature, so you have to go
- into the BIOS/UEFI settings to change the boot order. Again,
- search online for details about your specific computer
- model.
-
-
- For Apple computers with Intel processors press and hold the
- ⌥ (Option or Alt) key until you see the
- boot menu. On Apple silicon press and hold the power button.
-
-
-
-
- If your computer supports both BIOS and UEFI boot, choose
- the UEFI option.
-
-
-
-
- If you use a CD for the installation, the computer will
- probably boot from it automatically. If not, choose the
- option containing the word CD from the boot
- menu.
-
-
-
-
-
- Shortly after selecting the appropriate boot drive, you should
- be presented with a menu with different installer options.
- Leave the default and wait (or press Enter to
- speed up).
-
-
-
-
- The graphical images will start their corresponding desktop
- environment and the graphical installer, which can take some
- time. The minimal images will boot to a command line. You have
- to follow the instructions in
- there.
-
-
-
-
-
- Graphical Installation
-
- The graphical installer is recommended for desktop users and will
- guide you through the installation.
-
-
-
-
- In the Welcome screen, you can select the
- language of the Installer and the installed system.
-
-
-
- Leaving the language as American English will
- make it easier to search for error messages in a search
- engine or to report an issue.
-
-
-
-
-
- Next you should choose your location to have the timezone set
- correctly. You can actually click on the map!
-
-
-
- The installer will use an online service to guess your
- location based on your public IP address.
-
-
-
-
-
- Then you can select the keyboard layout. The default keyboard
- model should work well with most desktop keyboards. If you
- have a special keyboard or notebook, your model might be in
- the list. Select the language you are most comfortable typing
- in.
-
-
-
-
- On the Users screen, you have to type in your
- display name, login name and password. You can also enable an
- option to automatically login to the desktop.
-
-
-
-
- Then you have the option to choose a desktop environment. If
- you want to create a custom setup with a window manager, you
- can select No desktop.
-
-
-
- If you don’t have a favorite desktop and don’t know which
- one to choose, you can stick to either GNOME or Plasma. They
- have a quite different design, so you should choose
- whichever you like better. They are both popular choices and
- well tested on NixOS.
-
-
-
-
-
- You have the option to allow unfree software in the next
- screen.
-
-
-
-
- The easiest option in the Partitioning screen
- is Erase disk, which will delete all data from
- the selected disk and install the system on it. Also select
- Swap (with Hibernation) in the dropdown below
- it. You have the option to encrypt the whole disk with LUKS.
-
-
-
- At the top left you see if the Installer was booted with
- BIOS or UEFI. If you know your system supports UEFI and it
- shows BIOS, reboot with the correct option.
-
-
-
-
- Make sure you have selected the correct disk at the top and
- that no valuable data is still on the disk! It will be
- deleted when formatting the disk.
-
-
-
-
-
- Check the choices you made in the Summary and
- click Install.
-
-
-
- The installation takes about 15 minutes. The time varies
- based on the selected desktop environment, internet
- connection speed and disk write speed.
-
-
-
-
-
- When the install is complete, remove the USB flash drive and
- reboot into your new system!
-
-
-
-
-
- Manual Installation
-
- NixOS can be installed on BIOS or UEFI systems. The procedure for
- a UEFI installation is broadly the same as for a BIOS
- installation. The differences are mentioned in the following
- steps.
-
-
- The NixOS manual is available by running
- nixos-help in the command line or from the
- application menu in the desktop environment.
-
-
- To have access to the command line on the graphical images, open
- Terminal (GNOME) or Konsole (Plasma) from the application menu.
-
-
- You are logged-in automatically as nixos. The
- nixos user account has an empty password so you
- can use sudo without a password:
-
-
-$ sudo -i
-
-
- You can use loadkeys to switch to your
- preferred keyboard layout. (We even provide neo2 via
- loadkeys de neo!)
-
-
- If the text is too small to be legible, try
- setfont ter-v32n to increase the font size.
-
-
- To install over a serial port connect with
- 115200n8 (e.g.
- picocom -b 115200 /dev/ttyUSB0). When the
- bootloader lists boot entries, select the serial console boot
- entry.
-
-
- Networking in the installer
-
-
-
-
-
- The boot process should have brought up networking (check
- ip a). Networking is necessary for the
- installer, since it will download lots of stuff (such as source
- tarballs or Nixpkgs channel binaries). It’s best if you have a
- DHCP server on your network. Otherwise configure networking
- manually using ifconfig.
-
-
- On the graphical installer, you can configure the network, wifi
- included, through NetworkManager. Using the
- nmtui program, you can do so even in a
- non-graphical session. If you prefer to configure the network
- manually, disable NetworkManager with
- systemctl stop NetworkManager.
-
-
- On the minimal installer, NetworkManager is not available, so
- configuration must be performed manually. To configure the wifi,
- first start wpa_supplicant with
- sudo systemctl start wpa_supplicant, then run
- wpa_cli. For most home networks, you need to
- type in the following commands:
-
-
-> add_network
-0
-> set_network 0 ssid "myhomenetwork"
-OK
-> set_network 0 psk "mypassword"
-OK
-> set_network 0 key_mgmt WPA-PSK
-OK
-> enable_network 0
-OK
-
-
- For enterprise networks, for example
- eduroam, instead do:
-
-
-> add_network
-0
-> set_network 0 ssid "eduroam"
-OK
-> set_network 0 identity "myname@example.com"
-OK
-> set_network 0 password "mypassword"
-OK
-> set_network 0 key_mgmt WPA-EAP
-OK
-> enable_network 0
-OK
-
-
- When successfully connected, you should see a line such as this
- one
-
-
-<3>CTRL-EVENT-CONNECTED - Connection to 32:85:ab:ef:24:5c completed [id=0 id_str=]
-
-
- you can now leave wpa_cli by typing
- quit.
-
-
- If you would like to continue the installation from a different
- machine you can use activated SSH daemon. You need to copy your
- ssh key to either
- /home/nixos/.ssh/authorized_keys or
- /root/.ssh/authorized_keys (Tip: For
- installers with a modifiable filesystem such as the sd-card
- installer image a key can be manually placed by mounting the
- image on a different machine). Alternatively you must set a
- password for either root or
- nixos with passwd to be
- able to login.
-
-
-
- Partitioning and formatting
-
-
-
-
-
- The NixOS installer doesn’t do any partitioning or formatting,
- so you need to do that yourself.
-
-
- The NixOS installer ships with multiple partitioning tools. The
- examples below use parted, but also provides
- fdisk, gdisk,
- cfdisk, and cgdisk.
-
-
- The recommended partition scheme differs depending if the
- computer uses Legacy Boot or
- UEFI.
-
-
- UEFI (GPT)
-
-
-
-
-
- Here’s an example partition scheme for UEFI, using
- /dev/sda as the device.
-
-
-
- You can safely ignore parted’s
- informational message about needing to update /etc/fstab.
-
-
-
-
-
- Create a GPT partition table.
-
-
-# parted /dev/sda -- mklabel gpt
-
-
-
-
- Add the root partition. This will
- fill the disk except for the end part, where the swap will
- live, and the space left in front (512MiB) which will be
- used by the boot partition.
-
-
-# parted /dev/sda -- mkpart primary 512MB -8GB
-
-
-
-
- Next, add a swap partition. The size
- required will vary according to needs, here a 8GB one is
- created.
-
-
-# parted /dev/sda -- mkpart primary linux-swap -8GB 100%
-
-
-
- The swap partition size rules are no different than for
- other Linux distributions.
-
-
-
-
-
- Finally, the boot partition. NixOS by
- default uses the ESP (EFI system partition) as its
- /boot partition. It uses the
- initially reserved 512MiB at the start of the disk.
-
-
-# parted /dev/sda -- mkpart ESP fat32 1MB 512MB
-# parted /dev/sda -- set 3 esp on
-
-
-
-
- Once complete, you can follow with
- .
-
-
-
- Legacy Boot (MBR)
-
-
-
-
-
- Here’s an example partition scheme for Legacy Boot, using
- /dev/sda as the device.
-
-
-
- You can safely ignore parted’s
- informational message about needing to update /etc/fstab.
-
-
-
-
-
- Create a MBR partition table.
-
-
-# parted /dev/sda -- mklabel msdos
-
-
-
-
- Add the root partition. This will
- fill the the disk except for the end part, where the swap
- will live.
-
-
-# parted /dev/sda -- mkpart primary 1MB -8GB
-
-
-
-
- Set the root partition’s boot flag to on. This allows the
- disk to be booted from.
-
-
-# parted /dev/sda -- set 1 boot on
-
-
-
-
- Finally, add a swap partition. The
- size required will vary according to needs, here a 8GB one
- is created.
-
-
-# parted /dev/sda -- mkpart primary linux-swap -8GB 100%
-
-
-
- The swap partition size rules are no different than for
- other Linux distributions.
-
-
-
-
-
- Once complete, you can follow with
- .
-
-
-
- Formatting
-
-
-
-
-
- Use the following commands:
-
-
-
-
- For initialising Ext4 partitions:
- mkfs.ext4. It is recommended that you
- assign a unique symbolic label to the file system using
- the option -L label, since this makes
- the file system configuration independent from device
- changes. For example:
-
-
-# mkfs.ext4 -L nixos /dev/sda1
-
-
-
-
- For creating swap partitions: mkswap.
- Again it’s recommended to assign a label to the swap
- partition: -L label. For example:
-
-
-# mkswap -L swap /dev/sda2
-
-
-
-
- UEFI systems
-
-
- For creating boot partitions: mkfs.fat.
- Again it’s recommended to assign a label to the boot
- partition: -n label. For example:
-
-
-# mkfs.fat -F 32 -n boot /dev/sda3
-
-
-
-
- For creating LVM volumes, the LVM commands, e.g.,
- pvcreate, vgcreate,
- and lvcreate.
-
-
-
-
- For creating software RAID devices, use
- mdadm.
-
-
-
-
-
-
- Installing
-
-
-
-
-
-
-
- Mount the target file system on which NixOS should be
- installed on /mnt, e.g.
-
-
-# mount /dev/disk/by-label/nixos /mnt
-
-
-
-
- UEFI systems
-
-
- Mount the boot file system on /mnt/boot,
- e.g.
-
-
-# mkdir -p /mnt/boot
-# mount /dev/disk/by-label/boot /mnt/boot
-
-
-
-
- If your machine has a limited amount of memory, you may want
- to activate swap devices now
- (swapon device). The installer (or
- rather, the build actions that it may spawn) may need quite
- a bit of RAM, depending on your configuration.
-
-
-# swapon /dev/sda2
-
-
-
-
- You now need to create a file
- /mnt/etc/nixos/configuration.nix that
- specifies the intended configuration of the system. This is
- because NixOS has a declarative
- configuration model: you create or edit a description of the
- desired configuration of your system, and then NixOS takes
- care of making it happen. The syntax of the NixOS
- configuration file is described in
- , while a list of
- available configuration options appears in
- . A minimal example is shown in
- Example: NixOS
- Configuration.
-
-
- The command nixos-generate-config can
- generate an initial configuration file for you:
-
-
-# nixos-generate-config --root /mnt
-
-
- You should then edit
- /mnt/etc/nixos/configuration.nix to suit
- your needs:
-
-
-# nano /mnt/etc/nixos/configuration.nix
-
-
- If you’re using the graphical ISO image, other editors may
- be available (such as vim). If you have
- network access, you can also install other editors – for
- instance, you can install Emacs by running
- nix-env -f '<nixpkgs>' -iA emacs.
-
-
-
-
- BIOS systems
-
-
-
- You must set the option
- to
- specify on which disk the GRUB boot loader is to be
- installed. Without it, NixOS cannot boot.
-
-
- If there are other operating systems running on the
- machine before installing NixOS, the
-
- option can be set to true to
- automatically add them to the grub menu.
-
-
-
-
-
- UEFI systems
-
-
-
- You must select a boot-loader, either system-boot or
- GRUB. The recommended option is systemd-boot: set the
- option
-
- to true.
- nixos-generate-config should do
- this automatically for new configurations when booted
- in UEFI mode.
-
-
- You may want to look at the options starting with
- boot.loader.efi
- and
- boot.loader.systemd-boot
- as well.
-
-
- If you want to use GRUB, set
- to
- nodev and
- to
- true.
-
-
- With system-boot, you should not need any special
- configuration to detect other installed systems. With
- GRUB, set
- to
- true, but this will only detect
- windows partitions, not other linux distributions. If
- you dual boot another linux distribution, use
- system-boot instead.
-
-
-
-
-
- If you need to configure networking for your machine the
- configuration options are described in
- . In particular, while wifi
- is supported on the installation image, it is not enabled by
- default in the configuration generated by
- nixos-generate-config.
-
-
- Another critical option is fileSystems,
- specifying the file systems that need to be mounted by
- NixOS. However, you typically don’t need to set it yourself,
- because nixos-generate-config sets it
- automatically in
- /mnt/etc/nixos/hardware-configuration.nix
- from your currently mounted file systems. (The configuration
- file hardware-configuration.nix is
- included from configuration.nix and will
- be overwritten by future invocations of
- nixos-generate-config; thus, you
- generally should not modify it.) Additionally, you may want
- to look at
- Hardware
- configuration for known-hardware at this point or
- after installation.
-
-
-
- Depending on your hardware configuration or type of file
- system, you may need to set the option
- boot.initrd.kernelModules to include
- the kernel modules that are necessary for mounting the
- root file system, otherwise the installed system will not
- be able to boot. (If this happens, boot from the
- installation media again, mount the target file system on
- /mnt, fix
- /mnt/etc/nixos/configuration.nix and
- rerun nixos-install.) In most cases,
- nixos-generate-config will figure out
- the required modules.
-
-
-
-
-
- Do the installation:
-
-
-# nixos-install
-
-
- This will install your system based on the configuration you
- provided. If anything fails due to a configuration problem
- or any other issue (such as a network outage while
- downloading binaries from the NixOS binary cache), you can
- re-run nixos-install after fixing your
- configuration.nix.
-
-
- As the last step, nixos-install will ask
- you to set the password for the root
- user, e.g.
-
-
-setting root password...
-New password: ***
-Retype new password: ***
-
-
-
- For unattended installations, it is possible to use
- nixos-install --no-root-passwd in order
- to disable the password prompt entirely.
-
-
-
-
-
- If everything went well:
-
-
-# reboot
-
-
-
-
- You should now be able to boot into the installed NixOS. The
- GRUB boot menu shows a list of available
- configurations (initially just one). Every time
- you change the NixOS configuration (see
- Changing
- Configuration), a new item is added to the menu. This
- allows you to easily roll back to a previous configuration
- if something goes wrong.
-
-
- You should log in and change the root
- password with passwd.
-
-
- You’ll probably want to create some user accounts as well,
- which can be done with useradd:
-
-
-$ useradd -c 'Eelco Dolstra' -m eelco
-$ passwd eelco
-
-
- You may also want to install some software. This will be
- covered in .
-
-
-
-
-
- Installation summary
-
-
-
-
-
- To summarise, Example:
- Commands for Installing NixOS on
- /dev/sda shows a typical sequence of
- commands for installing NixOS on an empty hard drive (here
- /dev/sda). Example:
- NixOS Configuration shows a corresponding configuration
- Nix expression.
-
-
-
- Example: Example partition schemes for
- NixOS on /dev/sda (MBR)
-
-
-# parted /dev/sda -- mklabel msdos
-# parted /dev/sda -- mkpart primary 1MB -8GB
-# parted /dev/sda -- mkpart primary linux-swap -8GB 100%
-
-
-
- Example: Example partition schemes for
- NixOS on /dev/sda (UEFI)
-
-
-# parted /dev/sda -- mklabel gpt
-# parted /dev/sda -- mkpart primary 512MB -8GB
-# parted /dev/sda -- mkpart primary linux-swap -8GB 100%
-# parted /dev/sda -- mkpart ESP fat32 1MB 512MB
-# parted /dev/sda -- set 3 esp on
-
-
-
- Example: Commands for Installing NixOS
- on /dev/sda
-
-
- With a partitioned disk.
-
-
-# mkfs.ext4 -L nixos /dev/sda1
-# mkswap -L swap /dev/sda2
-# swapon /dev/sda2
-# mkfs.fat -F 32 -n boot /dev/sda3 # (for UEFI systems only)
-# mount /dev/disk/by-label/nixos /mnt
-# mkdir -p /mnt/boot # (for UEFI systems only)
-# mount /dev/disk/by-label/boot /mnt/boot # (for UEFI systems only)
-# nixos-generate-config --root /mnt
-# nano /mnt/etc/nixos/configuration.nix
-# nixos-install
-# reboot
-
-
-
- Example: NixOS Configuration
-
-
-{ config, pkgs, ... }: {
- imports = [
- # Include the results of the hardware scan.
- ./hardware-configuration.nix
- ];
-
- boot.loader.grub.device = "/dev/sda"; # (for BIOS systems only)
- boot.loader.systemd-boot.enable = true; # (for UEFI systems only)
-
- # Note: setting fileSystems is generally not
- # necessary, since nixos-generate-config figures them out
- # automatically in hardware-configuration.nix.
- #fileSystems."/".device = "/dev/disk/by-label/nixos";
-
- # Enable the OpenSSH server.
- services.sshd.enable = true;
-}
-
-
-
-
- Additional installation notes
-
-
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/installation/obtaining.chapter.xml b/nixos/doc/manual/from_md/installation/obtaining.chapter.xml
deleted file mode 100644
index d187adfc0c53..000000000000
--- a/nixos/doc/manual/from_md/installation/obtaining.chapter.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
- Obtaining NixOS
-
- NixOS ISO images can be downloaded from the
- NixOS
- download page. Follow the instructions in
- to create a bootable USB
- flash drive.
-
-
- If you have a very old system that can’t boot from USB, you can burn
- the image to an empty CD. NixOS might not work very well on such
- systems.
-
-
- As an alternative to installing NixOS yourself, you can get a
- running NixOS system through several other means:
-
-
-
-
- Using virtual appliances in Open Virtualization Format (OVF)
- that can be imported into VirtualBox. These are available from
- the
- NixOS
- download page.
-
-
-
-
- Using AMIs for Amazon’s EC2. To find one for your region, please
- refer to the
- download
- page.
-
-
-
-
- Using NixOps, the NixOS-based cloud deployment tool, which
- allows you to provision VirtualBox and EC2 NixOS instances from
- declarative specifications. Check out the
- NixOps
- homepage for details.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/installation/upgrading.chapter.xml b/nixos/doc/manual/from_md/installation/upgrading.chapter.xml
deleted file mode 100644
index 99882784b46f..000000000000
--- a/nixos/doc/manual/from_md/installation/upgrading.chapter.xml
+++ /dev/null
@@ -1,152 +0,0 @@
-
- Upgrading NixOS
-
- The best way to keep your NixOS installation up to date is to use
- one of the NixOS channels. A channel is a Nix
- mechanism for distributing Nix expressions and associated binaries.
- The NixOS channels are updated automatically from NixOS’s Git
- repository after certain tests have passed and all packages have
- been built. These channels are:
-
-
-
-
- Stable channels, such as
- nixos-22.11.
- These only get conservative bug fixes and package upgrades. For
- instance, a channel update may cause the Linux kernel on your
- system to be upgraded from 4.19.34 to 4.19.38 (a minor bug fix),
- but not from 4.19.x to 4.20.x (a major change that has the
- potential to break things). Stable channels are generally
- maintained until the next stable branch is created.
-
-
-
-
- The unstable channel,
- nixos-unstable.
- This corresponds to NixOS’s main development branch, and may
- thus see radical changes between channel updates. It’s not
- recommended for production systems.
-
-
-
-
- Small channels, such as
- nixos-22.11-small
- or
- nixos-unstable-small.
- These are identical to the stable and unstable channels
- described above, except that they contain fewer binary packages.
- This means they get updated faster than the regular channels
- (for instance, when a critical security patch is committed to
- NixOS’s source tree), but may require more packages to be built
- from source than usual. They’re mostly intended for server
- environments and as such contain few GUI applications.
-
-
-
-
- To see what channels are available, go to
- https://nixos.org/channels.
- (Note that the URIs of the various channels redirect to a directory
- that contains the channel’s latest version and includes ISO images
- and VirtualBox appliances.) Please note that during the release
- process, channels that are not yet released will be present here as
- well. See the Getting NixOS page
- https://nixos.org/nixos/download.html
- to find the newest supported stable release.
-
-
- When you first install NixOS, you’re automatically subscribed to the
- NixOS channel that corresponds to your installation source. For
- instance, if you installed from a 22.11 ISO, you will be subscribed
- to the nixos-22.11 channel. To see which NixOS
- channel you’re subscribed to, run the following as root:
-
-
-# nix-channel --list | grep nixos
-nixos https://nixos.org/channels/nixos-unstable
-
-
- To switch to a different NixOS channel, do
-
-
-# nix-channel --add https://nixos.org/channels/channel-name nixos
-
-
- (Be sure to include the nixos parameter at the
- end.) For instance, to use the NixOS 22.11 stable channel:
-
-
-# nix-channel --add https://nixos.org/channels/nixos-22.11 nixos
-
-
- If you have a server, you may want to use the small
- channel instead:
-
-
-# nix-channel --add https://nixos.org/channels/nixos-22.11-small nixos
-
-
- And if you want to live on the bleeding edge:
-
-
-# nix-channel --add https://nixos.org/channels/nixos-unstable nixos
-
-
- You can then upgrade NixOS to the latest version in your chosen
- channel by running
-
-
-# nixos-rebuild switch --upgrade
-
-
- which is equivalent to the more verbose
- nix-channel --update nixos; nixos-rebuild switch.
-
-
-
- Channels are set per user. This means that running
- nix-channel --add as a non root user (or
- without sudo) will not affect configuration in
- /etc/nixos/configuration.nix
-
-
-
-
- It is generally safe to switch back and forth between channels.
- The only exception is that a newer NixOS may also have a newer Nix
- version, which may involve an upgrade of Nix’s database schema.
- This cannot be undone easily, so in that case you will not be able
- to go back to your original channel.
-
-
-
- Automatic Upgrades
-
- You can keep a NixOS system up-to-date automatically by adding the
- following to configuration.nix:
-
-
-system.autoUpgrade.enable = true;
-system.autoUpgrade.allowReboot = true;
-
-
- This enables a periodically executed systemd service named
- nixos-upgrade.service. If the
- allowReboot option is false,
- it runs nixos-rebuild switch --upgrade to
- upgrade NixOS to the latest version in the current channel. (To
- see when the service runs, see
- systemctl list-timers.) If
- allowReboot is true, then
- the system will automatically reboot if the new generation
- contains a different kernel, initrd or kernel modules. You can
- also specify a channel explicitly, e.g.
-
-
-system.autoUpgrade.channel = https://nixos.org/channels/nixos-22.11;
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1310.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1310.section.xml
deleted file mode 100644
index b4f3657b4b88..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1310.section.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-
- Release 13.10 (<quote>Aardvark</quote>, 2013/10/31)
-
- This is the first stable release branch of NixOS.
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1404.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1404.section.xml
deleted file mode 100644
index 5686545c1afb..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1404.section.xml
+++ /dev/null
@@ -1,189 +0,0 @@
-
- Release 14.04 (<quote>Baboon</quote>, 2014/04/30)
-
- This is the second stable release branch of NixOS. In addition to
- numerous new and upgraded packages and modules, this release has the
- following highlights:
-
-
-
-
- Installation on UEFI systems is now supported. See
- for details.
-
-
-
-
- Systemd has been updated to version 212, which has
- numerous
- improvements. NixOS now automatically starts systemd user
- instances when you log in. You can define global user units
- through the systemd.unit.* options.
-
-
-
-
- NixOS is now based on Glibc 2.19 and GCC 4.8.
-
-
-
-
- The default Linux kernel has been updated to 3.12.
-
-
-
-
- KDE has been updated to 4.12.
-
-
-
-
- GNOME 3.10 experimental support has been added.
-
-
-
-
- Nix has been updated to 1.7
- (details).
-
-
-
-
- NixOS now supports fully declarative management of users and
- groups. If you set users.mutableUsers to
- false, then the contents of
- /etc/passwd and /etc/group
- will be
- congruent
- to your NixOS configuration. For instance, if you remove a user
- from users.extraUsers and run
- nixos-rebuild, the user account will cease to
- exist. Also, imperative commands for managing users and groups,
- such as useradd, are no longer available. If
- users.mutableUsers is true
- (the default), then behaviour is unchanged from NixOS 13.10.
-
-
-
-
- NixOS now has basic container support, meaning you can easily
- run a NixOS instance as a container in a NixOS host system.
- These containers are suitable for testing and experimentation
- but not production use, since they’re not fully isolated from
- the host. See for details.
-
-
-
-
- Systemd units provided by packages can now be overridden from
- the NixOS configuration. For instance, if a package
- foo provides systemd units, you can say:
-
-
-{
- systemd.packages = [ pkgs.foo ];
-}
-
-
- to enable those units. You can then set or override unit options
- in the usual way, e.g.
-
-
-{
- systemd.services.foo.wantedBy = [ "multi-user.target" ];
- systemd.services.foo.serviceConfig.MemoryLimit = "512M";
-}
-
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- Nixpkgs no longer exposes unfree packages by default. If your
- NixOS configuration requires unfree packages from Nixpkgs, you
- need to enable support for them explicitly by setting:
-
-
-{
- nixpkgs.config.allowUnfree = true;
-}
-
-
- Otherwise, you get an error message such as:
-
-
- error: package ‘nvidia-x11-331.49-3.12.17’ in ‘…/nvidia-x11/default.nix:56’
- has an unfree license, refusing to evaluate
-
-
-
-
- The Adobe Flash player is no longer enabled by default in the
- Firefox and Chromium wrappers. To enable it, you must set:
-
-
-{
- nixpkgs.config.allowUnfree = true;
- nixpkgs.config.firefox.enableAdobeFlash = true; # for Firefox
- nixpkgs.config.chromium.enableAdobeFlash = true; # for Chromium
-}
-
-
-
-
- The firewall is now enabled by default. If you don’t want this,
- you need to disable it explicitly:
-
-
-{
- networking.firewall.enable = false;
-}
-
-
-
-
- The option boot.loader.grub.memtest86 has
- been renamed to
- boot.loader.grub.memtest86.enable.
-
-
-
-
- The mysql55 service has been merged into the
- mysql service, which no longer sets a default
- for the option services.mysql.package.
-
-
-
-
- Package variants are now differentiated by suffixing the name,
- rather than the version. For instance,
- sqlite-3.8.4.3-interactive is now called
- sqlite-interactive-3.8.4.3. This ensures that
- nix-env -i sqlite is unambiguous, and that
- nix-env -u won’t upgrade
- sqlite to
- sqlite-interactive or vice versa. Notably,
- this change affects the Firefox wrapper (which provides
- plugins), as it is now called
- firefox-wrapper. So when using
- nix-env, you should do
- nix-env -e firefox; nix-env -i firefox-wrapper
- if you want to keep using the wrapper. This change does not
- affect declarative package management, since attribute names
- like pkgs.firefoxWrapper were already
- unambiguous.
-
-
-
-
- The symlink /etc/ca-bundle.crt is gone.
- Programs should instead use the environment variable
- OPENSSL_X509_CERT_FILE (which points to
- /etc/ssl/certs/ca-bundle.crt).
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1412.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1412.section.xml
deleted file mode 100644
index ccaa4f6bd081..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1412.section.xml
+++ /dev/null
@@ -1,466 +0,0 @@
-
- Release 14.12 (<quote>Caterpillar</quote>, 2014/12/30)
-
- In addition to numerous new and upgraded packages, this release has
- the following highlights:
-
-
-
-
- Systemd has been updated to version 217, which has numerous
- improvements.
-
-
-
-
- Nix
- has been updated to 1.8.
-
-
-
-
- NixOS is now based on Glibc 2.20.
-
-
-
-
- KDE has been updated to 4.14.
-
-
-
-
- The default Linux kernel has been updated to 3.14.
-
-
-
-
- If users.mutableUsers is enabled (the
- default), changes made to the declaration of a user or group
- will be correctly realised when running
- nixos-rebuild. For instance, removing a user
- specification from configuration.nix will
- cause the actual user account to be deleted. If
- users.mutableUsers is disabled, it is no
- longer necessary to specify UIDs or GIDs; if omitted, they are
- allocated dynamically.
-
-
-
-
- Following new services were added since the last release:
-
-
-
-
- atftpd
-
-
-
-
- bosun
-
-
-
-
- bspwm
-
-
-
-
- chronos
-
-
-
-
- collectd
-
-
-
-
- consul
-
-
-
-
- cpuminer-cryptonight
-
-
-
-
- crashplan
-
-
-
-
- dnscrypt-proxy
-
-
-
-
- docker-registry
-
-
-
-
- docker
-
-
-
-
- etcd
-
-
-
-
- fail2ban
-
-
-
-
- fcgiwrap
-
-
-
-
- fleet
-
-
-
-
- fluxbox
-
-
-
-
- gdm
-
-
-
-
- geoclue2
-
-
-
-
- gitlab
-
-
-
-
- gitolite
-
-
-
-
- gnome3.gnome-documents
-
-
-
-
- gnome3.gnome-online-miners
-
-
-
-
- gnome3.gvfs
-
-
-
-
- gnome3.seahorse
-
-
-
-
- hbase
-
-
-
-
- i2pd
-
-
-
-
- influxdb
-
-
-
-
- kubernetes
-
-
-
-
- liquidsoap
-
-
-
-
- lxc
-
-
-
-
- mailpile
-
-
-
-
- mesos
-
-
-
-
- mlmmj
-
-
-
-
- monetdb
-
-
-
-
- mopidy
-
-
-
-
- neo4j
-
-
-
-
- nsd
-
-
-
-
- openntpd
-
-
-
-
- opentsdb
-
-
-
-
- openvswitch
-
-
-
-
- parallels-guest
-
-
-
-
- peerflix
-
-
-
-
- phd
-
-
-
-
- polipo
-
-
-
-
- prosody
-
-
-
-
- radicale
-
-
-
-
- redmine
-
-
-
-
- riemann
-
-
-
-
- scollector
-
-
-
-
- seeks
-
-
-
-
- siproxd
-
-
-
-
- strongswan
-
-
-
-
- tcsd
-
-
-
-
- teamspeak3
-
-
-
-
- thermald
-
-
-
-
- torque/mrom
-
-
-
-
- torque/server
-
-
-
-
- uhub
-
-
-
-
- unifi
-
-
-
-
- znc
-
-
-
-
- zookeeper
-
-
-
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- The default version of Apache httpd is now 2.4. If you use the
- extraConfig option to pass literal Apache
- configuration text, you may need to update it — see
- Apache’s
- documentation for details. If you wish to continue to use
- httpd 2.2, add the following line to your NixOS configuration:
-
-
-{
- services.httpd.package = pkgs.apacheHttpd_2_2;
-}
-
-
-
-
- PHP 5.3 has been removed because it is no longer supported by
- the PHP project. A
- migration
- guide is available.
-
-
-
-
- The host side of a container virtual Ethernet pair is now called
- ve-container-name rather than
- c-container-name.
-
-
-
-
- GNOME 3.10 support has been dropped. The default GNOME version
- is now 3.12.
-
-
-
-
- VirtualBox has been upgraded to 4.3.20 release. Users may be
- required to run rm -rf /tmp/.vbox*. The line
- imports = [ <nixpkgs/nixos/modules/programs/virtualbox.nix> ]
- is no longer necessary, use
- services.virtualboxHost.enable = true
- instead.
-
-
- Also, hardening mode is now enabled by default, which means that
- unless you want to use USB support, you no longer need to be a
- member of the vboxusers group.
-
-
-
-
- Chromium has been updated to 39.0.2171.65.
- enablePepperPDF is now enabled by default.
- chromium*Wrapper packages no longer exist,
- because upstream removed NSAPI support.
- chromium-stable has been renamed to
- chromium.
-
-
-
-
- Python packaging documentation is now part of nixpkgs manual. To
- override the python packages available to a custom python you
- now use pkgs.pythonFull.buildEnv.override
- instead of pkgs.pythonFull.override.
-
-
-
-
- boot.resumeDevice = "8:6" is no
- longer supported. Most users will want to leave it undefined,
- which takes the swap partitions automatically. There is an
- evaluation assertion to ensure that the string starts with a
- slash.
-
-
-
-
- The system-wide default timezone for NixOS installations changed
- from CET to UTC. To choose
- a different timezone for your system, configure
- time.timeZone in
- configuration.nix. A fairly complete list of
- possible values for that setting is available at
- https://en.wikipedia.org/wiki/List_of_tz_database_time_zones.
-
-
-
-
- GNU screen has been updated to 4.2.1, which breaks the ability
- to connect to sessions created by older versions of screen.
-
-
-
-
- The Intel GPU driver was updated to the 3.x prerelease version
- (used by most distributions) and supports DRI3 now.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1509.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1509.section.xml
deleted file mode 100644
index 96b51a051066..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1509.section.xml
+++ /dev/null
@@ -1,776 +0,0 @@
-
- Release 15.09 (<quote>Dingo</quote>, 2015/09/30)
-
- In addition to numerous new and upgraded packages, this release has
- the following highlights:
-
-
-
-
- The Haskell
- packages infrastructure has been re-designed from the ground up
- (Haskell NG). NixOS now distributes the latest
- version of every single package registered on
- Hackage --
- well in excess of 8,000 Haskell packages. Detailed instructions
- on how to use that infrastructure can be found in the
- User’s
- Guide to the Haskell Infrastructure. Users migrating from
- an earlier release may find helpful information below, in the
- list of backwards-incompatible changes. Furthermore, we
- distribute 51(!) additional Haskell package sets that provide
- every single LTS
- Haskell release since version 0.0 as well as the most
- recent Stackage
- Nightly snapshot. The announcement
- Full
- Stackage Support in Nixpkgs gives additional
- details.
-
-
-
-
- Nix has been updated to version 1.10, which among other
- improvements enables cryptographic signatures on binary caches
- for improved security.
-
-
-
-
- You can now keep your NixOS system up to date automatically by
- setting
-
-
-
-
-{
- system.autoUpgrade.enable = true;
-}
-
-
- This will cause the system to periodically check for updates in your
- current channel and run nixos-rebuild.
-
-
-
-
- This release is based on Glibc 2.21, GCC 4.9 and Linux 3.18.
-
-
-
-
- GNOME has been upgraded to 3.16.
-
-
-
-
- Xfce has been upgraded to 4.12.
-
-
-
-
- KDE 5 has been upgraded to KDE Frameworks 5.10, Plasma 5.3.2 and
- Applications 15.04.3. KDE 4 has been updated to kdelibs-4.14.10.
-
-
-
-
- E19 has been upgraded to 0.16.8.15.
-
-
-
-
- The following new services were added since the last release:
-
-
-
-
- services/mail/exim.nix
-
-
-
-
- services/misc/apache-kafka.nix
-
-
-
-
- services/misc/canto-daemon.nix
-
-
-
-
- services/misc/confd.nix
-
-
-
-
- services/misc/devmon.nix
-
-
-
-
- services/misc/gitit.nix
-
-
-
-
- services/misc/ihaskell.nix
-
-
-
-
- services/misc/mbpfan.nix
-
-
-
-
- services/misc/mediatomb.nix
-
-
-
-
- services/misc/mwlib.nix
-
-
-
-
- services/misc/parsoid.nix
-
-
-
-
- services/misc/plex.nix
-
-
-
-
- services/misc/ripple-rest.nix
-
-
-
-
- services/misc/ripple-data-api.nix
-
-
-
-
- services/misc/subsonic.nix
-
-
-
-
- services/misc/sundtek.nix
-
-
-
-
- services/monitoring/cadvisor.nix
-
-
-
-
- services/monitoring/das_watchdog.nix
-
-
-
-
- services/monitoring/grafana.nix
-
-
-
-
- services/monitoring/riemann-tools.nix
-
-
-
-
- services/monitoring/teamviewer.nix
-
-
-
-
- services/network-filesystems/u9fs.nix
-
-
-
-
- services/networking/aiccu.nix
-
-
-
-
- services/networking/asterisk.nix
-
-
-
-
- services/networking/bird.nix
-
-
-
-
- services/networking/charybdis.nix
-
-
-
-
- services/networking/docker-registry-server.nix
-
-
-
-
- services/networking/fan.nix
-
-
-
-
- services/networking/firefox/sync-server.nix
-
-
-
-
- services/networking/gateone.nix
-
-
-
-
- services/networking/heyefi.nix
-
-
-
-
- services/networking/i2p.nix
-
-
-
-
- services/networking/lambdabot.nix
-
-
-
-
- services/networking/mstpd.nix
-
-
-
-
- services/networking/nix-serve.nix
-
-
-
-
- services/networking/nylon.nix
-
-
-
-
- services/networking/racoon.nix
-
-
-
-
- services/networking/skydns.nix
-
-
-
-
- services/networking/shout.nix
-
-
-
-
- services/networking/softether.nix
-
-
-
-
- services/networking/sslh.nix
-
-
-
-
- services/networking/tinc.nix
-
-
-
-
- services/networking/tlsdated.nix
-
-
-
-
- services/networking/tox-bootstrapd.nix
-
-
-
-
- services/networking/tvheadend.nix
-
-
-
-
- services/networking/zerotierone.nix
-
-
-
-
- services/scheduling/marathon.nix
-
-
-
-
- services/security/fprintd.nix
-
-
-
-
- services/security/hologram.nix
-
-
-
-
- services/security/munge.nix
-
-
-
-
- services/system/cloud-init.nix
-
-
-
-
- services/web-servers/shellinabox.nix
-
-
-
-
- services/web-servers/uwsgi.nix
-
-
-
-
- services/x11/unclutter.nix
-
-
-
-
- services/x11/display-managers/sddm.nix
-
-
-
-
- system/boot/coredump.nix
-
-
-
-
- system/boot/loader/loader.nix
-
-
-
-
- system/boot/loader/generic-extlinux-compatible
-
-
-
-
- system/boot/networkd.nix
-
-
-
-
- system/boot/resolved.nix
-
-
-
-
- system/boot/timesyncd.nix
-
-
-
-
- tasks/filesystems/exfat.nix
-
-
-
-
- tasks/filesystems/ntfs.nix
-
-
-
-
- tasks/filesystems/vboxsf.nix
-
-
-
-
- virtualisation/virtualbox-host.nix
-
-
-
-
- virtualisation/vmware-guest.nix
-
-
-
-
- virtualisation/xen-dom0.nix
-
-
-
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- sshd no longer supports DSA and ECDSA host
- keys by default. If you have existing systems with such host
- keys and want to continue to use them, please set
-
-
-
-
-{
- system.stateVersion = "14.12";
-}
-
-
- The new option system.stateVersion ensures that
- certain configuration changes that could break existing systems
- (such as the sshd host key setting) will maintain
- compatibility with the specified NixOS release. NixOps sets the
- state version of existing deployments automatically.
-
-
-
-
- cron is no longer enabled by default, unless
- you have a non-empty
- services.cron.systemCronJobs. To force
- cron to be enabled, set
- services.cron.enable = true.
-
-
-
-
- Nix now requires binary caches to be cryptographically signed.
- If you have unsigned binary caches that you want to continue to
- use, you should set
- nix.requireSignedBinaryCaches = false.
-
-
-
-
- Steam now doesn’t need root rights to work. Instead of using
- *-steam-chrootenv, you should now just run
- steam. steamChrootEnv
- package was renamed to steam, and old
- steam package -- to
- steamOriginal.
-
-
-
-
- CMPlayer has been renamed to bomi upstream. Package
- cmplayer was accordingly renamed to
- bomi
-
-
-
-
- Atom Shell has been renamed to Electron upstream. Package
- atom-shell was accordingly renamed to
- electron
-
-
-
-
- Elm is not released on Hackage anymore. You should now use
- elmPackages.elm which contains the latest Elm
- platform.
-
-
-
-
- The CUPS printing service has been updated to version
- 2.0.2. Furthermore its systemd service has
- been renamed to cups.service.
-
-
- Local printers are no longer shared or advertised by default.
- This behavior can be changed by enabling
- services.printing.defaultShared or
- services.printing.browsing respectively.
-
-
-
-
- The VirtualBox host and guest options have been named more
- consistently. They can now found in
- virtualisation.virtualbox.host.* instead of
- services.virtualboxHost.* and
- virtualisation.virtualbox.guest.* instead of
- services.virtualboxGuest.*.
-
-
- Also, there now is support for the vboxsf
- file system using the fileSystems
- configuration attribute. An example of how this can be used in a
- configuration:
-
-
-
-
-{
- fileSystems."/shiny" = {
- device = "myshinysharedfolder";
- fsType = "vboxsf";
- };
-}
-
-
-
-
- nix-env -qa no longer
- discovers Haskell packages by name. The only packages visible in
- the global scope are ghc,
- cabal-install, and stack,
- but all other packages are hidden. The reason for this
- inconvenience is the sheer size of the Haskell package set.
- Name-based lookups are expensive, and most
- nix-env -qa operations would become much
- slower if we’d add the entire Hackage database into the top
- level attribute set. Instead, the list of Haskell packages can
- be displayed by running:
-
-
-
-
-nix-env -f "<nixpkgs>" -qaP -A haskellPackages
-
-
- Executable programs written in Haskell can be installed with:
-
-
-nix-env -f "<nixpkgs>" -iA haskellPackages.pandoc
-
-
- Installing Haskell libraries this way, however,
- is no longer supported. See the next item for more details.
-
-
-
-
- Previous versions of NixOS came with a feature called
- ghc-wrapper, a small script that allowed GHC
- to transparently pick up on libraries installed in the user’s
- profile. This feature has been deprecated;
- ghc-wrapper was removed from the
- distribution. The proper way to register Haskell libraries with
- the compiler now is the
- haskellPackages.ghcWithPackages function. The
- User’s
- Guide to the Haskell Infrastructure provides more
- information about this subject.
-
-
-
-
- All Haskell builds that have been generated with version 1.x of
- the cabal2nix utility are now invalid and
- need to be re-generated with a current version of
- cabal2nix to function. The most recent
- version of this tool can be installed by running
- nix-env -i cabal2nix.
-
-
-
-
- The haskellPackages set in Nixpkgs used to
- have a function attribute called extension
- that users could override in their
- ~/.nixpkgs/config.nix files to configure
- additional attributes, etc. That function still exists, but it’s
- now called overrides.
-
-
-
-
- The OpenBLAS library has been updated to version
- 0.2.14. Support for the
- x86_64-darwin platform was added. Dynamic
- architecture detection was enabled; OpenBLAS now selects
- microarchitecture-optimized routines at runtime, so optimal
- performance is achieved without the need to rebuild OpenBLAS
- locally. OpenBLAS has replaced ATLAS in most packages which use
- an optimized BLAS or LAPACK implementation.
-
-
-
-
- The phpfpm is now using the default PHP
- version (pkgs.php) instead of PHP 5.4
- (pkgs.php54).
-
-
-
-
- The locate service no longer indexes the Nix
- store by default, preventing packages with potentially numerous
- versions from cluttering the output. Indexing the store can be
- activated by setting
- services.locate.includeStore = true.
-
-
-
-
- The Nix expression search path (NIX_PATH) no
- longer contains /etc/nixos/nixpkgs by
- default. You can override NIX_PATH by setting
- nix.nixPath.
-
-
-
-
- Python 2.6 has been marked as broken (as it no longer receives
- security updates from upstream).
-
-
-
-
- Any use of module arguments such as pkgs to
- access library functions, or to define
- imports attributes will now lead to an
- infinite loop at the time of the evaluation.
-
-
- In case of an infinite loop, use the
- --show-trace command line argument and read
- the line just above the error message.
-
-
-$ nixos-rebuild build --show-trace
-…
-while evaluating the module argument `pkgs' in "/etc/nixos/my-module.nix":
-infinite recursion encountered
-
-
- Any use of pkgs.lib, should be replaced by
- lib, after adding it as argument of the
- module. The following module
-
-
-{ config, pkgs, ... }:
-
-with pkgs.lib;
-
-{
- options = {
- foo = mkOption { … };
- };
- config = mkIf config.foo { … };
-}
-
-
- should be modified to look like:
-
-
-{ config, pkgs, lib, ... }:
-
-with lib;
-
-{
- options = {
- foo = mkOption { option declaration };
- };
- config = mkIf config.foo { option definition };
-}
-
-
- When pkgs is used to download other projects
- to import their modules, and only in such cases, it should be
- replaced by (import <nixpkgs> {}). The
- following module
-
-
-{ config, pkgs, ... }:
-
-let
- myProject = pkgs.fetchurl {
- src = url;
- sha256 = hash;
- };
-in
-
-{
- imports = [ "${myProject}/module.nix" ];
-}
-
-
- should be modified to look like:
-
-
-{ config, pkgs, ... }:
-
-let
- myProject = (import <nixpkgs> {}).fetchurl {
- src = url;
- sha256 = hash;
- };
-in
-
-{
- imports = [ "${myProject}/module.nix" ];
-}
-
-
-
-
- Other notable improvements:
-
-
-
-
- The nixos and nixpkgs channels were unified, so one
- can use
- nix-env -iA nixos.bash instead of
- nix-env -iA nixos.pkgs.bash. See
- the
- commit for details.
-
-
-
-
- Users running an SSH server who worry about the quality of their
- /etc/ssh/moduli file with respect to the
- vulnerabilities
- discovered in the Diffie-Hellman key exchange can now
- replace OpenSSH’s default version with one they generated
- themselves using the new
- services.openssh.moduliFile option.
-
-
-
-
- A newly packaged TeX Live 2015 is provided in
- pkgs.texlive, split into 6500 nix packages.
- For basic user documentation see
- the
- source. Beware of
- an
- issue when installing a too large package set. The plan
- is to deprecate and maybe delete the original TeX packages until
- the next release.
-
-
-
-
- buildEnv.env on all Python interpreters is
- now available for nix-shell interoperability.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1603.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1603.section.xml
deleted file mode 100644
index 25b356e0aa6a..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1603.section.xml
+++ /dev/null
@@ -1,695 +0,0 @@
-
- Release 16.03 (<quote>Emu</quote>, 2016/03/31)
-
- In addition to numerous new and upgraded packages, this release has
- the following highlights:
-
-
-
-
- Systemd 229, bringing
- numerous
- improvements over 217.
-
-
-
-
- Linux 4.4 (was 3.18).
-
-
-
-
- GCC 5.3 (was 4.9). Note that GCC 5
- changes
- the C++ ABI in an incompatible way; this may cause
- problems if you try to link objects compiled with different
- versions of GCC.
-
-
-
-
- Glibc 2.23 (was 2.21).
-
-
-
-
- Binutils 2.26 (was 2.23.1). See #909
-
-
-
-
- Improved support for ensuring
- bitwise
- reproducible builds. For example,
- stdenv now sets the environment variable
- SOURCE_DATE_EPOCH to a deterministic value,
- and Nix has
- gained
- an option to repeat a build a number of times to test
- determinism. An ongoing project, the goal of exact
- reproducibility is to allow binaries to be verified
- independently (e.g., a user might only trust binaries that
- appear in three independent binary caches).
-
-
-
-
- Perl 5.22.
-
-
-
-
- The following new services were added since the last release:
-
-
-
-
- services/monitoring/longview.nix
-
-
-
-
- hardware/video/webcam/facetimehd.nix
-
-
-
-
- i18n/input-method/default.nix
-
-
-
-
- i18n/input-method/fcitx.nix
-
-
-
-
- i18n/input-method/ibus.nix
-
-
-
-
- i18n/input-method/nabi.nix
-
-
-
-
- i18n/input-method/uim.nix
-
-
-
-
- programs/fish.nix
-
-
-
-
- security/acme.nix
-
-
-
-
- security/audit.nix
-
-
-
-
- security/oath.nix
-
-
-
-
- services/hardware/irqbalance.nix
-
-
-
-
- services/mail/dspam.nix
-
-
-
-
- services/mail/opendkim.nix
-
-
-
-
- services/mail/postsrsd.nix
-
-
-
-
- services/mail/rspamd.nix
-
-
-
-
- services/mail/rmilter.nix
-
-
-
-
- services/misc/autofs.nix
-
-
-
-
- services/misc/bepasty.nix
-
-
-
-
- services/misc/calibre-server.nix
-
-
-
-
- services/misc/cfdyndns.nix
-
-
-
-
- services/misc/gammu-smsd.nix
-
-
-
-
- services/misc/mathics.nix
-
-
-
-
- services/misc/matrix-synapse.nix
-
-
-
-
- services/misc/octoprint.nix
-
-
-
-
- services/monitoring/hdaps.nix
-
-
-
-
- services/monitoring/heapster.nix
-
-
-
-
- services/monitoring/longview.nix
-
-
-
-
- services/network-filesystems/netatalk.nix
-
-
-
-
- services/network-filesystems/xtreemfs.nix
-
-
-
-
- services/networking/autossh.nix
-
-
-
-
- services/networking/dnschain.nix
-
-
-
-
- services/networking/gale.nix
-
-
-
-
- services/networking/miniupnpd.nix
-
-
-
-
- services/networking/namecoind.nix
-
-
-
-
- services/networking/ostinato.nix
-
-
-
-
- services/networking/pdnsd.nix
-
-
-
-
- services/networking/shairport-sync.nix
-
-
-
-
- services/networking/supplicant.nix
-
-
-
-
- services/search/kibana.nix
-
-
-
-
- services/security/haka.nix
-
-
-
-
- services/security/physlock.nix
-
-
-
-
- services/web-apps/pump.io.nix
-
-
-
-
- services/x11/hardware/libinput.nix
-
-
-
-
- services/x11/window-managers/windowlab.nix
-
-
-
-
- system/boot/initrd-network.nix
-
-
-
-
- system/boot/initrd-ssh.nix
-
-
-
-
- system/boot/loader/loader.nix
-
-
-
-
- system/boot/networkd.nix
-
-
-
-
- system/boot/resolved.nix
-
-
-
-
- virtualisation/lxd.nix
-
-
-
-
- virtualisation/rkt.nix
-
-
-
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- We no longer produce graphical ISO images and VirtualBox images
- for i686-linux. A minimal ISO image is still
- provided.
-
-
-
-
- Firefox and similar browsers are now wrapped by
- default. The package and attribute names are plain
- firefox or midori, etc.
- Backward-compatibility attributes were set up, but note that
- nix-env -u will not
- update your current firefox-with-plugins; you
- have to uninstall it and install firefox
- instead.
-
-
-
-
- wmiiSnap has been replaced with
- wmii_hg, but
- services.xserver.windowManager.wmii.enable
- has been updated respectively so this only affects you if you
- have explicitly installed wmiiSnap.
-
-
-
-
- jobs NixOS option has been removed. It served
- as compatibility layer between Upstart jobs and SystemD
- services. All services have been rewritten to use
- systemd.services
-
-
-
-
- wmiimenu is removed, as it has been removed
- by the developers upstream. Use wimenu from
- the wmii-hg package.
-
-
-
-
- Gitit is no longer automatically added to the module list in
- NixOS and as such there will not be any manual entries for it.
- You will need to add an import statement to your NixOS
- configuration in order to use it, e.g.
-
-
-{
- imports = [ <nixpkgs/nixos/modules/services/misc/gitit.nix> ];
-}
-
-
- will include the Gitit service configuration options.
-
-
-
-
- nginx does not accept flags for enabling and
- disabling modules anymore. Instead it accepts
- modules argument, which is a list of modules
- to be built in. All modules now reside in
- nginxModules set. Example configuration:
-
-
-nginx.override {
- modules = [ nginxModules.rtmp nginxModules.dav nginxModules.moreheaders ];
-}
-
-
-
-
- s3sync is removed, as it hasn’t been
- developed by upstream for 4 years and only runs with ruby 1.8.
- For an actively-developer alternative look at
- tarsnap and others.
-
-
-
-
- ruby_1_8 has been removed as it’s not
- supported from upstream anymore and probably contains security
- issues.
-
-
-
-
- tidy-html5 package is removed. Upstream only
- provided (lib)tidy5 during development, and
- now they went back to (lib)tidy to work as a
- drop-in replacement of the original package that has been
- unmaintained for years. You can (still) use the
- html-tidy package, which got updated to a
- stable release from this new upstream.
-
-
-
-
- extraDeviceOptions argument is removed from
- bumblebee package. Instead there are now two
- separate arguments: extraNvidiaDeviceOptions
- and extraNouveauDeviceOptions for setting
- extra X11 options for nvidia and nouveau drivers, respectively.
-
-
-
-
- The Ctrl+Alt+Backspace key combination no
- longer kills the X server by default. There’s a new option
- services.xserver.enableCtrlAltBackspace
- allowing to enable the combination again.
-
-
-
-
- emacsPackagesNg now contains all packages
- from the ELPA, MELPA, and MELPA Stable repositories.
-
-
-
-
- Data directory for Postfix MTA server is moved from
- /var/postfix to
- /var/lib/postfix. Old configurations are
- migrated automatically. service.postfix
- module has also received many improvements, such as correct
- directories’ access rights, new aliasFiles
- and mapFiles options and more.
-
-
-
-
- Filesystem options should now be configured as a list of
- strings, not a comma-separated string. The old style will
- continue to work, but print a warning, until the 16.09 release.
- An example of the new style:
-
-
-{
- fileSystems."/example" = {
- device = "/dev/sdc";
- fsType = "btrfs";
- options = [ "noatime" "compress=lzo" "space_cache" "autodefrag" ];
- };
-}
-
-
-
-
- CUPS, installed by services.printing module,
- now has its data directory in /var/lib/cups.
- Old configurations from /etc/cups are moved
- there automatically, but there might be problems. Also
- configuration options
- services.printing.cupsdConf and
- services.printing.cupsdFilesConf were removed
- because they had been allowing one to override configuration
- variables required for CUPS to work at all on NixOS. For most
- use cases, services.printing.extraConf and
- new option services.printing.extraFilesConf
- should be enough; if you encounter a situation when they are
- not, please file a bug.
-
-
- There are also Gutenprint improvements; in particular, a new
- option services.printing.gutenprint is added
- to enable automatic updating of Gutenprint PPMs; it’s greatly
- recommended to enable it instead of adding
- gutenprint to the drivers
- list.
-
-
-
-
- services.xserver.vaapiDrivers has been
- removed. Use
- hardware.opengl.extraPackages{,32} instead.
- You can also specify VDPAU drivers there.
-
-
-
-
- programs.ibus moved to
- i18n.inputMethod.ibus. The option
- programs.ibus.plugins changed to
- i18n.inputMethod.ibus.engines and the option
- to enable ibus changed from
- programs.ibus.enable to
- i18n.inputMethod.enabled.
- i18n.inputMethod.enabled should be set to the
- used input method name, "ibus" for
- ibus. An example of the new style:
-
-
-{
- i18n.inputMethod.enabled = "ibus";
- i18n.inputMethod.ibus.engines = with pkgs.ibus-engines; [ anthy mozc ];
-}
-
-
- That is equivalent to the old version:
-
-
-{
- programs.ibus.enable = true;
- programs.ibus.plugins = with pkgs; [ ibus-anthy mozc ];
-}
-
-
-
-
- services.udev.extraRules option now writes
- rules to 99-local.rules instead of
- 10-local.rules. This makes all the user rules
- apply after others, so their results wouldn’t be overridden by
- anything else.
-
-
-
-
- Large parts of the services.gitlab module has
- been been rewritten. There are new configuration options
- available. The stateDir option was renamned
- to statePath and the
- satellitesDir option was removed. Please
- review the currently available options.
-
-
-
-
- The option
- services.nsd.zones.<name>.data no
- longer interpret the dollar sign ($) as a shell variable, as
- such it should not be escaped anymore. Thus the following zone
- data:
-
-
-$ORIGIN example.com.
-$TTL 1800
-@ IN SOA ns1.vpn.nbp.name. admin.example.com. (
-
-
- Should modified to look like the actual file expected by nsd:
-
-
-$ORIGIN example.com.
-$TTL 1800
-@ IN SOA ns1.vpn.nbp.name. admin.example.com. (
-
-
-
-
- service.syncthing.dataDir options now has to
- point to exact folder where syncthing is writing to. Example
- configuration should look something like:
-
-
-{
- services.syncthing = {
- enable = true;
- dataDir = "/home/somebody/.syncthing";
- user = "somebody";
- };
-}
-
-
-
-
- networking.firewall.allowPing is now enabled
- by default. Users are encouraged to configure an appropriate
- rate limit for their machines using the Kernel interface at
- /proc/sys/net/ipv4/icmp_ratelimit and
- /proc/sys/net/ipv6/icmp/ratelimit or using
- the firewall itself, i.e. by setting the NixOS option
- networking.firewall.pingLimit.
-
-
-
-
- Systems with some broadcom cards used to result into a generated
- config that is no longer accepted. If you get errors like
-
-
-error: path ‘/nix/store/*-broadcom-sta-*’ does not exist and cannot be created
-
-
- you should either re-run
- nixos-generate-config or manually replace
- "${config.boot.kernelPackages.broadcom_sta}"
- by config.boot.kernelPackages.broadcom_sta in
- your /etc/nixos/hardware-configuration.nix.
- More discussion is on
-
- the github issue.
-
-
-
-
- The services.xserver.startGnuPGAgent option
- has been removed. GnuPG 2.1.x changed the way the gpg-agent
- works, and that new approach no longer requires (or even
- supports) the start everything as a child of the
- agent scheme we’ve implemented in NixOS for older
- versions. To configure the gpg-agent for your X session, add the
- following code to ~/.bashrc or some file
- that’s sourced when your shell is started:
-
-
-GPG_TTY=$(tty)
-export GPG_TTY
-
-
- If you want to use gpg-agent for SSH, too, add the following to
- your session initialization (e.g.
- displayManager.sessionCommands)
-
-
- gpg-connect-agent /bye
- unset SSH_AGENT_PID
- export SSH_AUTH_SOCK="''${HOME}/.gnupg/S.gpg-agent.ssh"
-
-
- and make sure that
-
-
- enable-ssh-support
-
-
- is included in your ~/.gnupg/gpg-agent.conf.
- You will need to use ssh-add to re-add your
- ssh keys. If gpg’s automatic transformation of the private keys
- to the new format fails, you will need to re-import your private
- keyring as well:
-
-
- gpg --import ~/.gnupg/secring.gpg
-
-
- The gpg-agent(1) man page has more details
- about this subject, i.e. in the EXAMPLES section.
-
-
-
-
- Other notable improvements:
-
-
-
-
- ejabberd module is brought back and now works
- on NixOS.
-
-
-
-
- Input method support was improved. New NixOS modules (fcitx,
- nabi and uim), fcitx engines (chewing, hangul, m17n, mozc and
- table-other) and ibus engines (hangul and m17n) have been added.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1609.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1609.section.xml
deleted file mode 100644
index c2adbc88f5ca..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1609.section.xml
+++ /dev/null
@@ -1,273 +0,0 @@
-
- Release 16.09 (<quote>Flounder</quote>, 2016/09/30)
-
- In addition to numerous new and upgraded packages, this release has
- the following highlights:
-
-
-
-
- Many NixOS configurations and Nix packages now use significantly
- less disk space, thanks to the
- extensive
- work on closure size reduction. For example, the closure
- size of a minimal NixOS container went down from ~424 MiB in
- 16.03 to ~212 MiB in 16.09, while the closure size of Firefox
- went from ~651 MiB to ~259 MiB.
-
-
-
-
- To improve security, packages are now
- built
- using various hardening features. See the Nixpkgs manual
- for more information.
-
-
-
-
- Support for PXE netboot. See
- for documentation.
-
-
-
-
- X.org server 1.18. If you use the ati_unfree
- driver, 1.17 is still used due to an ABI incompatibility.
-
-
-
-
- This release is based on Glibc 2.24, GCC 5.4.0 and systemd 231.
- The default Linux kernel remains 4.4.
-
-
-
-
- The following new services were added since the last release:
-
-
-
-
- (this will get automatically generated at release time)
-
-
-
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- A large number of packages have been converted to use the
- multiple outputs feature of Nix to greatly reduce the amount of
- required disk space, as mentioned above. This may require
- changes to any custom packages to make them build again; see the
- relevant chapter in the Nixpkgs manual for more information.
- (Additional caveat to packagers: some packaging conventions
- related to multiple-output packages
- were
- changed late (August 2016) in the release cycle and
- differ from the initial introduction of multiple outputs.)
-
-
-
-
- Previous versions of Nixpkgs had support for all versions of the
- LTS Haskell package set. That support has been dropped. The
- previously provided haskell.packages.lts-x_y
- package sets still exist in name to aviod breaking user code,
- but these package sets don’t actually contain the versions
- mandated by the corresponding LTS release. Instead, our package
- set it loosely based on the latest available LTS release, i.e.
- LTS 7.x at the time of this writing. New releases of NixOS and
- Nixpkgs will drop those old names entirely.
- The
- motivation for this change has been discussed at length
- on the nix-dev mailing list and in
- Github
- issue #14897. Development strategies for Haskell hackers
- who want to rely on Nix and NixOS have been described in
- another
- nix-dev article.
-
-
-
-
- Shell aliases for systemd sub-commands
- were
- dropped: start,
- stop, restart,
- status.
-
-
-
-
- Redis now binds to 127.0.0.1 only instead of listening to all
- network interfaces. This is the default behavior of Redis 3.2
-
-
-
-
- /var/empty is now immutable. Activation
- script runs chattr +i to forbid any
- modifications inside the folder. See
-
- the pull request for what bugs this caused.
-
-
-
-
- Gitlab’s maintainance script gitlab-runner
- was removed and split up into the more clearer
- gitlab-run and gitlab-rake
- scripts, because gitlab-runner is a component
- of Gitlab CI.
-
-
-
-
- services.xserver.libinput.accelProfile
- default changed from flat to
- adaptive, as per
-
- official documentation.
-
-
-
-
- fonts.fontconfig.ultimate.rendering was
- removed because our presets were obsolete for some time. New
- presets are hardcoded into FreeType; you can select a preset via
- fonts.fontconfig.ultimate.preset. You can
- customize those presets via ordinary environment variables,
- using environment.variables.
-
-
-
-
- The audit service is no longer enabled by
- default. Use security.audit.enable = true to
- explicitly enable it.
-
-
-
-
- pkgs.linuxPackages.virtualbox now contains
- only the kernel modules instead of the VirtualBox user space
- binaries. If you want to reference the user space binaries, you
- have to use the new pkgs.virtualbox instead.
-
-
-
-
- goPackages was replaced with separated Go
- applications in appropriate nixpkgs
- categories. Each Go package uses its own dependency set. There’s
- also a new go2nix tool introduced to generate
- a Go package definition from its Go source automatically.
-
-
-
-
- services.mongodb.extraConfig configuration
- format was changed to YAML.
-
-
-
-
- PHP has been upgraded to 7.0
-
-
-
-
- Other notable improvements:
-
-
-
-
- Revamped grsecurity/PaX support. There is now only a single
- general-purpose distribution kernel and the configuration
- interface has been streamlined. Desktop users should be able to
- simply set
-
-
-{
- security.grsecurity.enable = true;
-}
-
-
- to get a reasonably secure system without having to sacrifice
- too much functionality.
-
-
-
-
- Special filesystems, like /proc,
- /run and others, now have the same mount
- options as recommended by systemd and are unified across
- different places in NixOS. Mount options are updated during
- nixos-rebuild switch if possible. One benefit
- from this is improved security — most such filesystems are now
- mounted with noexec, nodev
- and/or nosuid options.
-
-
-
-
- The reverse path filter was interfering with DHCPv4 server
- operation in the past. An exception for DHCPv4 and a new option
- to log packets that were dropped due to the reverse path filter
- was added
- (networking.firewall.logReversePathDrops) for
- easier debugging.
-
-
-
-
- Containers configuration within
- containers.<name>.config is
- now
- properly typed and checked. In particular, partial
- configurations are merged correctly.
-
-
-
-
- The directory container setuid wrapper programs,
- /var/setuid-wrappers,
- is
- now updated atomically to prevent failures if the switch to a
- new configuration is interrupted.
-
-
-
-
- services.xserver.startGnuPGAgent has been
- removed due to GnuPG 2.1.x bump. See
-
- how to achieve similar behavior. You might need to
- pkill gpg-agent after the upgrade to prevent
- a stale agent being in the way.
-
-
-
-
-
- Declarative users could share the uid due to the bug in the
- script handling conflict resolution.
-
-
-
-
- Gummi boot has been replaced using systemd-boot.
-
-
-
-
- Hydra package and NixOS module were added for convenience.
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1703.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1703.section.xml
deleted file mode 100644
index 8667063f37e0..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1703.section.xml
+++ /dev/null
@@ -1,818 +0,0 @@
-
- Release 17.03 (<quote>Gorilla</quote>, 2017/03/31)
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- Nixpkgs is now extensible through overlays. See the
- Nixpkgs
- manual for more information.
-
-
-
-
- This release is based on Glibc 2.25, GCC 5.4.0 and systemd
- 232. The default Linux kernel is 4.9 and Nix is at 1.11.8.
-
-
-
-
- The default desktop environment now is KDE’s Plasma 5. KDE 4
- has been removed
-
-
-
-
- The setuid wrapper functionality now supports setting
- capabilities.
-
-
-
-
- X.org server uses branch 1.19. Due to ABI incompatibilities,
- ati_unfree keeps forcing 1.17 and
- amdgpu-pro starts forcing 1.18.
-
-
-
-
- Cross compilation has been rewritten. See the nixpkgs manual
- for details. The most obvious breaking change is that in
- derivations there is no .nativeDrv nor
- .crossDrv are now cross by default, not
- native.
-
-
-
-
- The overridePackages function has been
- rewritten to be replaced by
-
- overlays
-
-
-
-
- Packages in nixpkgs can be marked as insecure through listed
- vulnerabilities. See the
- Nixpkgs
- manual for more information.
-
-
-
-
- PHP now defaults to PHP 7.1
-
-
-
-
-
- New Services
-
- The following new services were added since the last release:
-
-
-
-
- hardware/ckb.nix
-
-
-
-
- hardware/mcelog.nix
-
-
-
-
- hardware/usb-wwan.nix
-
-
-
-
- hardware/video/capture/mwprocapture.nix
-
-
-
-
- programs/adb.nix
-
-
-
-
- programs/chromium.nix
-
-
-
-
- programs/gphoto2.nix
-
-
-
-
- programs/java.nix
-
-
-
-
- programs/mtr.nix
-
-
-
-
- programs/oblogout.nix
-
-
-
-
- programs/vim.nix
-
-
-
-
- programs/wireshark.nix
-
-
-
-
- security/dhparams.nix
-
-
-
-
- services/audio/ympd.nix
-
-
-
-
- services/computing/boinc/client.nix
-
-
-
-
- services/continuous-integration/buildbot/master.nix
-
-
-
-
- services/continuous-integration/buildbot/worker.nix
-
-
-
-
- services/continuous-integration/gitlab-runner.nix
-
-
-
-
- services/databases/riak-cs.nix
-
-
-
-
- services/databases/stanchion.nix
-
-
-
-
- services/desktops/gnome3/gnome-terminal-server.nix
-
-
-
-
- services/editors/infinoted.nix
-
-
-
-
- services/hardware/illum.nix
-
-
-
-
- services/hardware/trezord.nix
-
-
-
-
- services/logging/journalbeat.nix
-
-
-
-
- services/mail/offlineimap.nix
-
-
-
-
- services/mail/postgrey.nix
-
-
-
-
- services/misc/couchpotato.nix
-
-
-
-
- services/misc/docker-registry.nix
-
-
-
-
- services/misc/errbot.nix
-
-
-
-
- services/misc/geoip-updater.nix
-
-
-
-
- services/misc/gogs.nix
-
-
-
-
- services/misc/leaps.nix
-
-
-
-
- services/misc/nix-optimise.nix
-
-
-
-
- services/misc/ssm-agent.nix
-
-
-
-
- services/misc/sssd.nix
-
-
-
-
- services/monitoring/arbtt.nix
-
-
-
-
- services/monitoring/netdata.nix
-
-
-
-
- services/monitoring/prometheus/default.nix
-
-
-
-
- services/monitoring/prometheus/alertmanager.nix
-
-
-
-
- services/monitoring/prometheus/blackbox-exporter.nix
-
-
-
-
- services/monitoring/prometheus/json-exporter.nix
-
-
-
-
- services/monitoring/prometheus/nginx-exporter.nix
-
-
-
-
- services/monitoring/prometheus/node-exporter.nix
-
-
-
-
- services/monitoring/prometheus/snmp-exporter.nix
-
-
-
-
- services/monitoring/prometheus/unifi-exporter.nix
-
-
-
-
- services/monitoring/prometheus/varnish-exporter.nix
-
-
-
-
- services/monitoring/sysstat.nix
-
-
-
-
- services/monitoring/telegraf.nix
-
-
-
-
- services/monitoring/vnstat.nix
-
-
-
-
- services/network-filesystems/cachefilesd.nix
-
-
-
-
- services/network-filesystems/glusterfs.nix
-
-
-
-
- services/network-filesystems/ipfs.nix
-
-
-
-
- services/networking/dante.nix
-
-
-
-
- services/networking/dnscrypt-wrapper.nix
-
-
-
-
- services/networking/fakeroute.nix
-
-
-
-
- services/networking/flannel.nix
-
-
-
-
- services/networking/htpdate.nix
-
-
-
-
- services/networking/miredo.nix
-
-
-
-
- services/networking/nftables.nix
-
-
-
-
- services/networking/powerdns.nix
-
-
-
-
- services/networking/pdns-recursor.nix
-
-
-
-
- services/networking/quagga.nix
-
-
-
-
- services/networking/redsocks.nix
-
-
-
-
- services/networking/wireguard.nix
-
-
-
-
- services/system/cgmanager.nix
-
-
-
-
- services/torrent/opentracker.nix
-
-
-
-
- services/web-apps/atlassian/confluence.nix
-
-
-
-
- services/web-apps/atlassian/crowd.nix
-
-
-
-
- services/web-apps/atlassian/jira.nix
-
-
-
-
- services/web-apps/frab.nix
-
-
-
-
- services/web-apps/nixbot.nix
-
-
-
-
- services/web-apps/selfoss.nix
-
-
-
-
- services/web-apps/quassel-webserver.nix
-
-
-
-
- services/x11/unclutter-xfixes.nix
-
-
-
-
- services/x11/urxvtd.nix
-
-
-
-
- system/boot/systemd-nspawn.nix
-
-
-
-
- virtualisation/ecs-agent.nix
-
-
-
-
- virtualisation/lxcfs.nix
-
-
-
-
- virtualisation/openstack/keystone.nix
-
-
-
-
- virtualisation/openstack/glance.nix
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- Derivations have no .nativeDrv nor
- .crossDrv and are now cross by default, not
- native.
-
-
-
-
- stdenv.overrides is now expected to take
- self and super
- arguments. See lib.trivial.extends for what
- those parameters represent.
-
-
-
-
- ansible now defaults to ansible version 2
- as version 1 has been removed due to a serious
-
- vulnerability unpatched by upstream.
-
-
-
-
- gnome alias has been removed along with
- gtk, gtkmm and several
- others. Now you need to use versioned attributes, like
- gnome3.
-
-
-
-
- The attribute name of the Radicale daemon has been changed
- from pythonPackages.radicale to
- radicale.
-
-
-
-
- The stripHash bash function in
- stdenv changed according to its
- documentation; it now outputs the stripped name to
- stdout instead of putting it in the
- variable strippedName.
-
-
-
-
- PHP now scans for extra configuration .ini files in /etc/php.d
- instead of /etc. This prevents accidentally loading non-PHP
- .ini files that may be in /etc.
-
-
-
-
- Two lone top-level dict dbs moved into
- dictdDBs. This affects:
- dictdWordnet which is now at
- dictdDBs.wordnet and
- dictdWiktionary which is now at
- dictdDBs.wiktionary
-
-
-
-
- Parsoid service now uses YAML configuration format.
- service.parsoid.interwikis is now called
- service.parsoid.wikis and is a list of
- either API URLs or attribute sets as specified in parsoid’s
- documentation.
-
-
-
-
- Ntpd was replaced by
- systemd-timesyncd as the default service to
- synchronize system time with a remote NTP server. The old
- behavior can be restored by setting
- services.ntp.enable to
- true. Upstream time servers for all NTP
- implementations are now configured using
- networking.timeServers.
-
-
-
-
- service.nylon is now declared using named
- instances. As an example:
-
-
-{
- services.nylon = {
- enable = true;
- acceptInterface = "br0";
- bindInterface = "tun1";
- port = 5912;
- };
-}
-
-
- should be replaced with:
-
-
-{
- services.nylon.myvpn = {
- enable = true;
- acceptInterface = "br0";
- bindInterface = "tun1";
- port = 5912;
- };
-}
-
-
- this enables you to declare a SOCKS proxy for each uplink.
-
-
-
-
- overridePackages function no longer exists.
- It is replaced by
-
- overlays. For example, the following code:
-
-
-let
- pkgs = import <nixpkgs> {};
-in
- pkgs.overridePackages (self: super: ...)
-
-
- should be replaced by:
-
-
-let
- pkgs = import <nixpkgs> {};
-in
- import pkgs.path { overlays = [(self: super: ...)]; }
-
-
-
-
- Autoloading connection tracking helpers is now disabled by
- default. This default was also changed in the Linux kernel and
- is considered insecure if not configured properly in your
- firewall. If you need connection tracking helpers (i.e. for
- active FTP) please enable
- networking.firewall.autoLoadConntrackHelpers
- and tune
- networking.firewall.connectionTrackingModules
- to suit your needs.
-
-
-
-
- local_recipient_maps is not set to empty
- value by Postfix service. It’s an insecure default as stated
- by Postfix documentation. Those who want to retain this
- setting need to set it via
- services.postfix.extraConfig.
-
-
-
-
- Iputils no longer provide ping6 and traceroute6. The
- functionality of these tools has been integrated into ping and
- traceroute respectively. To enforce an address family the new
- flags -4 and -6 have
- been added. One notable incompatibility is that specifying an
- interface (for link-local IPv6 for instance) is no longer done
- with the -I flag, but by encoding the
- interface into the address
- (ping fe80::1%eth0).
-
-
-
-
- The socket handling of the services.rmilter
- module has been fixed and refactored. As rmilter doesn’t
- support binding to more than one socket, the options
- bindUnixSockets and
- bindInetSockets have been replaced by
- services.rmilter.bindSocket.*. The default
- is still a unix socket in
- /run/rmilter/rmilter.sock. Refer to the
- options documentation for more information.
-
-
-
-
- The fetch* functions no longer support md5,
- please use sha256 instead.
-
-
-
-
- The dnscrypt-proxy module interface has been streamlined
- around the extraArgs option. Where
- possible, legacy option declarations are mapped to
- extraArgs but will emit warnings. The
- resolverList has been outright removed: to
- use an unlisted resolver, use the
- customResolver option.
-
-
-
-
- torbrowser now stores local state under
- ~/.local/share/tor-browser by default. Any
- browser profile data from the old location,
- ~/.torbrowser4, must be migrated manually.
-
-
-
-
- The ihaskell, monetdb, offlineimap and sitecopy services have
- been removed.
-
-
-
-
-
- Other Notable Changes
-
-
-
- Module type system have a new extensible option types feature
- that allow to extend certain types, such as enum, through
- multiple option declarations of the same option across
- multiple modules.
-
-
-
-
- jre now defaults to GTK UI by default. This
- improves visual consistency and makes Java follow system font
- style, improving the situation on HighDPI displays. This has a
- cost of increased closure size; for server and other headless
- workloads it’s recommended to use
- jre_headless.
-
-
-
-
- Python 2.6 interpreter and package set have been removed.
-
-
-
-
- The Python 2.7 interpreter does not use modules anymore.
- Instead, all CPython interpreters now include the whole
- standard library except for `tkinter`, which is available in
- the Python package set.
-
-
-
-
- Python 2.7, 3.5 and 3.6 are now built deterministically and
- 3.4 mostly. Minor modifications had to be made to the
- interpreters in order to generate deterministic bytecode. This
- has security implications and is relevant for those using
- Python in a nix-shell. See the Nixpkgs
- manual for details.
-
-
-
-
- The Python package sets now use a fixed-point combinator and
- the sets are available as attributes of the interpreters.
-
-
-
-
- The Python function buildPythonPackage has
- been improved and can be used to build from Setuptools source,
- Flit source, and precompiled Wheels.
-
-
-
-
- When adding new or updating current Python libraries, the
- expressions should be put in separate files in
- pkgs/development/python-modules and called
- from python-packages.nix.
-
-
-
-
- The dnscrypt-proxy service supports synchronizing the list of
- public resolvers without working DNS resolution. This fixes
- issues caused by the resolver list becoming outdated. It also
- improves the viability of DNSCrypt only configurations.
-
-
-
-
- Containers using bridged networking no longer lose their
- connection after changes to the host networking.
-
-
-
-
- ZFS supports pool auto scrubbing.
-
-
-
-
- The bind DNS utilities (e.g. dig) have been split into their
- own output and are now also available in
- pkgs.dnsutils and it is no longer necessary
- to pull in all of bind to use them.
-
-
-
-
- Per-user configuration was moved from
- ~/.nixpkgs to
- ~/.config/nixpkgs. The former is still
- valid for config.nix for backwards
- compatibility.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1709.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1709.section.xml
deleted file mode 100644
index 849ec868c783..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1709.section.xml
+++ /dev/null
@@ -1,922 +0,0 @@
-
- Release 17.09 (<quote>Hummingbird</quote>, 2017/09/??)
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- The GNOME version is now 3.24. KDE Plasma was upgraded to
- 5.10, KDE Applications to 17.08.1 and KDE Frameworks to 5.37.
-
-
-
-
- The user handling now keeps track of deallocated UIDs/GIDs.
- When a user or group is revived, this allows it to be
- allocated the UID/GID it had before. A consequence is that
- UIDs and GIDs are no longer reused.
-
-
-
-
- The module option
- services.xserver.xrandrHeads now causes the
- first head specified in this list to be set as the primary
- head. Apart from that, it’s now possible to also set
- additional options by using an attribute set, for example:
-
-
-{ services.xserver.xrandrHeads = [
- "HDMI-0"
- {
- output = "DVI-0";
- primary = true;
- monitorConfig = ''
- Option "Rotate" "right"
- '';
- }
- ];
-}
-
-
- This will set the DVI-0 output to be the
- primary head, even though HDMI-0 is the
- first head in the list.
-
-
-
-
- The handling of SSL in the services.nginx
- module has been cleaned up, renaming the misnamed
- enableSSL to onlySSL
- which reflects its original intention. This is not to be used
- with the already existing forceSSL which
- creates a second non-SSL virtual host redirecting to the SSL
- virtual host. This by chance had worked earlier due to
- specific implementation details. In case you had specified
- both please remove the enableSSL option to
- keep the previous behaviour.
-
-
- Another addSSL option has been introduced
- to configure both a non-SSL virtual host and an SSL virtual
- host with the same configuration.
-
-
- Options to configure resolver options and
- upstream blocks have been introduced. See
- their information for further details.
-
-
- The port option has been replaced by a more
- generic listen option which makes it
- possible to specify multiple addresses, ports and SSL configs
- dependant on the new SSL handling mentioned above.
-
-
-
-
-
- New Services
-
- The following new services were added since the last release:
-
-
-
-
- config/fonts/fontconfig-penultimate.nix
-
-
-
-
- config/fonts/fontconfig-ultimate.nix
-
-
-
-
- config/terminfo.nix
-
-
-
-
- hardware/sensor/iio.nix
-
-
-
-
- hardware/nitrokey.nix
-
-
-
-
- hardware/raid/hpsa.nix
-
-
-
-
- programs/browserpass.nix
-
-
-
-
- programs/gnupg.nix
-
-
-
-
- programs/qt5ct.nix
-
-
-
-
- programs/slock.nix
-
-
-
-
- programs/thefuck.nix
-
-
-
-
- security/auditd.nix
-
-
-
-
- security/lock-kernel-modules.nix
-
-
-
-
- service-managers/docker.nix
-
-
-
-
- service-managers/trivial.nix
-
-
-
-
- services/admin/salt/master.nix
-
-
-
-
- services/admin/salt/minion.nix
-
-
-
-
- services/audio/slimserver.nix
-
-
-
-
- services/cluster/kubernetes/default.nix
-
-
-
-
- services/cluster/kubernetes/dns.nix
-
-
-
-
- services/cluster/kubernetes/dashboard.nix
-
-
-
-
- services/continuous-integration/hail.nix
-
-
-
-
- services/databases/clickhouse.nix
-
-
-
-
- services/databases/postage.nix
-
-
-
-
- services/desktops/gnome3/gnome-disks.nix
-
-
-
-
- services/desktops/gnome3/gpaste.nix
-
-
-
-
- services/logging/SystemdJournal2Gelf.nix
-
-
-
-
- services/logging/heartbeat.nix
-
-
-
-
- services/logging/journalwatch.nix
-
-
-
-
- services/logging/syslogd.nix
-
-
-
-
- services/mail/mailhog.nix
-
-
-
-
- services/mail/nullmailer.nix
-
-
-
-
- services/misc/airsonic.nix
-
-
-
-
- services/misc/autorandr.nix
-
-
-
-
- services/misc/exhibitor.nix
-
-
-
-
- services/misc/fstrim.nix
-
-
-
-
- services/misc/gollum.nix
-
-
-
-
- services/misc/irkerd.nix
-
-
-
-
- services/misc/jackett.nix
-
-
-
-
- services/misc/radarr.nix
-
-
-
-
- services/misc/snapper.nix
-
-
-
-
- services/monitoring/osquery.nix
-
-
-
-
- services/monitoring/prometheus/collectd-exporter.nix
-
-
-
-
- services/monitoring/prometheus/fritzbox-exporter.nix
-
-
-
-
- services/network-filesystems/kbfs.nix
-
-
-
-
- services/networking/dnscache.nix
-
-
-
-
- services/networking/fireqos.nix
-
-
-
-
- services/networking/iwd.nix
-
-
-
-
- services/networking/keepalived/default.nix
-
-
-
-
- services/networking/keybase.nix
-
-
-
-
- services/networking/lldpd.nix
-
-
-
-
- services/networking/matterbridge.nix
-
-
-
-
- services/networking/squid.nix
-
-
-
-
- services/networking/tinydns.nix
-
-
-
-
- services/networking/xrdp.nix
-
-
-
-
- services/security/shibboleth-sp.nix
-
-
-
-
- services/security/sks.nix
-
-
-
-
- services/security/sshguard.nix
-
-
-
-
- services/security/torify.nix
-
-
-
-
- services/security/usbguard.nix
-
-
-
-
- services/security/vault.nix
-
-
-
-
- services/system/earlyoom.nix
-
-
-
-
- services/system/saslauthd.nix
-
-
-
-
- services/web-apps/nexus.nix
-
-
-
-
- services/web-apps/pgpkeyserver-lite.nix
-
-
-
-
- services/web-apps/piwik.nix
-
-
-
-
- services/web-servers/lighttpd/collectd.nix
-
-
-
-
- services/web-servers/minio.nix
-
-
-
-
- services/x11/display-managers/xpra.nix
-
-
-
-
- services/x11/xautolock.nix
-
-
-
-
- tasks/filesystems/bcachefs.nix
-
-
-
-
- tasks/powertop.nix
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- In an Qemu-based virtualization
- environment, the network interface names changed from i.e.
- enp0s3 to
- ens3.
-
-
- This is due to a kernel configuration change. The new naming
- is consistent with those of other Linux distributions with
- systemd. See
- #29197
- for more information.
-
-
- A machine is affected if the virt-what tool
- either returns qemu or
- kvmand has interface
- names used in any part of its NixOS configuration, in
- particular if a static network configuration with
- networking.interfaces is used.
-
-
- Before rebooting affected machines, please ensure:
-
-
-
-
- Change the interface names in your NixOS configuration.
- The first interface will be called
- ens3, the second one
- ens8 and starting from there
- incremented by 1.
-
-
-
-
- After changing the interface names, rebuild your system
- with nixos-rebuild boot to activate the
- new configuration after a reboot. If you switch to the new
- configuration right away you might lose network
- connectivity! If using nixops, deploy
- with nixops deploy --force-reboot.
-
-
-
-
-
-
- The following changes apply if the
- stateVersion is changed to 17.09 or higher.
- For stateVersion = "17.03" or
- lower the old behavior is preserved.
-
-
-
-
- The postgres default version was
- changed from 9.5 to 9.6.
-
-
-
-
- The postgres superuser name has changed
- from root to
- postgres to more closely follow what
- other Linux distributions are doing.
-
-
-
-
- The postgres default
- dataDir has changed from
- /var/db/postgres to
- /var/lib/postgresql/$psqlSchema where
- $psqlSchema is 9.6 for example.
-
-
-
-
- The mysql default
- dataDir has changed from
- /var/mysql to
- /var/lib/mysql.
-
-
-
-
- Radicale’s default package has changed from 1.x to 2.x.
- Instructions to migrate can be found
- here
- . It is also possible to use the newer version by
- setting the package to
- radicale2, which is done automatically
- when stateVersion is 17.09 or higher.
- The extraArgs option has been added to
- allow passing the data migration arguments specified in
- the instructions; see the radicale.nix
- NixOS test for an example migration.
-
-
-
-
-
-
- The aiccu package was removed. This is due
- to SixXS
- sunsetting its IPv6 tunnel.
-
-
-
-
- The fanctl package and
- fan module have been removed due to the
- developers not upstreaming their iproute2 patches and lagging
- with compatibility to recent iproute2 versions.
-
-
-
-
- Top-level idea package collection was
- renamed. All JetBrains IDEs are now at
- jetbrains.
-
-
-
-
- flexget’s state database cannot be upgraded
- to its new internal format, requiring removal of any existing
- db-config.sqlite which will be
- automatically recreated.
-
-
-
-
- The ipfs service now doesn’t ignore the
- dataDir option anymore. If you’ve ever set
- this option to anything other than the default you’ll have to
- either unset it (so the default gets used) or migrate the old
- data manually with
-
-
-dataDir=<valueOfDataDir>
-mv /var/lib/ipfs/.ipfs/* $dataDir
-rmdir /var/lib/ipfs/.ipfs
-
-
-
-
- The caddy service was previously using an
- extra .caddy directory in the data
- directory specified with the dataDir
- option. The contents of the .caddy
- directory are now expected to be in the
- dataDir.
-
-
-
-
- The ssh-agent user service is not started
- by default anymore. Use
- programs.ssh.startAgent to enable it if
- needed. There is also a new
- programs.gnupg.agent module that creates a
- gpg-agent user service. It can also serve
- as a SSH agent if enableSSHSupport is set.
-
-
-
-
- The
- services.tinc.networks.<name>.listenAddress
- option had a misleading name that did not correspond to its
- behavior. It now correctly defines the ip to listen for
- incoming connections on. To keep the previous behaviour, use
- services.tinc.networks.<name>.bindToAddress
- instead. Refer to the description of the options for more
- details.
-
-
-
-
- tlsdate package and module were removed.
- This is due to the project being dead and not building with
- openssl 1.1.
-
-
-
-
- wvdial package and module were removed.
- This is due to the project being dead and not building with
- openssl 1.1.
-
-
-
-
- cc-wrappers setup-hook now exports a
- number of environment variables corresponding to binutils
- binaries, (e.g. LD,
- STRIP, RANLIB, etc).
- This is done to prevent packages build systems
- guessing, which is harder to predict, especially when
- cross-compiling. However, some packages have broken due to
- this—their build systems either not supporting, or claiming to
- support without adequate testing, taking such environment
- variables as parameters.
-
-
-
-
- services.firefox.syncserver now runs by
- default as a non-root user. To accommodate this change, the
- default sqlite database location has also been changed.
- Migration should work automatically. Refer to the description
- of the options for more details.
-
-
-
-
- The compiz window manager and package was
- removed. The system support had been broken for several years.
-
-
-
-
- Touchpad support should now be enabled through
- libinput as synaptics is
- now deprecated. See the option
- services.xserver.libinput.enable.
-
-
-
-
- grsecurity/PaX support has been dropped, following upstream’s
- decision to cease free support. See
-
- upstream’s announcement for more information. No
- complete replacement for grsecurity/PaX is available
- presently.
-
-
-
-
- services.mysql now has declarative
- configuration of databases and users with the
- ensureDatabases and
- ensureUsers options.
-
-
- These options will never delete existing databases and users,
- especially not when the value of the options are changed.
-
-
- The MySQL users will be identified using
-
- Unix socket authentication. This authenticates the Unix
- user with the same name only, and that without the need for a
- password.
-
-
- If you have previously created a MySQL root
- user with a password, you will need to
- add root user for unix socket
- authentication before using the new options. This can be done
- by running the following SQL script:
-
-
-CREATE USER 'root'@'%' IDENTIFIED BY '';
-GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' WITH GRANT OPTION;
-FLUSH PRIVILEGES;
-
--- Optionally, delete the password-authenticated user:
--- DROP USER 'root'@'localhost';
-
-
-
-
- services.mysqlBackup now works by default
- without any user setup, including for users other than
- mysql.
-
-
- By default, the mysql user is no longer the
- user which performs the backup. Instead a system account
- mysqlbackup is used.
-
-
- The mysqlBackup service is also now using
- systemd timers instead of cron.
-
-
- Therefore, the services.mysqlBackup.period
- option no longer exists, and has been replaced with
- services.mysqlBackup.calendar, which is in
- the format of
- systemd.time(7).
-
-
- If you expect to be sent an e-mail when the backup fails,
- consider using a script which monitors the systemd journal for
- errors. Regretfully, at present there is no built-in
- functionality for this.
-
-
- You can check that backups still work by running
- systemctl start mysql-backup then
- systemctl status mysql-backup.
-
-
-
-
- Templated systemd services e.g
- container@name are now handled currectly
- when switching to a new configuration, resulting in them being
- reloaded.
-
-
-
-
- Steam: the newStdcpp parameter was removed
- and should not be needed anymore.
-
-
-
-
- Redis has been updated to version 4 which mandates a cluster
- mass-restart, due to changes in the network handling, in order
- to ensure compatibility with networks NATing traffic.
-
-
-
-
-
- Other Notable Changes
-
-
-
- Modules can now be disabled by using
-
- disabledModules, allowing another to take it’s place.
- This can be used to import a set of modules from another
- channel while keeping the rest of the system on a stable
- release.
-
-
-
-
- Updated to FreeType 2.7.1, including a new TrueType engine.
- The new engine replaces the Infinality engine which was the
- default in NixOS. The default font rendering settings are now
- provided by fontconfig-penultimate, replacing
- fontconfig-ultimate; the new defaults are less invasive and
- provide rendering that is more consistent with other systems
- and hopefully with each font designer’s intent. Some
- system-wide configuration has been removed from the Fontconfig
- NixOS module where user Fontconfig settings are available.
-
-
-
-
- ZFS/SPL have been updated to 0.7.0,
- zfsUnstable, splUnstable have therefore
- been removed.
-
-
-
-
- The time.timeZone option now allows the
- value null in addition to timezone strings.
- This value allows changing the timezone of a system
- imperatively using
- timedatectl set-timezone. The default
- timezone is still UTC.
-
-
-
-
- Nixpkgs overlays may now be specified with a file as well as a
- directory. The value of
- <nixpkgs-overlays> may be a file, and
- ~/.config/nixpkgs/overlays.nix can be used
- instead of the ~/.config/nixpkgs/overlays
- directory.
-
-
- See the overlays chapter of the Nixpkgs manual for more
- details.
-
-
-
-
- Definitions for /etc/hosts can now be
- specified declaratively with
- networking.hosts.
-
-
-
-
- Two new options have been added to the installer loader, in
- addition to the default having changed. The kernel log
- verbosity has been lowered to the upstream default for the
- default options, in order to not spam the console when e.g.
- joining a network.
-
-
- This therefore leads to adding a new debug
- option to set the log level to the previous verbose mode, to
- make debugging easier, but still accessible easily.
-
-
- Additionally a copytoram option has been
- added, which makes it possible to remove the install medium
- after booting. This allows tethering from your phone after
- booting from it.
-
-
-
-
- services.gitlab-runner.configOptions has
- been added to specify the configuration of gitlab-runners
- declaratively.
-
-
-
-
- services.jenkins.plugins has been added to
- install plugins easily, this can be generated with
- jenkinsPlugins2nix.
-
-
-
-
- services.postfix.config has been added to
- specify the main.cf with NixOS options. Additionally other
- options have been added to the postfix module and has been
- improved further.
-
-
-
-
- The GitLab package and module have been updated to the latest
- 10.0 release.
-
-
-
-
- The systemd-boot boot loader now lists the
- NixOS version, kernel version and build date of all bootable
- generations.
-
-
-
-
- The dnscrypt-proxy service now defaults to using a random
- upstream resolver, selected from the list of public
- non-logging resolvers with DNSSEC support. Existing
- configurations can be migrated to this mode of operation by
- omitting the
- services.dnscrypt-proxy.resolverName option
- or setting it to "random".
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1803.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1803.section.xml
deleted file mode 100644
index f197c52906b0..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1803.section.xml
+++ /dev/null
@@ -1,879 +0,0 @@
-
- Release 18.03 (<quote>Impala</quote>, 2018/04/04)
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- End of support is planned for end of October 2018, handing
- over to 18.09.
-
-
-
-
- Platform support: x86_64-linux and x86_64-darwin since release
- time (the latter isn’t NixOS, really). Binaries for
- aarch64-linux are available, but no channel exists yet, as
- it’s waiting for some test fixes, etc.
-
-
-
-
- Nix now defaults to 2.0; see its
- release
- notes.
-
-
-
-
- Core version changes: linux: 4.9 -> 4.14, glibc: 2.25 ->
- 2.26, gcc: 6 -> 7, systemd: 234 -> 237.
-
-
-
-
- Desktop version changes: gnome: 3.24 -> 3.26, (KDE)
- plasma-desktop: 5.10 -> 5.12.
-
-
-
-
- MariaDB 10.2, updated from 10.1, is now the default MySQL
- implementation. While upgrading a few changes have been made
- to the infrastructure involved:
-
-
-
-
- libmysql has been deprecated, please
- use mysql.connector-c instead, a
- compatibility passthru has been added to the MySQL
- packages.
-
-
-
-
- The mysql57 package has a new
- static output containing the static
- libraries including libmysqld.a
-
-
-
-
-
-
- PHP now defaults to PHP 7.2, updated from 7.1.
-
-
-
-
-
- New Services
-
- The following new services were added since the last release:
-
-
-
-
- ./config/krb5/default.nix
-
-
-
-
- ./hardware/digitalbitbox.nix
-
-
-
-
- ./misc/label.nix
-
-
-
-
- ./programs/ccache.nix
-
-
-
-
- ./programs/criu.nix
-
-
-
-
- ./programs/digitalbitbox/default.nix
-
-
-
-
- ./programs/less.nix
-
-
-
-
- ./programs/npm.nix
-
-
-
-
- ./programs/plotinus.nix
-
-
-
-
- ./programs/rootston.nix
-
-
-
-
- ./programs/systemtap.nix
-
-
-
-
- ./programs/sway.nix
-
-
-
-
- ./programs/udevil.nix
-
-
-
-
- ./programs/way-cooler.nix
-
-
-
-
- ./programs/yabar.nix
-
-
-
-
- ./programs/zsh/zsh-autoenv.nix
-
-
-
-
- ./services/backup/borgbackup.nix
-
-
-
-
- ./services/backup/crashplan-small-business.nix
-
-
-
-
- ./services/desktops/dleyna-renderer.nix
-
-
-
-
- ./services/desktops/dleyna-server.nix
-
-
-
-
- ./services/desktops/pipewire.nix
-
-
-
-
- ./services/desktops/gnome3/chrome-gnome-shell.nix
-
-
-
-
- ./services/desktops/gnome3/tracker-miners.nix
-
-
-
-
- ./services/hardware/fwupd.nix
-
-
-
-
- ./services/hardware/interception-tools.nix
-
-
-
-
- ./services/hardware/u2f.nix
-
-
-
-
- ./services/hardware/usbmuxd.nix
-
-
-
-
- ./services/mail/clamsmtp.nix
-
-
-
-
- ./services/mail/dkimproxy-out.nix
-
-
-
-
- ./services/mail/pfix-srsd.nix
-
-
-
-
- ./services/misc/gitea.nix
-
-
-
-
- ./services/misc/home-assistant.nix
-
-
-
-
- ./services/misc/ihaskell.nix
-
-
-
-
- ./services/misc/logkeys.nix
-
-
-
-
- ./services/misc/novacomd.nix
-
-
-
-
- ./services/misc/osrm.nix
-
-
-
-
- ./services/misc/plexpy.nix
-
-
-
-
- ./services/misc/pykms.nix
-
-
-
-
- ./services/misc/tzupdate.nix
-
-
-
-
- ./services/monitoring/fusion-inventory.nix
-
-
-
-
- ./services/monitoring/prometheus/exporters.nix
-
-
-
-
- ./services/network-filesystems/beegfs.nix
-
-
-
-
- ./services/network-filesystems/davfs2.nix
-
-
-
-
- ./services/network-filesystems/openafs/client.nix
-
-
-
-
- ./services/network-filesystems/openafs/server.nix
-
-
-
-
- ./services/network-filesystems/ceph.nix
-
-
-
-
- ./services/networking/aria2.nix
-
-
-
-
- ./services/networking/monero.nix
-
-
-
-
- ./services/networking/nghttpx/default.nix
-
-
-
-
- ./services/networking/nixops-dns.nix
-
-
-
-
- ./services/networking/rxe.nix
-
-
-
-
- ./services/networking/stunnel.nix
-
-
-
-
- ./services/web-apps/matomo.nix
-
-
-
-
- ./services/web-apps/restya-board.nix
-
-
-
-
- ./services/web-servers/mighttpd2.nix
-
-
-
-
- ./services/x11/fractalart.nix
-
-
-
-
- ./system/boot/binfmt.nix
-
-
-
-
- ./system/boot/grow-partition.nix
-
-
-
-
- ./tasks/filesystems/ecryptfs.nix
-
-
-
-
- ./virtualisation/hyperv-guest.nix
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- sound.enable now defaults to false.
-
-
-
-
- Dollar signs in options under
- services.postfix are passed verbatim to
- Postfix, which will interpret them as the beginning of a
- parameter expression. This was already true for string-valued
- options in the previous release, but not for list-valued
- options. If you need to pass literal dollar signs through
- Postfix, double them.
-
-
-
-
- The postage package (for web-based
- PostgreSQL administration) has been renamed to
- pgmanage. The corresponding module has also
- been renamed. To migrate please rename all
- services.postage options to
- services.pgmanage.
-
-
-
-
- Package attributes starting with a digit have been prefixed
- with an underscore sign. This is to avoid quoting in the
- configuration and other issues with command-line tools like
- nix-env. The change affects the following
- packages:
-
-
-
-
- 2048-in-terminal →
- _2048-in-terminal
-
-
-
-
- 90secondportraits →
- _90secondportraits
-
-
-
-
- 2bwm → _2bwm
-
-
-
-
- 389-ds-base →
- _389-ds-base
-
-
-
-
-
-
- The OpenSSH service no longer enables
- support for DSA keys by default, which could cause a system
- lock out. Update your keys or, unfavorably, re-enable DSA
- support manually.
-
-
- DSA support was
- deprecated
- in OpenSSH 7.0, due to it being too weak. To re-enable
- support, add
- PubkeyAcceptedKeyTypes +ssh-dss to the end
- of your services.openssh.extraConfig.
-
-
- After updating the keys to be stronger, anyone still on a
- pre-17.03 version is safe to jump to 17.03, as vetted
- here.
-
-
-
-
- The openssh package now includes Kerberos
- support by default; the
- openssh_with_kerberos package is now a
- deprecated alias. If you do not want Kerberos support, you can
- do
- openssh.override { withKerberos = false; }.
- Note, this also applies to the openssh_hpn
- package.
-
-
-
-
- cc-wrapper has been split in two; there is
- now also a bintools-wrapper. The most
- commonly used files in nix-support are now
- split between the two wrappers. Some commonly used ones, like
- nix-support/dynamic-linker, are duplicated
- for backwards compatability, even though they rightly belong
- only in bintools-wrapper. Other more
- obscure ones are just moved.
-
-
-
-
- The propagation logic has been changed. The new logic, along
- with new types of dependencies that go with, is thoroughly
- documented in the Specifying dependencies
- section of the Standard Environment chapter of
- the nixpkgs manual. The old logic isn’t but is easy to
- describe: dependencies were propagated as the same type of
- dependency no matter what. In practice, that means that many
- propagatedNativeBuildInputs should instead
- be propagatedBuildInputs. Thankfully, that
- was and is the least used type of dependency. Also, it means
- that some propagatedBuildInputs should
- instead be depsTargetTargetPropagated.
- Other types dependencies should be unaffected.
-
-
-
-
- lib.addPassthru drv passthru is removed.
- Use lib.extendDerivation true passthru drv
- instead.
-
-
-
-
- The memcached service no longer accept
- dynamic socket paths via
- services.memcached.socket. Unix sockets can
- be still enabled by
- services.memcached.enableUnixSocket and
- will be accessible at
- /run/memcached/memcached.sock.
-
-
-
-
- The hardware.amdHybridGraphics.disable
- option was removed for lack of a maintainer. If you still need
- this module, you may wish to include a copy of it from an
- older version of nixos in your imports.
-
-
-
-
- The merging of config options for
- services.postfix.config was buggy.
- Previously, if other options in the Postfix module like
- services.postfix.useSrs were set and the
- user set config options that were also set by such options,
- the resulting config wouldn’t include all options that were
- needed. They are now merged correctly. If config options need
- to be overridden, lib.mkForce or
- lib.mkOverride can be used.
-
-
-
-
- The following changes apply if the
- stateVersion is changed to 18.03 or higher.
- For stateVersion = "17.09" or
- lower the old behavior is preserved.
-
-
-
-
- matrix-synapse uses postgresql by
- default instead of sqlite. Migration instructions can be
- found
-
- here .
-
-
-
-
-
-
- The jid package has been removed, due to
- maintenance overhead of a go package having non-versioned
- dependencies.
-
-
-
-
- When using services.xserver.libinput
- (enabled by default in GNOME), it now handles all input
- devices, not just touchpads. As a result, you might need to
- re-evaluate any custom Xorg configuration. In particular,
- Option "XkbRules" "base"
- may result in broken keyboard layout.
-
-
-
-
- The attic package was removed. A maintained
- fork called
- Borg
- should be used instead. Migration instructions can be found
- here.
-
-
-
-
- The Piwik analytics software was renamed to Matomo:
-
-
-
-
- The package pkgs.piwik was renamed to
- pkgs.matomo.
-
-
-
-
- The service services.piwik was renamed
- to services.matomo.
-
-
-
-
- The data directory /var/lib/piwik was
- renamed to /var/lib/matomo. All files
- will be moved automatically on first startup, but you
- might need to adjust your backup scripts.
-
-
-
-
- The default serverName for the nginx
- configuration changed from
- piwik.${config.networking.hostName} to
- matomo.${config.networking.hostName}.${config.networking.domain}
- if config.networking.domain is set,
- matomo.${config.networking.hostName} if
- it is not set. If you change your
- serverName, remember you’ll need to
- update the trustedHosts[] array in
- /var/lib/matomo/config/config.ini.php
- as well.
-
-
-
-
- The piwik user was renamed to
- matomo. The service will adjust
- ownership automatically for files in the data directory.
- If you use unix socket authentication, remember to give
- the new matomo user access to the
- database and to change the username to
- matomo in the
- [database] section of
- /var/lib/matomo/config/config.ini.php.
-
-
-
-
- If you named your database `piwik`, you might want to
- rename it to `matomo` to keep things clean, but this is
- neither enforced nor required.
-
-
-
-
-
-
- nodejs-4_x is end-of-life.
- nodejs-4_x,
- nodejs-slim-4_x and
- nodePackages_4_x are removed.
-
-
-
-
- The pump.io NixOS module was removed. It is
- now maintained as an
- external
- module.
-
-
-
-
- The Prosody XMPP server has received a major update. The
- following modules were renamed:
-
-
-
-
- services.prosody.modules.httpserver is
- now services.prosody.modules.http_files
-
-
-
-
- services.prosody.modules.console is now
- services.prosody.modules.admin_telnet
-
-
-
-
- Many new modules are now core modules, most notably
- services.prosody.modules.carbons and
- services.prosody.modules.mam.
-
-
- The better-performing libevent backend is
- now enabled by default.
-
-
- withCommunityModules now passes through the
- modules to services.prosody.extraModules.
- Use withOnlyInstalledCommunityModules for
- modules that should not be enabled directly, e.g
- lib_ldap.
-
-
-
-
- All prometheus exporter modules are now defined as submodules.
- The exporters are configured using
- services.prometheus.exporters.
-
-
-
-
-
- Other Notable Changes
-
-
-
- ZNC option services.znc.mutable now
- defaults to true. That means that old
- configuration is not overwritten by default when update to the
- znc options are made.
-
-
-
-
- The option
- networking.wireless.networks.<name>.auth
- has been added for wireless networks with WPA-Enterprise
- authentication. There is also a new
- extraConfig option to directly configure
- wpa_supplicant and
- hidden to connect to hidden networks.
-
-
-
-
- In the module
- networking.interfaces.<name> the
- following options have been removed:
-
-
-
-
- ipAddress
-
-
-
-
- ipv6Address
-
-
-
-
- prefixLength
-
-
-
-
- ipv6PrefixLength
-
-
-
-
- subnetMask
-
-
-
-
- To assign static addresses to an interface the options
- ipv4.addresses and
- ipv6.addresses should be used instead. The
- options ip4 and ip6 have
- been renamed to ipv4.addresses
- ipv6.addresses respectively. The new
- options ipv4.routes and
- ipv6.routes have been added to set up
- static routing.
-
-
-
-
- The option services.logstash.listenAddress
- is now 127.0.0.1 by default. Previously the
- default behaviour was to listen on all interfaces.
-
-
-
-
- services.btrfs.autoScrub has been added, to
- periodically check btrfs filesystems for data corruption. If
- there’s a correct copy available, it will automatically repair
- corrupted blocks.
-
-
-
-
- displayManager.lightdm.greeters.gtk.clock-format.
- has been added, the clock format string (as expected by
- strftime, e.g. %H:%M) to use with the
- lightdm gtk greeter panel.
-
-
- If set to null the default clock format is used.
-
-
-
-
- displayManager.lightdm.greeters.gtk.indicators
- has been added, a list of allowed indicator modules to use
- with the lightdm gtk greeter panel.
-
-
- Built-in indicators include ~a11y,
- ~language, ~session,
- ~power, ~clock,
- ~host, ~spacer. Unity
- indicators can be represented by short name (e.g.
- sound, power), service
- file name, or absolute path.
-
-
- If set to null the default indicators are
- used.
-
-
- In order to have the previous default configuration add
-
-
-{
- services.xserver.displayManager.lightdm.greeters.gtk.indicators = [
- "~host" "~spacer"
- "~clock" "~spacer"
- "~session"
- "~language"
- "~a11y"
- "~power"
- ];
-}
-
-
- to your configuration.nix.
-
-
-
-
- The NixOS test driver supports user services declared by
- systemd.user.services. The methods
- waitForUnit,
- getUnitInfo, startJob
- and stopJob provide an optional
- $user argument for that purpose.
-
-
-
-
- Enabling bash completion on NixOS,
- programs.bash.enableCompletion, will now
- also enable completion for the Nix command line tools by
- installing the
- nix-bash-completions
- package.
-
-
-
-
- The vim/kakoune plugin updater now reads from a CSV file:
- check
- pkgs/applications/editors/vim/plugins/vim-plugin-names
- out to see the new format
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1809.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1809.section.xml
deleted file mode 100644
index 4bbfa7be398e..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1809.section.xml
+++ /dev/null
@@ -1,941 +0,0 @@
-
- Release 18.09 (<quote>Jellyfish</quote>, 2018/10/05)
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following notable updates:
-
-
-
-
- End of support is planned for end of April 2019, handing over
- to 19.03.
-
-
-
-
- Platform support: x86_64-linux and x86_64-darwin as always.
- Support for aarch64-linux is as with the previous releases,
- not equivalent to the x86-64-linux release, but with efforts
- to reach parity.
-
-
-
-
- Nix has been updated to 2.1; see its
- release
- notes.
-
-
-
-
- Core versions: linux: 4.14 LTS (unchanged), glibc: 2.26 →
- 2.27, gcc: 7 (unchanged), systemd: 237 → 239.
-
-
-
-
- Desktop version changes: gnome: 3.26 → 3.28, (KDE)
- plasma-desktop: 5.12 → 5.13.
-
-
-
-
- Notable changes and additions for 18.09 include:
-
-
-
-
- Support for wrapping binaries using
- firejail has been added through
- programs.firejail.wrappedBinaries.
-
-
- For example
-
-
-{
- programs.firejail = {
- enable = true;
- wrappedBinaries = {
- firefox = "${lib.getBin pkgs.firefox}/bin/firefox";
- mpv = "${lib.getBin pkgs.mpv}/bin/mpv";
- };
- };
-}
-
-
- This will place firefox and
- mpv binaries in the global path wrapped by
- firejail.
-
-
-
-
- User channels are now in the default
- NIX_PATH, allowing users to use their
- personal nix-channel defined channels in
- nix-build and nix-shell
- commands, as well as in imports like
- import <mychannel>.
-
-
- For example
-
-
-$ nix-channel --add https://nixos.org/channels/nixpkgs-unstable nixpkgsunstable
-$ nix-channel --update
-$ nix-build '<nixpkgsunstable>' -A gitFull
-$ nix run -f '<nixpkgsunstable>' gitFull
-$ nix-instantiate -E '(import <nixpkgsunstable> {}).gitFull'
-
-
-
-
-
- New Services
-
- A curated selection of new services that were added since the last
- release:
-
-
-
-
- The services.cassandra module has been
- reworked and was rewritten from scratch. The service has
- succeeding tests for the versions 2.1, 2.2, 3.0 and 3.11 of
- Apache
- Cassandra.
-
-
-
-
- There is a new services.foundationdb module
- for deploying
- FoundationDB
- clusters.
-
-
-
-
- When enabled the iproute2 will copy the
- files expected by ip route (e.g.,
- rt_tables) in
- /etc/iproute2. This allows to write aliases
- for routing tables for instance.
-
-
-
-
- services.strongswan-swanctl is a modern
- replacement for services.strongswan. You
- can use either one of them to setup IPsec VPNs but not both at
- the same time.
-
-
- services.strongswan-swanctl uses the
- swanctl
- command which uses the modern
- vici
- Versatile IKE Configuration Interface.
- The deprecated ipsec command used in
- services.strongswan is using the legacy
- stroke
- configuration interface.
-
-
-
-
- The new services.elasticsearch-curator
- service periodically curates or manages, your Elasticsearch
- indices and snapshots.
-
-
-
-
- Every new services:
-
-
-
-
- ./config/xdg/autostart.nix
-
-
-
-
- ./config/xdg/icons.nix
-
-
-
-
- ./config/xdg/menus.nix
-
-
-
-
- ./config/xdg/mime.nix
-
-
-
-
- ./hardware/brightnessctl.nix
-
-
-
-
- ./hardware/onlykey.nix
-
-
-
-
- ./hardware/video/uvcvideo/default.nix
-
-
-
-
- ./misc/documentation.nix
-
-
-
-
- ./programs/firejail.nix
-
-
-
-
- ./programs/iftop.nix
-
-
-
-
- ./programs/sedutil.nix
-
-
-
-
- ./programs/singularity.nix
-
-
-
-
- ./programs/xss-lock.nix
-
-
-
-
- ./programs/zsh/zsh-autosuggestions.nix
-
-
-
-
- ./services/admin/oxidized.nix
-
-
-
-
- ./services/backup/duplicati.nix
-
-
-
-
- ./services/backup/restic.nix
-
-
-
-
- ./services/backup/restic-rest-server.nix
-
-
-
-
- ./services/cluster/hadoop/default.nix
-
-
-
-
- ./services/databases/aerospike.nix
-
-
-
-
- ./services/databases/monetdb.nix
-
-
-
-
- ./services/desktops/bamf.nix
-
-
-
-
- ./services/desktops/flatpak.nix
-
-
-
-
- ./services/desktops/zeitgeist.nix
-
-
-
-
- ./services/development/bloop.nix
-
-
-
-
- ./services/development/jupyter/default.nix
-
-
-
-
- ./services/hardware/lcd.nix
-
-
-
-
- ./services/hardware/undervolt.nix
-
-
-
-
- ./services/misc/clipmenu.nix
-
-
-
-
- ./services/misc/gitweb.nix
-
-
-
-
- ./services/misc/serviio.nix
-
-
-
-
- ./services/misc/safeeyes.nix
-
-
-
-
- ./services/misc/sysprof.nix
-
-
-
-
- ./services/misc/weechat.nix
-
-
-
-
- ./services/monitoring/datadog-agent.nix
-
-
-
-
- ./services/monitoring/incron.nix
-
-
-
-
- ./services/networking/dnsdist.nix
-
-
-
-
- ./services/networking/freeradius.nix
-
-
-
-
- ./services/networking/hans.nix
-
-
-
-
- ./services/networking/morty.nix
-
-
-
-
- ./services/networking/ndppd.nix
-
-
-
-
- ./services/networking/ocserv.nix
-
-
-
-
- ./services/networking/owamp.nix
-
-
-
-
- ./services/networking/quagga.nix
-
-
-
-
- ./services/networking/shadowsocks.nix
-
-
-
-
- ./services/networking/stubby.nix
-
-
-
-
- ./services/networking/zeronet.nix
-
-
-
-
- ./services/security/certmgr.nix
-
-
-
-
- ./services/security/cfssl.nix
-
-
-
-
- ./services/security/oauth2_proxy_nginx.nix
-
-
-
-
- ./services/web-apps/virtlyst.nix
-
-
-
-
- ./services/web-apps/youtrack.nix
-
-
-
-
- ./services/web-servers/hitch/default.nix
-
-
-
-
- ./services/web-servers/hydron.nix
-
-
-
-
- ./services/web-servers/meguca.nix
-
-
-
-
- ./services/web-servers/nginx/gitweb.nix
-
-
-
-
- ./virtualisation/kvmgt.nix
-
-
-
-
- ./virtualisation/qemu-guest-agent.nix
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- Some licenses that were incorrectly not marked as unfree now
- are. This is the case for:
-
-
-
-
- cc-by-nc-sa-20: Creative Commons Attribution Non
- Commercial Share Alike 2.0
-
-
-
-
- cc-by-nc-sa-25: Creative Commons Attribution Non
- Commercial Share Alike 2.5
-
-
-
-
- cc-by-nc-sa-30: Creative Commons Attribution Non
- Commercial Share Alike 3.0
-
-
-
-
- cc-by-nc-sa-40: Creative Commons Attribution Non
- Commercial Share Alike 4.0
-
-
-
-
- cc-by-nd-30: Creative Commons Attribution-No Derivative
- Works v3.00
-
-
-
-
- msrla: Microsoft Research License Agreement
-
-
-
-
-
-
- The deprecated services.cassandra module
- has seen a complete rewrite. (See above.)
-
-
-
-
- lib.strict is removed. Use
- builtins.seq instead.
-
-
-
-
- The clementine package points now to the
- free derivation. clementineFree is removed
- now and clementineUnfree points to the
- package which is bundled with the unfree
- libspotify package.
-
-
-
-
- The netcat package is now taken directly
- from OpenBSD’s libressl, instead of relying
- on Debian’s fork. The new version should be very close to the
- old version, but there are some minor differences.
- Importantly, flags like -b, -q, -C, and -Z are no longer
- accepted by the nc command.
-
-
-
-
- The services.docker-registry.extraConfig
- object doesn’t contain environment variables anymore. Instead
- it needs to provide an object structure that can be mapped
- onto the YAML configuration defined in
- the
- docker/distribution docs.
-
-
-
-
- gnucash has changed from version 2.4 to
- 3.x. If you’ve been using gnucash (version
- 2.4) instead of gnucash26 (version 2.6) you
- must open your Gnucash data file(s) with
- gnucash26 and then save them to upgrade the
- file format. Then you may use your data file(s) with Gnucash
- 3.x. See the upgrade
- documentation.
- Gnucash 2.4 is still available under the attribute
- gnucash24.
-
-
-
-
- services.munge now runs as user (and group)
- munge instead of root. Make sure the key
- file is accessible to the daemon.
-
-
-
-
- dockerTools.buildImage now uses
- null as default value for
- tag, which indicates that the nix output
- hash will be used as tag.
-
-
-
-
- The ELK stack: elasticsearch,
- logstash and kibana has
- been upgraded from 2.* to 6.3.*. The 2.* versions have been
- unsupported
- since last year so they have been removed. You can
- still use the 5.* versions under the names
- elasticsearch5,
- logstash5 and kibana5.
-
-
- The elastic beats: filebeat,
- heartbeat, metricbeat
- and packetbeat have had the same treatment:
- they now target 6.3.* as well. The 5.* versions are available
- under the names: filebeat5,
- heartbeat5, metricbeat5
- and packetbeat5
-
-
- The ELK-6.3 stack now comes with
- X-Pack
- by default. Since X-Pack is licensed under the
- Elastic
- License the ELK packages now have an unfree license. To
- use them you need to specify
- allowUnfree = true; in your nixpkgs
- configuration.
-
-
- Fortunately there is also a free variant of the ELK stack
- without X-Pack. The packages are available under the names:
- elasticsearch-oss,
- logstash-oss and
- kibana-oss.
-
-
-
-
- Options
- boot.initrd.luks.devices.name.yubikey.ramfsMountPoint
- boot.initrd.luks.devices.name.yubikey.storage.mountPoint
- were removed. luksroot.nix module never
- supported more than one YubiKey at a time anyway, hence those
- options never had any effect. You should be able to remove
- them from your config without any issues.
-
-
-
-
- stdenv.system and system
- in nixpkgs now refer to the host platform instead of the build
- platform. For native builds this is not change, let alone a
- breaking one. For cross builds, it is a breaking change, and
- stdenv.buildPlatform.system can be used
- instead for the old behavior. They should be using that
- anyways for clarity.
-
-
-
-
- Groups kvm and render
- are introduced now, as systemd requires them.
-
-
-
-
-
- Other Notable Changes
-
-
-
- dockerTools.pullImage relies on image
- digest instead of image tag to download the image. The
- sha256 of a pulled image has to be updated.
-
-
-
-
- lib.attrNamesToStr has been deprecated. Use
- more specific concatenation
- (lib.concat(Map)StringsSep) instead.
-
-
-
-
- lib.addErrorContextToAttrs has been
- deprecated. Use builtins.addErrorContext
- directly.
-
-
-
-
- lib.showVal has been deprecated. Use
- lib.traceSeqN instead.
-
-
-
-
- lib.traceXMLVal has been deprecated. Use
- lib.traceValFn builtins.toXml instead.
-
-
-
-
- lib.traceXMLValMarked has been deprecated.
- Use
- lib.traceValFn (x: str + builtins.toXML x)
- instead.
-
-
-
-
- The pkgs argument to NixOS modules can now
- be set directly using nixpkgs.pkgs.
- Previously, only the system,
- config and overlays
- arguments could be used to influence pkgs.
-
-
-
-
- A NixOS system can now be constructed more easily based on a
- preexisting invocation of Nixpkgs. For example:
-
-
-{
- inherit (pkgs.nixos {
- boot.loader.grub.enable = false;
- fileSystems."/".device = "/dev/xvda1";
- }) toplevel kernel initialRamdisk manual;
-}
-
-
- This benefits evaluation performance, lets you write Nixpkgs
- packages that depend on NixOS images and is consistent with a
- deployment architecture that would be centered around Nixpkgs
- overlays.
-
-
-
-
- lib.traceValIfNot has been deprecated. Use
- if/then/else and
- lib.traceValSeq instead.
-
-
-
-
- lib.traceCallXml has been deprecated.
- Please complain if you use the function regularly.
-
-
-
-
- The attribute lib.nixpkgsVersion has been
- deprecated in favor of lib.version. Please
- refer to the discussion in
- NixOS/nixpkgs#39416
- for further reference.
-
-
-
-
- lib.recursiveUpdateUntil was not acting
- according to its specification. It has been fixed to act
- according to the docstring, and a test has been added.
-
-
-
-
- The module for security.dhparams has two
- new options now:
-
-
-
-
- security.dhparams.stateless
-
-
-
- Puts the generated Diffie-Hellman parameters into the
- Nix store instead of managing them in a stateful manner
- in /var/lib/dhparams.
-
-
-
-
-
- security.dhparams.defaultBitSize
-
-
-
- The default bit size to use for the generated
- Diffie-Hellman parameters.
-
-
-
-
-
-
- The path to the actual generated parameter files should now
- be queried using
- config.security.dhparams.params.name.path
- because it might be either in the Nix store or in a
- directory configured by
- security.dhparams.path.
-
-
-
-
- For developers:
-
-
- Module implementers should not set a specific bit size in
- order to let users configure it by themselves if they want
- to have a different bit size than the default (2048).
-
-
- An example usage of this would be:
-
-
-{ config, ... }:
-
-{
- security.dhparams.params.myservice = {};
- environment.etc."myservice.conf".text = ''
- dhparams = ${config.security.dhparams.params.myservice.path}
- '';
-}
-
-
-
-
-
- networking.networkmanager.useDnsmasq has
- been deprecated. Use
- networking.networkmanager.dns instead.
-
-
-
-
- The Kubernetes package has been bumped to major version 1.11.
- Please consult the
- release
- notes for details on new features and api changes.
-
-
-
-
- The option
- services.kubernetes.apiserver.admissionControl
- was renamed to
- services.kubernetes.apiserver.enableAdmissionPlugins.
-
-
-
-
- Recommended way to access the Kubernetes Dashboard is via
- HTTPS (TLS) Therefore; public service port for the dashboard
- has changed to 443 (container port 8443) and scheme to https.
-
-
-
-
- The option
- services.kubernetes.apiserver.address was
- renamed to
- services.kubernetes.apiserver.bindAddress.
- Note that the default value has changed from 127.0.0.1 to
- 0.0.0.0.
-
-
-
-
- The option
- services.kubernetes.apiserver.publicAddress
- was not used and thus has been removed.
-
-
-
-
- The option
- services.kubernetes.addons.dashboard.enableRBAC
- was renamed to
- services.kubernetes.addons.dashboard.rbac.enable.
-
-
-
-
- The Kubernetes Dashboard now has only minimal RBAC permissions
- by default. If dashboard cluster-admin rights are desired, set
- services.kubernetes.addons.dashboard.rbac.clusterAdmin
- to true. On existing clusters, in order for the revocation of
- privileges to take effect, the current ClusterRoleBinding for
- kubernetes-dashboard must be manually removed:
- kubectl delete clusterrolebinding kubernetes-dashboard
-
-
-
-
- The programs.screen module provides allows
- to configure /etc/screenrc, however the
- module behaved fairly counterintuitive as the config exists,
- but the package wasn’t available. Since 18.09
- pkgs.screen will be added to
- environment.systemPackages.
-
-
-
-
- The module services.networking.hostapd now
- uses WPA2 by default.
-
-
-
-
- s6Dns, s6Networking,
- s6LinuxUtils and
- s6PortableUtils renamed to
- s6-dns, s6-networking,
- s6-linux-utils and
- s6-portable-utils respectively.
-
-
-
-
- The module option nix.useSandbox is now
- defaulted to true.
-
-
-
-
- The config activation script of
- nixos-rebuild now
- reloads
- all user units for each authenticated user.
-
-
-
-
- The default display manager is now LightDM. To use SLiM set
- services.xserver.displayManager.slim.enable
- to true.
-
-
-
-
- NixOS option descriptions are now automatically broken up into
- individual paragraphs if the text contains two consecutive
- newlines, so it’s no longer necessary to use
- </para><para> to start a new
- paragraph.
-
-
-
-
- Top-level buildPlatform,
- hostPlatform, and
- targetPlatform in Nixpkgs are deprecated.
- Please use their equivalents in stdenv
- instead: stdenv.buildPlatform,
- stdenv.hostPlatform, and
- stdenv.targetPlatform.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1903.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1903.section.xml
deleted file mode 100644
index ed26f2ba45d0..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1903.section.xml
+++ /dev/null
@@ -1,790 +0,0 @@
-
- Release 19.03 (<quote>Koi</quote>, 2019/04/11)
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- End of support is planned for end of October 2019, handing
- over to 19.09.
-
-
-
-
- The default Python 3 interpreter is now CPython 3.7 instead of
- CPython 3.6.
-
-
-
-
- Added the Pantheon desktop environment. It can be enabled
- through
- services.xserver.desktopManager.pantheon.enable.
-
-
-
- By default,
- services.xserver.desktopManager.pantheon
- enables LightDM as a display manager, as pantheon’s screen
- locking implementation relies on it. Because of that it is
- recommended to leave LightDM enabled. If you’d like to
- disable it anyway, set
- services.xserver.displayManager.lightdm.enable
- to false and enable your preferred
- display manager.
-
-
-
- Also note that Pantheon’s LightDM greeter is not enabled by
- default, because it has numerous issues in NixOS and isn’t
- optimal for use here yet.
-
-
-
-
- A major refactoring of the Kubernetes module has been
- completed. Refactorings primarily focus on decoupling
- components and enhancing security. Two-way TLS and RBAC has
- been enabled by default for all components, which slightly
- changes the way the module is configured. See:
- for details.
-
-
-
-
- There is now a set of confinement options
- for systemd.services, which allows to
- restrict services into a chroot 2 ed environment that only
- contains the store paths from the runtime closure of the
- service.
-
-
-
-
-
- New Services
-
- The following new services were added since the last release:
-
-
-
-
- ./programs/nm-applet.nix
-
-
-
-
- There is a new security.googleOsLogin
- module for using
- OS
- Login to manage SSH access to Google Compute Engine
- instances, which supersedes the imperative and broken
- google-accounts-daemon used in
- nixos/modules/virtualisation/google-compute-config.nix.
-
-
-
-
- ./services/misc/beanstalkd.nix
-
-
-
-
- There is a new services.cockroachdb module
- for running CockroachDB databases. NixOS now ships with
- CockroachDB 2.1.x as well, available on
- x86_64-linux and
- aarch64-linux.
-
-
-
-
- ./security/duosec.nix
-
-
-
-
- The PAM module
- for Duo Security has been enabled for use. One can
- configure it using the security.duosec
- options along with the corresponding PAM option in
- security.pam.services.<name?>.duoSecurity.enable.
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- The minimum version of Nix required to evaluate Nixpkgs is now
- 2.0.
-
-
-
-
- For users of NixOS 18.03 and 19.03, NixOS defaults to Nix
- 2.0, but supports using Nix 1.11 by setting
- nix.package = pkgs.nix1;. If this
- option is set to a Nix 1.11 package, you will need to
- either unset the option or upgrade it to Nix 2.0.
-
-
-
-
- For users of NixOS 17.09, you will first need to upgrade
- Nix by setting
- nix.package = pkgs.nixStable2; and run
- nixos-rebuild switch as the
- root user.
-
-
-
-
- For users of a daemon-less Nix installation on Linux or
- macOS, you can upgrade Nix by running
- curl -L https://nixos.org/nix/install | sh,
- or prior to doing a channel update, running
- nix-env -iA nix. If you have already
- run a channel update and Nix is no longer able to evaluate
- Nixpkgs, the error message printed should provide adequate
- directions for upgrading Nix.
-
-
-
-
- For users of the Nix daemon on macOS, you can upgrade Nix
- by running
- sudo -i sh -c 'nix-channel --update && nix-env -iA nixpkgs.nix'; sudo launchctl stop org.nixos.nix-daemon; sudo launchctl start org.nixos.nix-daemon.
-
-
-
-
-
-
- The buildPythonPackage function now sets
- strictDeps = true to help distinguish
- between native and non-native dependencies in order to improve
- cross-compilation compatibility. Note however that this may
- break user expressions.
-
-
-
-
- The buildPythonPackage function now sets
- LANG = C.UTF-8 to enable Unicode support.
- The glibcLocales package is no longer
- needed as a build input.
-
-
-
-
- The Syncthing state and configuration data has been moved from
- services.syncthing.dataDir to the newly
- defined services.syncthing.configDir, which
- default to
- /var/lib/syncthing/.config/syncthing. This
- change makes possible to share synced directories using ACLs
- without Syncthing resetting the permission on every start.
-
-
-
-
- The ntp module now has sane default
- restrictions. If you’re relying on the previous defaults,
- which permitted all queries and commands from all
- firewall-permitted sources, you can set
- services.ntp.restrictDefault and
- services.ntp.restrictSource to
- [].
-
-
-
-
- Package rabbitmq_server is renamed to
- rabbitmq-server.
-
-
-
-
- The light module no longer uses setuid
- binaries, but udev rules. As a consequence users of that
- module have to belong to the video group in
- order to use the executable (i.e.
- users.users.yourusername.extraGroups = ["video"];).
-
-
-
-
- Buildbot now supports Python 3 and its packages have been
- moved to pythonPackages. The options
- services.buildbot-master.package and
- services.buildbot-worker.package can be
- used to select the Python 2 or 3 version of the package.
-
-
-
-
- Options
- services.znc.confOptions.networks.name.userName
- and
- services.znc.confOptions.networks.name.modulePackages
- were removed. They were never used for anything and can
- therefore safely be removed.
-
-
-
-
- Package wasm has been renamed
- proglodyte-wasm. The package
- wasm will be pointed to
- ocamlPackages.wasm in 19.09, so make sure
- to update your configuration if you want to keep
- proglodyte-wasm
-
-
-
-
- When the nixpkgs.pkgs option is set, NixOS
- will no longer ignore the nixpkgs.overlays
- option. The old behavior can be recovered by setting
- nixpkgs.overlays = lib.mkForce [];.
-
-
-
-
- OpenSMTPD has been upgraded to version 6.4.0p1. This release
- makes backwards-incompatible changes to the configuration file
- format. See man smtpd.conf for more
- information on the new file format.
-
-
-
-
- The versioned postgresql have been renamed
- to use underscore number separators. For example,
- postgresql96 has been renamed to
- postgresql_9_6.
-
-
-
-
- Package consul-ui and passthrough
- consul.ui have been removed. The package
- consul now uses upstream releases that
- vendor the UI into the binary. See
- #48714
- for details.
-
-
-
-
- Slurm introduces the new option
- services.slurm.stateSaveLocation, which is
- now set to /var/spool/slurm by default
- (instead of /var/spool). Make sure to move
- all files to the new directory or to set the option
- accordingly.
-
-
- The slurmctld now runs as user slurm
- instead of root. If you want to keep
- slurmctld running as root, set
- services.slurm.user = root.
-
-
- The options services.slurm.nodeName and
- services.slurm.partitionName are now sets
- of strings to correctly reflect that fact that each of these
- options can occour more than once in the configuration.
-
-
-
-
- The solr package has been upgraded from
- 4.10.3 to 7.5.0 and has undergone some major changes. The
- services.solr module has been updated to
- reflect these changes. Please review
- http://lucene.apache.org/solr/ carefully before upgrading.
-
-
-
-
- Package ckb is renamed to
- ckb-next, and options
- hardware.ckb.* are renamed to
- hardware.ckb-next.*.
-
-
-
-
- The option
- services.xserver.displayManager.job.logToFile
- which was previously set to true when using
- the display managers lightdm,
- sddm or xpra has been
- reset to the default value (false).
-
-
-
-
- Network interface indiscriminate NixOS firewall options
- (networking.firewall.allow*) are now
- preserved when also setting interface specific rules such as
- networking.firewall.interfaces.en0.allow*.
- These rules continue to use the pseudo device
- default
- (networking.firewall.interfaces.default.*),
- and assigning to this pseudo device will override the
- (networking.firewall.allow*) options.
-
-
-
-
- The nscd service now disables all caching
- of passwd and group
- databases by default. This was interferring with the correct
- functioning of the libnss_systemd.so module
- which is used by systemd to manage uids and
- usernames in the presence of DynamicUser=
- in systemd services. This was already the default behaviour in
- presence of services.sssd.enable = true
- because nscd caching would interfere with
- sssd in unpredictable ways as well. Because
- we’re using nscd not for caching, but for convincing glibc to
- find NSS modules in the nix store instead of an absolute path,
- we have decided to disable caching globally now, as it’s
- usually not the behaviour the user wants and can lead to
- surprising behaviour. Furthermore, negative caching of host
- lookups is also disabled now by default. This should fix the
- issue of dns lookups failing in the presence of an unreliable
- network.
-
-
- If the old behaviour is desired, this can be restored by
- setting the services.nscd.config option
- with the desired caching parameters.
-
-
-{
- services.nscd.config =
- ''
- server-user nscd
- threads 1
- paranoia no
- debug-level 0
-
- enable-cache passwd yes
- positive-time-to-live passwd 600
- negative-time-to-live passwd 20
- suggested-size passwd 211
- check-files passwd yes
- persistent passwd no
- shared passwd yes
-
- enable-cache group yes
- positive-time-to-live group 3600
- negative-time-to-live group 60
- suggested-size group 211
- check-files group yes
- persistent group no
- shared group yes
-
- enable-cache hosts yes
- positive-time-to-live hosts 600
- negative-time-to-live hosts 5
- suggested-size hosts 211
- check-files hosts yes
- persistent hosts no
- shared hosts yes
- '';
-}
-
-
- See
- #50316
- for details.
-
-
-
-
- GitLab Shell previously used the nix store paths for the
- gitlab-shell command in its
- authorized_keys file, which might stop
- working after garbage collection. To circumvent that, we
- regenerated that file on each startup. As
- gitlab-shell has now been changed to use
- /var/run/current-system/sw/bin/gitlab-shell,
- this is not necessary anymore, but there might be leftover
- lines with a nix store path. Regenerate the
- authorized_keys file via
- sudo -u git -H gitlab-rake gitlab:shell:setup
- in that case.
-
-
-
-
- The pam_unix account module is now loaded
- with its control field set to required
- instead of sufficient, so that later PAM
- account modules that might do more extensive checks are being
- executed. Previously, the whole account module verification
- was exited prematurely in case a nss module provided the
- account name to pam_unix. The LDAP and SSSD
- NixOS modules already add their NSS modules when enabled. In
- case your setup breaks due to some later PAM account module
- previosuly shadowed, or failing NSS lookups, please file a
- bug. You can get back the old behaviour by manually setting
- security.pam.services.<name?>.text.
-
-
-
-
- The pam_unix password module is now loaded
- with its control field set to sufficient
- instead of required, so that password
- managed only by later PAM password modules are being executed.
- Previously, for example, changing an LDAP account’s password
- through PAM was not possible: the whole password module
- verification was exited prematurely by
- pam_unix, preventing
- pam_ldap to manage the password as it
- should.
-
-
-
-
- fish has been upgraded to 3.0. It comes
- with a number of improvements and backwards incompatible
- changes. See the fish
- release
- notes for more information.
-
-
-
-
- The ibus-table input method has had a change in config format,
- which causes all previous settings to be lost. See
- this
- commit message for details.
-
-
-
-
- NixOS module system type types.optionSet
- and lib.mkOption argument
- options are deprecated. Use
- types.submodule instead.
- (#54637)
-
-
-
-
- matrix-synapse has been updated to version
- 0.99. It will
- no
- longer generate a self-signed certificate on first
- launch and will be
- the
- last version to accept self-signed certificates. As
- such, it is now recommended to use a proper certificate
- verified by a root CA (for example Let’s Encrypt). The new
- manual chapter on
- Matrix contains a working example of using nginx as a
- reverse proxy in front of matrix-synapse,
- using Let’s Encrypt certificates.
-
-
-
-
- mailutils now works by default when
- sendmail is not in a setuid wrapper. As a
- consequence, the sendmailPath argument,
- having lost its main use, has been removed.
-
-
-
-
- graylog has been upgraded from version 2.*
- to 3.*. Some setups making use of extraConfig (especially
- those exposing Graylog via reverse proxies) need to be updated
- as upstream removed/replaced some settings. See
- Upgrading
- Graylog for details.
-
-
-
-
- The option users.ldap.bind.password was
- renamed to users.ldap.bind.passwordFile,
- and needs to be readable by the nslcd user.
- Same applies to the new
- users.ldap.daemon.rootpwmodpwFile option.
-
-
-
-
- nodejs-6_x is end-of-life.
- nodejs-6_x,
- nodejs-slim-6_x and
- nodePackages_6_x are removed.
-
-
-
-
-
- Other Notable Changes
-
-
-
- The services.matomo module gained the
- option services.matomo.package which
- determines the used Matomo version.
-
-
- The Matomo module now also comes with the systemd service
- matomo-archive-processing.service and a
- timer that automatically triggers archive processing every
- hour. This means that you can safely
-
- disable browser triggers for Matomo archiving at
- Administration > System > General Settings.
-
-
- Additionally, you can enable to
-
- delete old visitor logs at
- Administration > System > Privacy,
- but make sure that you run
- systemctl start matomo-archive-processing.service
- at least once without errors if you have already collected
- data before, so that the reports get archived before the
- source data gets deleted.
-
-
-
-
- composableDerivation along with supporting
- library functions has been removed.
-
-
-
-
- The deprecated truecrypt package has been
- removed and truecrypt attribute is now an
- alias for veracrypt. VeraCrypt is
- backward-compatible with TrueCrypt volumes. Note that
- cryptsetup also supports loading TrueCrypt
- volumes.
-
-
-
-
- The Kubernetes DNS addons, kube-dns, has been replaced with
- CoreDNS. This change is made in accordance with Kubernetes
- making CoreDNS the official default starting from
- Kubernetes
- v1.11. Please beware that upgrading DNS-addon on
- existing clusters might induce minor downtime while the
- DNS-addon terminates and re-initializes. Also note that the
- DNS-service now runs with 2 pod replicas by default. The
- desired number of replicas can be configured using:
- services.kubernetes.addons.dns.replicas.
-
-
-
-
- The quassel-webserver package and module was removed from
- nixpkgs due to the lack of maintainers.
-
-
-
-
- The manual gained a
- new chapter on self-hosting matrix-synapse
- and riot-web , the most prevalent
- server and client implementations for the
- Matrix federated
- communication network.
-
-
-
-
- The astah-community package was removed from nixpkgs due to it
- being discontinued and the downloads not being available
- anymore.
-
-
-
-
- The httpd service now saves log files with a .log file
- extension by default for easier integration with the logrotate
- service.
-
-
-
-
- The owncloud server packages and httpd subservice module were
- removed from nixpkgs due to the lack of maintainers.
-
-
-
-
- It is possible now to uze ZRAM devices as general purpose
- ephemeral block devices, not only as swap. Using more than 1
- device as ZRAM swap is no longer recommended, but is still
- possible by setting zramSwap.swapDevices
- explicitly.
-
-
- ZRAM algorithm can be changed now.
-
-
- Changes to ZRAM algorithm are applied during
- nixos-rebuild switch, so make sure you have
- enough swap space on disk to survive ZRAM device rebuild.
- Alternatively, use
- nixos-rebuild boot; reboot.
-
-
-
-
- Flat volumes are now disabled by default in
- hardware.pulseaudio. This has been done to
- prevent applications, which are unaware of this feature,
- setting their volumes to 100% on startup causing harm to your
- audio hardware and potentially your ears.
-
-
-
- With this change application specific volumes are relative
- to the master volume which can be adjusted independently,
- whereas before they were absolute; meaning that in effect,
- it scaled the device-volume with the volume of the loudest
- application.
-
-
-
-
-
- The
- ndppd
- module now supports
- all
- config options provided by the current upstream version
- as service options. Additionally the ndppd
- package doesn’t contain the systemd unit configuration from
- upstream anymore, the unit is completely configured by the
- NixOS module now.
-
-
-
-
- New installs of NixOS will default to the Redmine 4.x series
- unless otherwise specified in
- services.redmine.package while existing
- installs of NixOS will default to the Redmine 3.x series.
-
-
-
-
- The
- Grafana
- module now supports declarative
- datasource
- and dashboard provisioning.
-
-
-
-
- The use of insecure ports on kubernetes has been deprecated.
- Thus options:
- services.kubernetes.apiserver.port and
- services.kubernetes.controllerManager.port
- has been renamed to .insecurePort, and
- default of both options has changed to 0 (disabled).
-
-
-
-
- Note that the default value of
- services.kubernetes.apiserver.bindAddress
- has changed from 127.0.0.1 to 0.0.0.0, allowing the apiserver
- to be accessible from outside the master node itself. If the
- apiserver insecurePort is enabled, it is strongly recommended
- to only bind on the loopback interface. See:
- services.kubernetes.apiserver.insecurebindAddress.
-
-
-
-
- The option
- services.kubernetes.apiserver.allowPrivileged
- and
- services.kubernetes.kubelet.allowPrivileged
- now defaults to false. Disallowing privileged containers on
- the cluster.
-
-
-
-
- The kubernetes module does no longer add the kubernetes
- package to environment.systemPackages
- implicitly.
-
-
-
-
- The intel driver has been removed from the
- default list of
- X.org
- video drivers. The modesetting
- driver should take over automatically, it is better maintained
- upstream and has less problems with advanced X11 features.
- This can lead to a change in the output names used by
- xrandr. Some performance regressions on
- some GPU models might happen. Some OpenCL and VA-API
- applications might also break (Beignet seems to provide OpenCL
- support with modesetting driver, too).
- Kernel mode setting API does not support backlight control, so
- xbacklight tool will not work; backlight
- level can be controlled directly via /sys/
- or with brightnessctl. Users who need this
- functionality more than multi-output XRandR are advised to add
- `intel` to `videoDrivers` and report an issue (or provide
- additional details in an existing one)
-
-
-
-
- Openmpi has been updated to version 4.0.0, which removes some
- deprecated MPI-1 symbols. This may break some older
- applications that still rely on those symbols. An upgrade
- guide can be found
- here.
-
-
- The nginx package now relies on OpenSSL 1.1 and supports TLS
- 1.3 by default. You can set the protocols used by the nginx
- service using
- services.nginx.sslProtocols.
-
-
-
-
- A new subcommand nixos-rebuild edit was
- added.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-1909.section.xml b/nixos/doc/manual/from_md/release-notes/rl-1909.section.xml
deleted file mode 100644
index 3bf83e1eccbd..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-1909.section.xml
+++ /dev/null
@@ -1,1197 +0,0 @@
-
- Release 19.09 (<quote>Loris</quote>, 2019/10/09)
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- End of support is planned for end of April 2020, handing over
- to 20.03.
-
-
-
-
- Nix has been updated to 2.3; see its
- release
- notes.
-
-
-
-
- Core version changes:
-
-
- systemd: 239 -> 243
-
-
- gcc: 7 -> 8
-
-
- glibc: 2.27 (unchanged)
-
-
- linux: 4.19 LTS (unchanged)
-
-
- openssl: 1.0 -> 1.1
-
-
-
-
- Desktop version changes:
-
-
- plasma5: 5.14 -> 5.16
-
-
- gnome3: 3.30 -> 3.32
-
-
-
-
- PHP now defaults to PHP 7.3, updated from 7.2.
-
-
-
-
- PHP 7.1 is no longer supported due to upstream not supporting
- this version for the entire lifecycle of the 19.09 release.
-
-
-
-
- The binfmt module is now easier to use. Additional systems can
- be added through
- boot.binfmt.emulatedSystems. For instance,
- boot.binfmt.emulatedSystems = [ "wasm32-wasi" "x86_64-windows" "aarch64-linux" ];
- will set up binfmt interpreters for each of those listed
- systems.
-
-
-
-
- The installer now uses a less privileged
- nixos user whereas before we logged in as
- root. To gain root privileges use sudo -i
- without a password.
-
-
-
-
- We’ve updated to Xfce 4.14, which brings a new module
- services.xserver.desktopManager.xfce4-14.
- If you’d like to upgrade, please switch from the
- services.xserver.desktopManager.xfce module
- as it will be deprecated in a future release. They’re
- incompatibilities with the current Xfce module; it doesn’t
- support thunarPlugins and it isn’t
- recommended to use
- services.xserver.desktopManager.xfce and
- services.xserver.desktopManager.xfce4-14
- simultaneously or to downgrade from Xfce 4.14 after upgrading.
-
-
-
-
- The GNOME 3 desktop manager module sports an interface to
- enable/disable core services, applications, and optional GNOME
- packages like games.
-
-
-
-
- services.gnome3.core-os-services.enable
-
-
-
-
- services.gnome3.core-shell.enable
-
-
-
-
- services.gnome3.core-utilities.enable
-
-
-
-
- services.gnome3.games.enable
-
-
-
-
- With these options we hope to give users finer grained control
- over their systems. Prior to this change you’d either have to
- manually disable options or use
- environment.gnome3.excludePackages which
- only excluded the optional applications.
- environment.gnome3.excludePackages is now
- unguarded, it can exclude any package installed with
- environment.systemPackages in the GNOME 3
- module.
-
-
-
-
- Orthogonal to the previous changes to the GNOME 3 desktop
- manager module, we’ve updated all default services and
- applications to match as close as possible to a default
- reference GNOME 3 experience.
-
-
- The following changes were enacted in
- services.gnome3.core-utilities.enable
-
-
-
-
- accerciser
-
-
-
-
- dconf-editor
-
-
-
-
- evolution
-
-
-
-
- gnome-documents
-
-
-
-
- gnome-nettool
-
-
-
-
- gnome-power-manager
-
-
-
-
- gnome-todo
-
-
-
-
- gnome-tweaks
-
-
-
-
- gnome-usage
-
-
-
-
- gucharmap
-
-
-
-
- nautilus-sendto
-
-
-
-
- vinagre
-
-
-
-
- cheese
-
-
-
-
- geary
-
-
-
-
- The following changes were enacted in
- services.gnome3.core-shell.enable
-
-
-
-
- gnome-color-manager
-
-
-
-
- orca
-
-
-
-
- services.avahi.enable
-
-
-
-
-
-
-
- New Services
-
- The following new services were added since the last release:
-
-
-
-
- ./programs/dwm-status.nix
-
-
-
-
- The new hardware.printers module allows to
- declaratively configure CUPS printers via the
- ensurePrinters and
- ensureDefaultPrinter options.
- ensurePrinters will never delete existing
- printers, but will make sure that the given printers are
- configured as declared.
-
-
-
-
- There is a new
- services.system-config-printer.enable
- and
- programs.system-config-printer.enable
- module for the program of the same name. If you previously had
- system-config-printer enabled through some
- other means you should migrate to using one of these modules.
-
-
-
-
- services.xserver.desktopManager.plasma5
-
-
-
-
- services.xserver.desktopManager.gnome3
-
-
-
-
- services.xserver.desktopManager.pantheon
-
-
-
-
- services.xserver.desktopManager.mate
- Note Mate uses
- programs.system-config-printer as it
- doesn’t use it as a service, but its graphical interface
- directly.
-
-
-
-
-
-
- services.blueman.enable
- has been added. If you previously had blueman installed via
- environment.systemPackages please migrate
- to using the NixOS module, as this would result in an
- insufficiently configured blueman.
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- Buildbot no longer supports Python 2, as support was dropped
- upstream in version 2.0.0. Configurations may need to be
- modified to make them compatible with Python 3.
-
-
-
-
- PostgreSQL now uses /run/postgresql as its
- socket directory instead of /tmp. So if you
- run an application like eg. Nextcloud, where you need to use
- the Unix socket path as the database host name, you need to
- change it accordingly.
-
-
-
-
- PostgreSQL 9.4 is scheduled EOL during the 19.09 life cycle
- and has been removed.
-
-
-
-
- The options
- services.prometheus.alertmanager.user and
- services.prometheus.alertmanager.group have
- been removed because the alertmanager service is now using
- systemd’s
-
- DynamicUser mechanism which obviates these options.
-
-
-
-
- The NetworkManager systemd unit was renamed back from
- network-manager.service to NetworkManager.service for better
- compatibility with other applications expecting this name. The
- same applies to ModemManager where modem-manager.service is
- now called ModemManager.service again.
-
-
-
-
- The services.nzbget.configFile and
- services.nzbget.openFirewall options were
- removed as they are managed internally by the nzbget. The
- services.nzbget.dataDir option hadn’t
- actually been used by the module for some time and so was
- removed as cleanup.
-
-
-
-
- The services.mysql.pidDir option was
- removed, as it was only used by the wordpress apache-httpd
- service to wait for mysql to have started up. This can be
- accomplished by either describing a dependency on
- mysql.service (preferred) or waiting for the (hardcoded)
- /run/mysqld/mysql.sock file to appear.
-
-
-
-
- The services.emby.enable module has been
- removed, see services.jellyfin.enable
- instead for a free software fork of Emby. See the Jellyfin
- documentation:
-
- Migrating from Emby to Jellyfin
-
-
-
-
- IPv6 Privacy Extensions are now enabled by default for
- undeclared interfaces. The previous behaviour was quite
- misleading — even though the default value for
- networking.interfaces.*.preferTempAddress
- was true, undeclared interfaces would not
- prefer temporary addresses. Now, interfaces not mentioned in
- the config will prefer temporary addresses. EUI64 addresses
- can still be set as preferred by explicitly setting the option
- to false for the interface in question.
-
-
-
-
- Since Bittorrent Sync was superseded by Resilio Sync in 2016,
- the bittorrentSync,
- bittorrentSync14, and
- bittorrentSync16 packages have been removed
- in favor of resilio-sync.
-
-
- The corresponding module, services.btsync
- has been replaced by the services.resilio
- module.
-
-
-
-
- The httpd service no longer attempts to start the postgresql
- service. If you have come to depend on this behaviour then you
- can preserve the behavior with the following configuration:
- systemd.services.httpd.after = [ "postgresql.service" ];
-
-
- The option services.httpd.extraSubservices
- has been marked as deprecated. You may still use this feature,
- but it will be removed in a future release of NixOS. You are
- encouraged to convert any httpd subservices you may have
- written to a full NixOS module.
-
-
- Most of the httpd subservices packaged with NixOS have been
- replaced with full NixOS modules including LimeSurvey,
- WordPress, and Zabbix. These modules can be enabled using the
- services.limesurvey.enable,
- services.mediawiki.enable,
- services.wordpress.enable, and
- services.zabbixWeb.enable options.
-
-
-
-
- The option
- systemd.network.networks.<name>.routes.*.routeConfig.GatewayOnlink
- was renamed to
- systemd.network.networks.<name>.routes.*.routeConfig.GatewayOnLink
- (capital L). This follows
-
- upstreams renaming of the setting.
-
-
-
-
- As of this release the NixOps feature
- autoLuks is deprecated. It no longer works
- with our systemd version without manual intervention.
-
-
- Whenever the usage of the module is detected the evaluation
- will fail with a message explaining why and how to deal with
- the situation.
-
-
- A new knob named
- nixops.enableDeprecatedAutoLuks has been
- introduced to disable the eval failure and to acknowledge the
- notice was received and read. If you plan on using the feature
- please note that it might break with subsequent updates.
-
-
- Make sure you set the _netdev option for
- each of the file systems referring to block devices provided
- by the autoLuks module. Not doing this might render the system
- in a state where it doesn’t boot anymore.
-
-
- If you are actively using the autoLuks
- module please let us know in
- issue
- #62211.
-
-
-
-
- The setopt declarations will be evaluated at the end of
- /etc/zshrc, so any code in
- programs.zsh.interactiveShellInit,
- programs.zsh.loginShellInit
- and
- programs.zsh.promptInit
- may break if it relies on those options being set.
-
-
-
-
- The prometheus-nginx-exporter package now
- uses the official exporter provided by NGINX Inc. Its metrics
- are differently structured and are incompatible to the old
- ones. For information about the metrics, have a look at the
- official
- repo.
-
-
-
-
- The shibboleth-sp package has been updated
- to version 3. It is largely backward compatible, for further
- information refer to the
- release
- notes and
- upgrade
- guide.
-
-
- Nodejs 8 is scheduled EOL under the lifetime of 19.09 and has
- been dropped.
-
-
-
-
- By default, prometheus exporters are now run with
- DynamicUser enabled. Exporters that need a
- real user, now run under a separate user and group which
- follow the pattern
- <exporter-name>-exporter, instead of
- the previous default nobody and
- nogroup. Only some exporters are affected
- by the latter, namely the exporters
- dovecot, node,
- postfix and varnish.
-
-
-
-
- The ibus-qt package is not installed by
- default anymore when
- i18n.inputMethod.enabled
- is set to ibus. If IBus support in Qt 4.x
- applications is required, add the ibus-qt
- package to your
- environment.systemPackages
- manually.
-
-
-
-
- The CUPS Printing service now uses socket-based activation by
- default, only starting when needed. The previous behavior can
- be restored by setting
- services.cups.startWhenNeeded to
- false.
-
-
-
-
- The services.systemhealth module has been
- removed from nixpkgs due to lack of maintainer.
-
-
-
-
- The services.mantisbt module has been
- removed from nixpkgs due to lack of maintainer.
-
-
-
-
- Squid 3 has been removed and the squid
- derivation now refers to Squid 4.
-
-
-
-
- The services.pdns-recursor.extraConfig
- option has been replaced by
- services.pdns-recursor.settings. The new
- option allows setting extra configuration while being better
- type-checked and mergeable.
-
-
-
-
- No service depends on keys.target anymore
- which is a systemd target that indicates if all
- NixOps
- keys were successfully uploaded. Instead,
- <key-name>-key.service should be used
- to define a dependency of a key in a service. The full issue
- behind the keys.target dependency is
- described at
- NixOS/nixpkgs#67265.
-
-
- The following services are affected by this:
-
-
-
-
- services.dovecot2
-
-
-
-
- services.nsd
-
-
-
-
- services.softether
-
-
-
-
- services.strongswan
-
-
-
-
- services.strongswan-swanctl
-
-
-
-
- services.httpd
-
-
-
-
-
-
- The security.acme.directory option has been
- replaced by a read-only
- security.acme.certs.<cert>.directory
- option for each certificate you define. This will be a
- subdirectory of /var/lib/acme. You can use
- this read-only option to figure out where the certificates are
- stored for a specific certificate. For example, the
- services.nginx.virtualhosts.<name>.enableACME
- option will use this directory option to find the certs for
- the virtual host.
-
-
- security.acme.preDelay and
- security.acme.activationDelay options have
- been removed. To execute a service before certificates are
- provisioned or renewed add a
- RequiredBy=acme-${cert}.service to any
- service.
-
-
- Furthermore, the acme module will not automatically add a
- dependency on lighttpd.service anymore. If
- you are using certficates provided by letsencrypt for
- lighttpd, then you should depend on the certificate service
- acme-${cert}.service> manually.
-
-
- For nginx, the dependencies are still automatically managed
- when
- services.nginx.virtualhosts.<name>.enableACME
- is enabled just like before. What changed is that nginx now
- directly depends on the specific certificates that it needs,
- instead of depending on the catch-all
- acme-certificates.target. This target unit
- was also removed from the codebase. This will mean nginx will
- no longer depend on certificates it isn’t explicitly managing
- and fixes a bug with certificate renewal ordering racing with
- nginx restarting which could lead to nginx getting in a broken
- state as described at
- NixOS/nixpkgs#60180.
-
-
-
-
- The old deprecated emacs package sets have
- been dropped. What used to be called
- emacsPackagesNg is now simply called
- emacsPackages.
-
-
-
-
- services.xserver.desktopManager.xterm is
- now disabled by default if stateVersion is
- 19.09 or higher. Previously the xterm desktopManager was
- enabled when xserver was enabled, but it isn’t useful for all
- people so it didn’t make sense to have any desktopManager
- enabled default.
-
-
-
-
- The WeeChat plugin
- pkgs.weechatScripts.weechat-xmpp has been
- removed as it doesn’t receive any updates from upstream and
- depends on outdated Python2-based modules.
-
-
-
-
- Old unsupported versions (logstash5,
- kibana5, filebeat5,
- heartbeat5, metricbeat5,
- packetbeat5) of the ELK-stack and Elastic
- beats have been removed.
-
-
-
-
- For NixOS 19.03, both Prometheus 1 and 2 were available to
- allow for a seamless transition from version 1 to 2 with
- existing setups. Because Prometheus 1 is no longer developed,
- it was removed. Prometheus 2 is now configured with
- services.prometheus.
-
-
-
-
- Citrix Receiver (citrix_receiver) has been
- dropped in favor of Citrix Workspace
- (citrix_workspace).
-
-
-
-
- The services.gitlab module has had its
- literal secret options
- (services.gitlab.smtp.password,
- services.gitlab.databasePassword,
- services.gitlab.initialRootPassword,
- services.gitlab.secrets.secret,
- services.gitlab.secrets.db,
- services.gitlab.secrets.otp and
- services.gitlab.secrets.jws) replaced by
- file-based versions
- (services.gitlab.smtp.passwordFile,
- services.gitlab.databasePasswordFile,
- services.gitlab.initialRootPasswordFile,
- services.gitlab.secrets.secretFile,
- services.gitlab.secrets.dbFile,
- services.gitlab.secrets.otpFile and
- services.gitlab.secrets.jwsFile). This was
- done so that secrets aren’t stored in the world-readable nix
- store, but means that for each option you’ll have to create a
- file with the same exact string, add File to
- the end of the option name, and change the definition to a
- string pointing to the corresponding file; e.g.
- services.gitlab.databasePassword = "supersecurepassword"
- becomes
- services.gitlab.databasePasswordFile = "/path/to/secret_file"
- where the file secret_file contains the
- string supersecurepassword.
-
-
- The state path (services.gitlab.statePath)
- now has the following restriction: no parent directory can be
- owned by any other user than root or the
- user specified in services.gitlab.user;
- i.e. if services.gitlab.statePath is set to
- /var/lib/gitlab/state,
- gitlab and all parent directories must be
- owned by either root or the user specified
- in services.gitlab.user.
-
-
-
-
- The networking.useDHCP option is
- unsupported in combination with
- networking.useNetworkd in anticipation of
- defaulting to it. It has to be set to false
- and enabled per interface with
- networking.interfaces.<name>.useDHCP = true;
-
-
-
-
- The Twitter client corebird has been
- dropped as
- it
- is discontinued and does not work against the new Twitter
- API. Please use the fork cawbird
- instead which has been adapted to the API changes and is still
- maintained.
-
-
-
-
- The nodejs-11_x package has been removed as
- it’s EOLed by upstream.
-
-
-
-
- Because of the systemd upgrade, systemd-timesyncd will no
- longer work if system.stateVersion is not
- set correctly. When upgrading from NixOS 19.03, please make
- sure that system.stateVersion is set to
- "19.03", or lower if the
- installation dates back to an earlier version of NixOS.
-
-
-
-
- Due to the short lifetime of non-LTS kernel releases package
- attributes like linux_5_1,
- linux_5_2 and linux_5_3
- have been removed to discourage dependence on specific non-LTS
- kernel versions in stable NixOS releases. Going forward,
- versioned attributes like linux_4_9 will
- exist for LTS versions only. Please use
- linux_latest or
- linux_testing if you depend on non-LTS
- releases. Keep in mind that linux_latest
- and linux_testing will change versions
- under the hood during the lifetime of a stable release and
- might include breaking changes.
-
-
-
-
- Because of the systemd upgrade, some network interfaces might
- change their name. For details see
-
- upstream docs or
-
- our ticket.
-
-
-
-
-
- Other Notable Changes
-
-
-
- The documentation module gained an option
- named documentation.nixos.includeAllModules
- which makes the generated configuration.nix 5 manual page
- include all options from all NixOS modules included in a given
- configuration.nix configuration file.
- Currently, it is set to false by default as
- enabling it frequently prevents evaluation. But the plan is to
- eventually have it set to true by default.
- Please set it to true now in your
- configuration.nix and fix all the bugs it
- uncovers.
-
-
-
-
- The vlc package gained support for
- Chromecast streaming, enabled by default. TCP port 8010 must
- be open for it to work, so something like
- networking.firewall.allowedTCPPorts = [ 8010 ];
- may be required in your configuration. Also consider enabling
-
- Accelerated Video Playback for better transcoding
- performance.
-
-
-
-
- The following changes apply if the
- stateVersion is changed to 19.09 or higher.
- For stateVersion = "19.03" or
- lower the old behavior is preserved.
-
-
-
-
- solr.package defaults to
- pkgs.solr_8.
-
-
-
-
-
-
- The hunspellDicts.fr-any dictionary now
- ships with fr_FR.{aff,dic} which is linked
- to fr-toutesvariantes.{aff,dic}.
-
-
-
-
- The mysql service now runs as
- mysql user. Previously, systemd did execute
- it as root, and mysql dropped privileges itself. This includes
- ExecStartPre= and
- ExecStartPost= phases. To accomplish that,
- runtime and data directory setup was delegated to
- RuntimeDirectory and tmpfiles.
-
-
-
-
- With the upgrade to systemd version 242 the
- systemd-timesyncd service is no longer
- using DynamicUser=yes. In order for the
- upgrade to work we rely on an activation script to move the
- state from the old to the new directory. The older directory
- (prior 19.09) was
- /var/lib/private/systemd/timesync.
-
-
- As long as the system.config.stateVersion
- is below 19.09 the state folder will
- migrated to its proper location
- (/var/lib/systemd/timesync), if required.
-
-
-
-
- The package avahi is now built to look up
- service definitions from
- /etc/avahi/services instead of its output
- directory in the nix store. Accordingly the module
- avahi now supports custom service
- definitions via
- services.avahi.extraServiceFiles, which are
- then placed in the aforementioned directory. See
- avahi.service5 for more information on custom service
- definitions.
-
-
-
-
- Since version 0.1.19, cargo-vendor honors
- package includes that are specified in the
- Cargo.toml file of Rust crates.
- rustPlatform.buildRustPackage uses
- cargo-vendor to collect and build dependent
- crates. Since this change in cargo-vendor
- changes the set of vendored files for most Rust packages, the
- hash that use used to verify the dependencies,
- cargoSha256, also changes.
-
-
- The cargoSha256 hashes of all in-tree
- derivations that use buildRustPackage have
- been updated to reflect this change. However, third-party
- derivations that use buildRustPackage may
- have to be updated as well.
-
-
-
-
- The consul package was upgraded past
- version 1.5, so its deprecated legacy UI is
- no longer available.
-
-
-
-
- The default resample-method for PulseAudio has been changed
- from the upstream default speex-float-1 to
- speex-float-5. Be aware that low-powered
- ARM-based and MIPS-based boards will struggle with this so
- you’ll need to set
- hardware.pulseaudio.daemon.config.resample-method
- back to speex-float-1.
-
-
-
-
- The phabricator package and associated
- httpd.extraSubservice, as well as the
- phd service have been removed from nixpkgs
- due to lack of maintainer.
-
-
-
-
- The mercurial
- httpd.extraSubservice has been removed from
- nixpkgs due to lack of maintainer.
-
-
-
-
- The trac
- httpd.extraSubservice has been removed from
- nixpkgs because it was unmaintained.
-
-
-
-
- The foswiki package and associated
- httpd.extraSubservice have been removed
- from nixpkgs due to lack of maintainer.
-
-
-
-
- The tomcat-connector
- httpd.extraSubservice has been removed from
- nixpkgs.
-
-
-
-
- It’s now possible to change configuration in
- services.nextcloud
- after the initial deploy since all config parameters are
- persisted in an additional config file generated by the
- module. Previously core configuration like database parameters
- were set using their imperative installer after creating
- /var/lib/nextcloud.
-
-
-
-
- There exists now lib.forEach, which is like
- map, but with arguments flipped. When
- mapping function body spans many lines (or has nested
- maps), it is often hard to follow which
- list is modified.
-
-
- Previous solution to this problem was either to use
- lib.flip map idiom or extract that
- anonymous mapping function to a named one. Both can still be
- used but lib.forEach is preferred over
- lib.flip map.
-
-
- The /etc/sysctl.d/nixos.conf file
- containing all the options set via
- boot.kernel.sysctl
- was moved to /etc/sysctl.d/60-nixos.conf,
- as sysctl.d5 recommends prefixing all filenames in
- /etc/sysctl.d with a two-digit number and a
- dash to simplify the ordering of the files.
-
-
-
-
- We now install the sysctl snippets shipped with systemd.
-
-
-
-
- Loose reverse path filtering
-
-
-
-
- Source route filtering
-
-
-
-
- fq_codel as a packet scheduler (this
- helps to fight bufferbloat)
-
-
-
-
- This also configures the kernel to pass core dumps to
- systemd-coredump, and restricts the SysRq
- key combinations to the sync command only. These sysctl
- snippets can be found in
- /etc/sysctl.d/50-*.conf, and overridden via
- boot.kernel.sysctl
- (which will place the parameters in
- /etc/sysctl.d/60-nixos.conf).
-
-
-
-
- Core dumps are now processed by
- systemd-coredump by default.
- systemd-coredump behaviour can still be
- modified via systemd.coredump.extraConfig.
- To stick to the old behaviour (having the kernel dump to a
- file called core in the working directory),
- without piping it through systemd-coredump,
- set systemd.coredump.enable to
- false.
-
-
-
-
- systemd.packages option now also supports
- generators and shutdown scripts. Old
- systemd.generator-packages option has been
- removed.
-
-
-
-
- The rmilter package was removed with
- associated module and options due deprecation by upstream
- developer. Use rspamd in proxy mode
- instead.
-
-
-
-
- systemd cgroup accounting via the
- systemd.enableCgroupAccounting
- option is now enabled by default. It now also enables the more
- recent Block IO and IP accounting features.
-
-
-
-
- We no longer enable custom font rendering settings with
- fonts.fontconfig.penultimate.enable by
- default. The defaults from fontconfig are sufficient.
-
-
-
-
- The crashplan package and the
- crashplan service have been removed from
- nixpkgs due to crashplan shutting down the service, while the
- crashplansb package and
- crashplan-small-business service have been
- removed from nixpkgs due to lack of maintainer.
-
-
- The
- redis
- module was hardcoded to use the
- redis user, /run/redis
- as runtime directory and /var/lib/redis as
- state directory. Note that the NixOS module for Redis now
- disables kernel support for Transparent Huge Pages (THP),
- because this features causes major performance problems for
- Redis, e.g. (https://redis.io/topics/latency).
-
-
-
-
- Using fonts.enableDefaultFonts adds a
- default emoji font noto-fonts-emoji.
-
-
-
-
- services.xserver.enable
-
-
-
-
- programs.sway.enable
-
-
-
-
- programs.way-cooler.enable
-
-
-
-
- services.xrdp.enable
-
-
-
-
-
-
- The altcoins categorization of packages has
- been removed. You now access these packages at the top level,
- ie. nix-shell -p dogecoin instead of
- nix-shell -p altcoins.dogecoin, etc.
-
-
-
-
- Ceph has been upgraded to v14.2.1. See the
- release
- notes for details. The mgr dashboard as well as osds
- backed by loop-devices is no longer explicitly supported by
- the package and module. Note: There’s been some issues with
- python-cherrypy, which is used by the dashboard and prometheus
- mgr modules (and possibly others), hence
- 0000-dont-check-cherrypy-version.patch.
-
-
-
-
- pkgs.weechat is now compiled against
- pkgs.python3. Weechat also recommends
- to use
- Python3 in their docs.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-2003.section.xml b/nixos/doc/manual/from_md/release-notes/rl-2003.section.xml
deleted file mode 100644
index 35fbb7447c70..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-2003.section.xml
+++ /dev/null
@@ -1,1497 +0,0 @@
-
- Release 20.03 (<quote>Markhor</quote>, 2020.04/20)
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- Support is planned until the end of October 2020, handing over
- to 20.09.
-
-
-
-
- Core version changes:
-
-
- gcc: 8.3.0 -> 9.2.0
-
-
- glibc: 2.27 -> 2.30
-
-
- linux: 4.19 -> 5.4
-
-
- mesa: 19.1.5 -> 19.3.3
-
-
- openssl: 1.0.2u -> 1.1.1d
-
-
-
-
- Desktop version changes:
-
-
- plasma5: 5.16.5 -> 5.17.5
-
-
- kdeApplications: 19.08.2 -> 19.12.3
-
-
- gnome3: 3.32 -> 3.34
-
-
- pantheon: 5.0 -> 5.1.3
-
-
-
-
- Linux kernel is updated to branch 5.4 by default (from 4.19).
-
-
-
-
- Grub is updated to 2.04, adding support for booting from F2FS
- filesystems and Btrfs volumes using zstd compression. Note
- that some users have been unable to boot after upgrading to
- 2.04 - for more information, please see
- this
- discussion.
-
-
-
-
- Postgresql for NixOS service now defaults to v11.
-
-
-
-
- The graphical installer image starts the graphical session
- automatically. Before you’d be greeted by a tty and asked to
- enter systemctl start display-manager. It
- is now possible to disable the display-manager from running by
- selecting the Disable display-manager quirk
- in the boot menu.
-
-
-
-
- GNOME 3 has been upgraded to 3.34. Please take a look at their
- Release
- Notes for details.
-
-
-
-
- If you enable the Pantheon Desktop Manager via
- services.xserver.desktopManager.pantheon.enable,
- we now default to also use
-
- Pantheon’s newly designed greeter . Contrary to NixOS’s
- usual update policy, Pantheon will receive updates during the
- cycle of NixOS 20.03 when backwards compatible.
-
-
-
-
- By default zfs pools will now be trimmed on a weekly basis.
- Trimming is only done on supported devices (i.e. NVME or SSDs)
- and should improve throughput and lifetime of these devices.
- It is controlled by the
- services.zfs.trim.enable varname. The zfs
- scrub service
- (services.zfs.autoScrub.enable) and the zfs
- autosnapshot service
- (services.zfs.autoSnapshot.enable) are now
- only enabled if zfs is set in
- config.boot.initrd.supportedFilesystems or
- config.boot.supportedFilesystems. These
- lists will automatically contain zfs as soon as any zfs
- mountpoint is configured in fileSystems.
-
-
-
-
- nixos-option has been rewritten in C++,
- speeding it up, improving correctness, and adding a
- -r option which prints all options and
- their values recursively.
-
-
-
-
- services.xserver.desktopManager.default and
- services.xserver.windowManager.default
- options were replaced by a single
- services.xserver.displayManager.defaultSession
- option to improve support for upstream session files. If you
- used something like:
-
-
-{
- services.xserver.desktopManager.default = "xfce";
- services.xserver.windowManager.default = "icewm";
-}
-
-
- you should change it to:
-
-
-{
- services.xserver.displayManager.defaultSession = "xfce+icewm";
-}
-
-
-
-
- The testing driver implementation in NixOS is now in Python
- make-test-python.nix. This was done by
- Jacek Galowicz
- (@tfc), and
- with the collaboration of Julian Stecklina
- (@blitz)
- and Jana Traue
- (@jtraue).
- All documentation has been updated to use this testing driver,
- and a vast majority of the 286 tests in NixOS were ported to
- python driver. In 20.09 the Perl driver implementation,
- make-test.nix, is slated for removal. This
- should give users of the NixOS integration framework a
- transitory period to rewrite their tests to use the Python
- implementation. Users of the Perl driver will see this warning
- everytime they use it:
-
-
-$ warning: Perl VM tests are deprecated and will be removed for 20.09.
-Please update your tests to use the python test driver.
-See https://github.com/NixOS/nixpkgs/pull/71684 for details.
-
-
- API compatibility is planned to be kept for at least the next
- release with the perl driver.
-
-
-
-
-
- New Services
-
- The following new services were added since the last release:
-
-
-
-
- The kubernetes kube-proxy now supports a new hostname
- configuration
- services.kubernetes.proxy.hostname which
- has to be set if the hostname of the node should be non
- default.
-
-
-
-
- UPower’s configuration is now managed by NixOS and can be
- customized via services.upower.
-
-
-
-
- To use Geary you should enable
- programs.geary.enable
- instead of just adding it to
- environment.systemPackages.
- It was created so Geary could function properly outside of
- GNOME.
-
-
-
-
- ./config/console.nix
-
-
-
-
- ./hardware/brillo.nix
-
-
-
-
- ./hardware/tuxedo-keyboard.nix
-
-
-
-
- ./programs/bandwhich.nix
-
-
-
-
- ./programs/bash-my-aws.nix
-
-
-
-
- ./programs/liboping.nix
-
-
-
-
- ./programs/traceroute.nix
-
-
-
-
- ./services/backup/sanoid.nix
-
-
-
-
- ./services/backup/syncoid.nix
-
-
-
-
- ./services/backup/zfs-replication.nix
-
-
-
-
- ./services/continuous-integration/buildkite-agents.nix
-
-
-
-
- ./services/databases/victoriametrics.nix
-
-
-
-
- ./services/desktops/gnome3/gnome-initial-setup.nix
-
-
-
-
- ./services/desktops/neard.nix
-
-
-
-
- ./services/games/openarena.nix
-
-
-
-
- ./services/hardware/fancontrol.nix
-
-
-
-
- ./services/mail/sympa.nix
-
-
-
-
- ./services/misc/freeswitch.nix
-
-
-
-
- ./services/misc/mame.nix
-
-
-
-
- ./services/monitoring/do-agent.nix
-
-
-
-
- ./services/monitoring/prometheus/xmpp-alerts.nix
-
-
-
-
- ./services/network-filesystems/orangefs/server.nix
-
-
-
-
- ./services/network-filesystems/orangefs/client.nix
-
-
-
-
- ./services/networking/3proxy.nix
-
-
-
-
- ./services/networking/corerad.nix
-
-
-
-
- ./services/networking/go-shadowsocks2.nix
-
-
-
-
- ./services/networking/ntp/openntpd.nix
-
-
-
-
- ./services/networking/shorewall.nix
-
-
-
-
- ./services/networking/shorewall6.nix
-
-
-
-
- ./services/networking/spacecookie.nix
-
-
-
-
- ./services/networking/trickster.nix
-
-
-
-
- ./services/networking/v2ray.nix
-
-
-
-
- ./services/networking/xandikos.nix
-
-
-
-
- ./services/networking/yggdrasil.nix
-
-
-
-
- ./services/web-apps/dokuwiki.nix
-
-
-
-
- ./services/web-apps/gotify-server.nix
-
-
-
-
- ./services/web-apps/grocy.nix
-
-
-
-
- ./services/web-apps/ihatemoney
-
-
-
-
- ./services/web-apps/moinmoin.nix
-
-
-
-
- ./services/web-apps/trac.nix
-
-
-
-
- ./services/web-apps/trilium.nix
-
-
-
-
- ./services/web-apps/shiori.nix
-
-
-
-
- ./services/web-servers/ttyd.nix
-
-
-
-
- ./services/x11/picom.nix
-
-
-
-
- ./services/x11/hardware/digimend.nix
-
-
-
-
- ./services/x11/imwheel.nix
-
-
-
-
- ./virtualisation/cri-o.nix
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- The dhcpcd package
-
- does not request IPv4 addresses for tap and bridge interfaces
- anymore by default. In order to still get an address on
- a bridge interface, one has to disable
- networking.useDHCP and explicitly enable
- networking.interfaces.<name>.useDHCP
- on every interface, that should get an address via DHCP. This
- way, dhcpcd is configured in an explicit way about which
- interface to run on.
-
-
-
-
- GnuPG is now built without support for a graphical passphrase
- entry by default. Please enable the
- gpg-agent user service via the NixOS option
- programs.gnupg.agent.enable. Note that
- upstream recommends using gpg-agent and
- will spawn a gpg-agent on the first
- invocation of GnuPG anyway.
-
-
-
-
- The dynamicHosts option has been removed
- from the
- NetworkManager
- module. Allowing (multiple) regular users to override host
- entries affecting the whole system opens up a huge attack
- vector. There seem to be very rare cases where this might be
- useful. Consider setting system-wide host entries using
- networking.hosts,
- provide them via the DNS server in your network, or use
- environment.etc
- to add a file into
- /etc/NetworkManager/dnsmasq.d reconfiguring
- hostsdir.
-
-
-
-
- The 99-main.network file was removed.
- Matching all network interfaces caused many breakages, see
- #18962
- and
- #71106.
-
-
- We already don’t support the global
- networking.useDHCP,
- networking.defaultGateway
- and
- networking.defaultGateway6
- options if
- networking.useNetworkd
- is enabled, but direct users to configure the per-device
- networking.interfaces.<name>….
- options.
-
-
-
-
- The stdenv now runs all bash with set -u,
- to catch the use of undefined variables. Before, it itself
- used set -u but was careful to unset it so
- other packages’ code ran as before. Now, all bash code is held
- to the same high standard, and the rather complex stateful
- manipulation of the options can be discarded.
-
-
-
-
- The SLIM Display Manager has been removed, as it has been
- unmaintained since 2013. Consider migrating to a different
- display manager such as LightDM (current default in NixOS),
- SDDM, GDM, or using the startx module which uses Xinitrc.
-
-
-
-
- The Way Cooler wayland compositor has been removed, as the
- project has been officially canceled. There are no more
- way-cooler attribute and
- programs.way-cooler options.
-
-
-
-
- The BEAM package set has been deleted. You will only find
- there the different interpreters. You should now use the
- different build tools coming with the languages with sandbox
- mode disabled.
-
-
-
-
- There is now only one Xfce package-set and module. This means
- that attributes xfce4-14 and
- xfceUnstable all now point to the latest
- Xfce 4.14 packages. And in the future NixOS releases will be
- the latest released version of Xfce available at the time of
- the release’s development (if viable).
-
-
-
-
- The
- phpfpm
- module now sets PrivateTmp=true in its
- systemd units for better process isolation. If you rely on
- /tmp being shared with other services,
- explicitly override this by setting
- serviceConfig.PrivateTmp to
- false for each phpfpm unit.
-
-
-
-
- KDE’s old multimedia framework Phonon no longer supports Qt 4.
- For that reason, Plasma desktop also does not have
- enableQt4Support option any more.
-
-
-
-
- The BeeGFS module has been removed.
-
-
-
-
- The osquery module has been removed.
-
-
-
-
- Going forward, ~/bin in the users home
- directory will no longer be in PATH by
- default. If you depend on this you should set the option
- environment.homeBinInPath to
- true. The aforementioned option was added
- this release.
-
-
-
-
- The buildRustCrate infrastructure now
- produces lib outputs in addition to the
- out output. This has led to drastically
- reduced closure sizes for some rust crates since development
- dependencies are now in the lib output.
-
-
-
-
- Pango was upgraded to 1.44, which no longer uses freetype for
- font loading. This means that type1 and bitmap fonts are no
- longer supported in applications relying on Pango for font
- rendering (notably, GTK application). See
-
- upstream issue for more information.
-
-
-
-
- The roundcube module has been hardened.
-
-
-
-
- The password of the database is not written world readable
- in the store any more. If database.host
- is set to localhost, then a unix user
- of the same name as the database will be created and
- PostreSQL peer authentication will be used, removing the
- need for a password. Otherwise, a password is still needed
- and can be provided with the new option
- database.passwordFile, which should be
- set to the path of a file containing the password and
- readable by the user nginx only. The
- database.password option is insecure
- and deprecated. Usage of this option will print a warning.
-
-
-
-
- A random des_key is set by default in
- the configuration of roundcube, instead of using the
- hardcoded and insecure default. To ensure a clean
- migration, all users will be logged out when you upgrade
- to this release.
-
-
-
-
-
-
- The packages openobex and
- obexftp are no longer installed when
- enabling Bluetooth via
- hardware.bluetooth.enable.
-
-
-
-
- The dump1090 derivation has been changed to
- use FlightAware’s dump1090 as its upstream. However, this
- version does not have an internal webserver anymore. The
- assets in the share/dump1090 directory of
- the derivation can be used in conjunction with an external
- webserver to replace this functionality.
-
-
-
-
- The fourStore and fourStoreEndpoint modules have been removed.
-
-
-
-
- Polkit no longer has the user of uid 0 (root) as an admin
- identity. We now follow the upstream default of only having
- every member of the wheel group admin privileged. Before it
- was root and members of wheel. The positive outcome of this is
- pkexec GUI popups or terminal prompts will no longer require
- the user to choose between two essentially equivalent choices
- (whether to perform the action as themselves with wheel
- permissions, or as the root user).
-
-
-
-
- NixOS containers no longer build NixOS manual by default. This
- saves evaluation time, especially if there are many
- declarative containers defined. Note that this is already done
- when
- <nixos/modules/profiles/minimal.nix>
- module is included in container config.
-
-
-
-
- The kresd services deprecates the
- interfaces option in favor of the
- listenPlain option which requires full
- systemd.socket
- compatible declaration which always include a port.
-
-
-
-
- Virtual console options have been reorganized and can be found
- under a single top-level attribute:
- console. The full set of changes is as
- follows:
-
-
-
-
- i18n.consoleFont renamed to
- console.font
-
-
-
-
- i18n.consoleKeyMap renamed to
- console.keyMap
-
-
-
-
- i18n.consoleColors renamed to
- console.colors
-
-
-
-
- i18n.consolePackages renamed to
- console.packages
-
-
-
-
- i18n.consoleUseXkbConfig renamed to
- console.useXkbConfig
-
-
-
-
- boot.earlyVconsoleSetup renamed to
- console.earlySetup
-
-
-
-
- boot.extraTTYs renamed to
- console.extraTTYs.
-
-
-
-
-
-
- The
- awstats
- module has been rewritten to serve stats via static html
- pages, updated on a timer, over
- nginx,
- instead of dynamic cgi pages over
- apache.
-
-
- Minor changes will be required to migrate existing
- configurations. Details of the required changes can seen by
- looking through the
- awstats
- module.
-
-
-
-
- The httpd module no longer provides options to support serving
- web content without defining a virtual host. As a result of
- this the
- services.httpd.logPerVirtualHost
- option now defaults to true instead of
- false. Please update your configuration to
- make use of
- services.httpd.virtualHosts.
-
-
- The
- services.httpd.virtualHosts.<name>
- option has changed type from a list of submodules to an
- attribute set of submodules, better matching
- services.nginx.virtualHosts.<name>.
-
-
- This change comes with the addition of the following options
- which mimic the functionality of their
- nginx counterparts:
- services.httpd.virtualHosts.<name>.addSSL,
- services.httpd.virtualHosts.<name>.forceSSL,
- services.httpd.virtualHosts.<name>.onlySSL,
- services.httpd.virtualHosts.<name>.enableACME,
- services.httpd.virtualHosts.<name>.acmeRoot,
- and
- services.httpd.virtualHosts.<name>.useACMEHost.
-
-
-
-
- For NixOS configuration options, the loaOf
- type has been deprecated and will be removed in a future
- release. In nixpkgs, options of this type will be changed to
- attrsOf instead. If you were using one of
- these in your configuration, you will see a warning suggesting
- what changes will be required.
-
-
- For example,
- users.users
- is a loaOf option that is commonly used as
- follows:
-
-
-{
- users.users =
- [ { name = "me";
- description = "My personal user.";
- isNormalUser = true;
- }
- ];
-}
-
-
- This should be rewritten by removing the list and using the
- value of name as the name of the attribute
- set:
-
-
-{
- users.users.me =
- { description = "My personal user.";
- isNormalUser = true;
- };
-}
-
-
- For more information on this change have look at these links:
- issue
- #1800,
- PR
- #63103.
-
-
-
-
- For NixOS modules, the types
- types.submodule and
- types.submoduleWith now support paths as
- allowed values, similar to how imports
- supports paths. Because of this, if you have a module that
- defines an option of type
- either (submodule ...) path, it will break
- since a path is now treated as the first type instead of the
- second. To fix this, change the type to
- either path (submodule ...).
-
-
-
-
- The
- Buildkite
- Agent module and corresponding packages have been
- updated to 3.x, and to support multiple instances of the agent
- running at the same time. This means you will have to rename
- services.buildkite-agent to
- services.buildkite-agents.<name>.
- Furthermore, the following options have been changed:
-
-
-
-
- services.buildkite-agent.meta-data has
- been renamed to
- services.buildkite-agents.<name>.tags,
- to match upstreams naming for 3.x. Its type has also
- changed - it now accepts an attrset of strings.
-
-
-
-
- Theservices.buildkite-agent.openssh.publicKeyPath
- option has been removed, as it’s not necessary to deploy
- public keys to clone private repositories.
-
-
-
-
- services.buildkite-agent.openssh.privateKeyPath
- has been renamed to
- buildkite-agents.<name>.privateSshKeyPath,
- as the whole openssh now only contained
- that single option.
-
-
-
-
- services.buildkite-agents.<name>.shell
- has been introduced, allowing to specify a custom shell to
- be used.
-
-
-
-
-
-
- The citrix_workspace_19_3_0 package has
- been removed as it will be EOLed within the lifespan of 20.03.
- For further information, please refer to the
- support
- and maintenance information from upstream.
-
-
-
-
- The gcc5 and gfortran5
- packages have been removed.
-
-
-
-
- The services.xserver.displayManager.auto
- module has been removed. It was only intended for use in
- internal NixOS tests, and gave the false impression of it
- being a special display manager when it’s actually LightDM.
- Please use the
- services.xserver.displayManager.lightdm.autoLogin
- options instead, or any other display manager in NixOS as they
- all support auto-login. If you used this module specifically
- because it permitted root auto-login you can override the
- lightdm-autologin pam module like:
-
-
-{
- security.pam.services.lightdm-autologin.text = lib.mkForce ''
- auth requisite pam_nologin.so
- auth required pam_succeed_if.so quiet
- auth required pam_permit.so
-
- account include lightdm
-
- password include lightdm
-
- session include lightdm
- '';
-}
-
-
- The difference is the:
-
-
-auth required pam_succeed_if.so quiet
-
-
- line, where default it’s:
-
-
- auth required pam_succeed_if.so uid >= 1000 quiet
-
-
- not permitting users with uid’s below 1000 (like root). All
- other display managers in NixOS are configured like this.
-
-
-
-
- There have been lots of improvements to the Mailman module. As
- a result,
-
-
-
-
- The services.mailman.hyperkittyBaseUrl
- option has been renamed to
- services.mailman.hyperkitty.baseUrl.
-
-
-
-
- The services.mailman.hyperkittyApiKey
- option has been removed. This is because having an option
- for the Hyperkitty API key meant that the API key would be
- stored in the world-readable Nix store, which was a
- security vulnerability. A new Hyperkitty API key will be
- generated the first time the new Hyperkitty service is
- run, and it will then be persisted outside of the Nix
- store. To continue using Hyperkitty, you must set
- services.mailman.hyperkitty.enable
- to true.
-
-
-
-
- Additionally, some Postfix configuration must now be set
- manually instead of automatically by the Mailman module:
-
-
-{
- services.postfix.relayDomains = [ "hash:/var/lib/mailman/data/postfix_domains" ];
- services.postfix.config.transport_maps = [ "hash:/var/lib/mailman/data/postfix_lmtp" ];
- services.postfix.config.local_recipient_maps = [ "hash:/var/lib/mailman/data/postfix_lmtp" ];
-}
-
-
- This is because some users may want to include other
- values in these lists as well, and this was not possible
- if they were set automatically by the Mailman module. It
- would not have been possible to just concatenate values
- from multiple modules each setting the values they needed,
- because the order of elements in the list is significant.
-
-
-
-
-
-
- The LLVM versions 3.5, 3.9 and 4 (including the corresponding
- CLang versions) have been dropped.
-
-
-
-
- The
- networking.interfaces.*.preferTempAddress
- option has been replaced by
- networking.interfaces.*.tempAddress. The
- new option allows better control of the IPv6 temporary
- addresses, including completely disabling them for interfaces
- where they are not needed.
-
-
-
-
- Rspamd was updated to version 2.2. Read
-
- the upstream migration notes carefully. Please be
- especially aware that some modules were removed and the
- default Bayes backend is now Redis.
-
-
-
-
- The *psu versions of oraclejdk8 have been
- removed as they aren’t provided by upstream anymore.
-
-
-
-
- The services.dnscrypt-proxy module has been
- removed as it used the deprecated version of dnscrypt-proxy.
- We’ve added
- services.dnscrypt-proxy2.enable
- to use the supported version. This module supports
- configuration via the Nix attribute set
- services.dnscrypt-proxy2.settings,
- or by passing a TOML configuration file via
- services.dnscrypt-proxy2.configFile.
-
-
-{
- # Example configuration:
- services.dnscrypt-proxy2.enable = true;
- services.dnscrypt-proxy2.settings = {
- listen_addresses = [ "127.0.0.1:43" ];
- sources.public-resolvers = {
- urls = [ "https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md" ];
- cache_file = "public-resolvers.md";
- minisign_key = "RWQf6LRCGA9i53mlYecO4IzT51TGPpvWucNSCh1CBM0QTaLn73Y7GFO3";
- refresh_delay = 72;
- };
- };
-
- services.dnsmasq.enable = true;
- services.dnsmasq.servers = [ "127.0.0.1#43" ];
-}
-
-
-
-
- qesteidutil has been deprecated in favor of
- qdigidoc.
-
-
-
-
- sqldeveloper_18 has been removed as it’s not maintained
- anymore, sqldeveloper has been updated to version
- 19.4. Please note that this means that this
- means that the oraclejdk is now required. For further
- information please read the
- release
- notes.
-
-
-
-
- Haskell env and shellFor
- dev shell environments now organize dependencies the same way
- as regular builds. In particular, rather than receiving all
- the different lists of dependencies mashed together as one big
- list, and then partitioning into Haskell and non-Hakell
- dependencies, they work from the original many different
- dependency parameters and don’t need to algorithmically
- partition anything.
-
-
- This means that if you incorrectly categorize a dependency,
- e.g. non-Haskell library dependency as a
- buildDepends or run-time Haskell dependency
- as a setupDepends, whereas things would
- have worked before they may not work now.
-
-
-
-
- The gcc-snapshot-package has been removed. It’s marked as
- broken for >2 years and used to point to a fairly old
- snapshot from the gcc7-branch.
-
-
-
-
- The nixos-build-vms8 -script now uses the python test-driver.
-
-
-
-
- The riot-web package now accepts configuration overrides as an
- attribute set instead of a string. A formerly used JSON
- configuration can be converted to an attribute set with
- builtins.fromJSON.
-
-
- The new default configuration also disables automatic guest
- account registration and analytics to improve privacy. The
- previous behavior can be restored by setting
- config.riot-web.conf = { disable_guests = false; piwik = true; }.
-
-
-
-
- Stand-alone usage of Upower now requires
- services.upower.enable instead of just
- installing into
- environment.systemPackages.
-
-
-
-
- nextcloud has been updated to v18.0.2. This
- means that users from NixOS 19.09 can’t upgrade directly since
- you can only move one version forward and 19.09 uses
- v16.0.8.
-
-
- To provide a safe upgrade-path and to circumvent similar
- issues in the future, the following measures were taken:
-
-
-
-
- The pkgs.nextcloud-attribute has been removed and replaced
- with versioned attributes (currently pkgs.nextcloud17 and
- pkgs.nextcloud18). With this change major-releases can be
- backported without breaking stuff and to make
- upgrade-paths easier.
-
-
-
-
- Existing setups will be detected using
- system.stateVersion:
- by default, nextcloud17 will be used, but will raise a
- warning which notes that after that deploy it’s
- recommended to update to the latest stable version
- (nextcloud18) by declaring the newly introduced setting
- services.nextcloud.package.
-
-
-
-
- Users with an overlay (e.g. to use nextcloud at version
- v18 on 19.09) will
- get an evaluation error by default. This is done to ensure
- that our
- package-option
- doesn’t select an older version by accident. It’s
- recommended to use pkgs.nextcloud18 or to set
- package
- to pkgs.nextcloud explicitly.
-
-
-
-
-
- Please note that if you’re coming from
- 19.03 or older, you have to manually
- upgrade to 19.09 first to upgrade your
- server to Nextcloud v16.
-
-
-
-
-
- Hydra has gained a massive performance improvement due to
- some
- database schema changes by adding several IDs and
- better indexing. However, it’s necessary to upgrade Hydra in
- multiple steps:
-
-
-
-
- At first, an older version of Hydra needs to be deployed
- which adds those (nullable) columns. When having set
- stateVersion
- to a value older than 20.03,
- this package will be selected by default from the module
- when upgrading. Otherwise, the package can be deployed
- using the following config:
-
-
-{ pkgs, ... }: {
- services.hydra.package = pkgs.hydra-migration;
-}
-
-
-
-
-
-
- Automatically fill the newly added ID columns on the server by
- running the following command:
-
-
-$ hydra-backfill-ids
-
-
-
- Please note that this process can take a while depending on
- your database-size!
-
-
-
-
-
- Deploy a newer version of Hydra to activate the DB
- optimizations. This can be done by using hydra-unstable. This
- package already includes
- flake-support
- and is therefore compiled against pkgs.nixFlakes.
-
-
-
- If your
- stateVersion
- is set to 20.03 or greater,
- hydra-unstable will be used automatically! This will break
- your setup if you didn’t run the migration.
-
-
-
- Please note that Hydra is currently not available with
- nixStable as this doesn’t compile anymore.
-
-
-
- pkgs.hydra has been removed to ensure a graceful
- database-migration using the dedicated package-attributes.
- If you still have pkgs.hydra defined in e.g. an overlay, an
- assertion error will be thrown. To circumvent this, you need
- to set
- services.hydra.package
- to pkgs.hydra explicitly and make sure you know what you’re
- doing!
-
-
-
-
-
- The TokuDB storage engine will be disabled in mariadb 10.5. It
- is recommended to switch to RocksDB. See also
- TokuDB.
-
-
-
-
-
- Other Notable Changes
-
-
-
- SD images are now compressed by default using
- bzip2.
-
-
-
-
- The nginx web server previously started its master process as
- root privileged, then ran worker processes as a less
- privileged identity user (the nginx user).
- This was changed to start all of nginx as a less privileged
- user (defined by services.nginx.user and
- services.nginx.group). As a consequence,
- all files that are needed for nginx to run (included
- configuration fragments, SSL certificates and keys, etc.) must
- now be readable by this less privileged user/group.
-
-
- To continue to use the old approach, you can configure:
-
-
-{
- services.nginx.appendConfig = let cfg = config.services.nginx; in ''user ${cfg.user} ${cfg.group};'';
- systemd.services.nginx.serviceConfig.User = lib.mkForce "root";
-}
-
-
-
-
- OpenSSH has been upgraded from 7.9 to 8.1, improving security
- and adding features but with potential incompatibilities.
- Consult the
-
- release announcement for more information.
-
-
-
-
- PRETTY_NAME in
- /etc/os-release now uses the short rather
- than full version string.
-
-
-
-
- The ACME module has switched from simp-le to
- lego
- which allows us to support DNS-01 challenges and wildcard
- certificates. The following options have been added:
- security.acme.acceptTerms,
- security.acme.certs.<name>.dnsProvider,
- security.acme.certs.<name>.credentialsFile,
- security.acme.certs.<name>.dnsPropagationCheck.
- As well as this, the options
- security.acme.acceptTerms and either
- security.acme.email or
- security.acme.certs.<name>.email must
- be set in order to use the ACME module. Certificates will be
- regenerated on activation, no account or certificate will be
- migrated from simp-le. In particular private keys will not be
- preserved. However, the credentials for simp-le are preserved
- and thus it is possible to roll back to previous versions
- without breaking certificate generation. Note also that in
- contrary to simp-le a new private key is recreated at each
- renewal by default, which can have consequences if you embed
- your public key in apps.
-
-
-
-
- It is now possible to unlock LUKS-Encrypted file systems using
- a FIDO2 token via
- boot.initrd.luks.fido2Support.
-
-
-
-
- Predictably named network interfaces get renamed in stage-1.
- This means that it is possible to use the proper interface
- name for e.g. Dropbear setups.
-
-
- For further reference, please read
- #68953
- or the corresponding
- discourse
- thread.
-
-
-
-
- The matrix-synapse-package has been updated to
- v1.11.1.
- Due to
- stricter
- requirements for database configuration when using
- postgresql, the automated database setup of the module has
- been removed to avoid any further edge-cases.
-
-
- matrix-synapse expects postgresql-databases
- to have the options LC_COLLATE and
- LC_CTYPE set to
- 'C'
- which basically instructs postgresql to
- ignore any locale-based preferences.
-
-
- Depending on your setup, you need to incorporate one of the
- following changes in your setup to upgrade to 20.03:
-
-
-
-
- If you use sqlite3 you don’t need to do
- anything.
-
-
-
-
- If you use postgresql on a different
- server, you don’t need to change anything as well since
- this module was never designed to configure remote
- databases.
-
-
-
-
- If you use postgresql and configured
- your synapse initially on 19.09 or
- older, you simply need to enable postgresql-support
- explicitly:
-
-
-{ ... }: {
- services.matrix-synapse = {
- enable = true;
- /* and all the other config you've defined here */
- };
- services.postgresql.enable = true;
-}
-
-
-
-
-
-
- If you deploy a fresh matrix-synapse, you need to configure
- the database yourself (e.g. by using the
- services.postgresql.initialScript
- option). An example for this can be found in the
- documentation of the
- Matrix module.
-
-
-
-
- If you initially deployed your matrix-synapse on
- nixos-unstableafter
- the 19.09-release, your database is
- misconfigured due to a regression in NixOS. For now,
- matrix-synapse will startup with a warning, but it’s
- recommended to reconfigure the database to set the values
- LC_COLLATE and LC_CTYPE
- to
- 'C'.
-
-
-
-
- The
- systemd.network.links
- option is now respected even when
- systemd-networkd
- is disabled. This mirrors the behaviour of systemd - It’s udev
- that parses .link files, not
- systemd-networkd.
-
-
-
-
- mongodb has been updated to version 3.4.24.
-
-
-
- Please note that mongodb has been relicensed under their own
- sspl-license.
- Since it’s not entirely free and not OSI-approved, it’s
- listed as non-free. This means that Hydra doesn’t provide
- prebuilt mongodb-packages and needs to be built locally.
-
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-2009.section.xml b/nixos/doc/manual/from_md/release-notes/rl-2009.section.xml
deleted file mode 100644
index a1b007e711d7..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-2009.section.xml
+++ /dev/null
@@ -1,2210 +0,0 @@
-
- Release 20.09 (<quote>Nightingale</quote>, 2020.10/27)
-
- Support is planned until the end of June 2021, handing over to
- 21.05. (Plans
-
- have shifted by two months since release of 20.09.)
-
-
- Highlights
-
- In addition to 7349 new, 14442 updated, and 8181 removed packages,
- this release has the following highlights:
-
-
-
-
- Core version changes:
-
-
-
-
- gcc: 9.2.0 -> 9.3.0
-
-
-
-
- glibc: 2.30 -> 2.31
-
-
-
-
- linux: still defaults to 5.4.x, all supported kernels
- available
-
-
-
-
- mesa: 19.3.5 -> 20.1.7
-
-
-
-
-
-
- Desktop Environments:
-
-
-
-
- plasma5: 5.17.5 -> 5.18.5
-
-
-
-
- kdeApplications: 19.12.3 -> 20.08.1
-
-
-
-
- gnome3: 3.34 -> 3.36, see its
- release
- notes
-
-
-
-
- cinnamon: added at 4.6
-
-
-
-
- NixOS now distributes an official
- GNOME
- ISO
-
-
-
-
-
-
- Programming Languages and Frameworks:
-
-
-
-
- Agda ecosystem was heavily reworked (see more details
- below)
-
-
-
-
- PHP now defaults to PHP 7.4, updated from 7.3
-
-
-
-
- PHP 7.2 is no longer supported due to upstream not
- supporting this version for the entire lifecycle of the
- 20.09 release
-
-
-
-
- Python 3 now defaults to Python 3.8 instead of 3.7
-
-
-
-
- Python 3.5 reached its upstream EOL at the end of
- September 2020: it has been removed from the list of
- available packages
-
-
-
-
-
-
- Databases and Service Monitoring:
-
-
-
-
- MariaDB has been updated to 10.4, MariaDB Galera to 26.4.
- Please read the related upgrade instructions under
- backwards
- incompatibilities before upgrading.
-
-
-
-
- Zabbix now defaults to 5.0, updated from 4.4. Please read
- related sections under
- backwards
- compatibilities before upgrading.
-
-
-
-
-
-
- Major module changes:
-
-
-
-
- Quickly configure a complete, private, self-hosted video
- conferencing solution with the new Jitsi Meet module.
-
-
-
-
- Two new options,
- authorizedKeysCommand
- and
- authorizedKeysCommandUser,
- have been added to the openssh module.
- If you have AuthorizedKeysCommand in
- your
- services.openssh.extraConfig
- you should make use of these new options instead.
-
-
-
-
- There is a new module for Podman
- (virtualisation.podman), a drop-in
- replacement for the Docker command line.
-
-
-
-
- The new virtualisation.containers
- module manages configuration shared by the CRI-O and
- Podman modules.
-
-
-
-
- Declarative Docker containers are renamed from
- docker-containers to
- virtualisation.oci-containers.containers.
- This is to make it possible to use
- podman instead of
- docker.
-
-
-
-
- The new option
- documentation.man.generateCaches
- has been added to automatically generate the
- man-db caches, which are needed by
- utilities like whatis and
- apropos. The caches are generated
- during the build of the NixOS configuration: since this
- can be expensive when a large number of packages are
- installed, the feature is disabled by default.
-
-
-
-
- services.postfix.sslCACert was replaced
- by
- services.postfix.tlsTrustedAuthorities
- which now defaults to system certificate authorities.
-
-
-
-
- The various documented workarounds to use steam have been
- converted to a module.
- programs.steam.enable enables steam,
- controller support and the workarounds.
-
-
-
-
- Support for built-in LCDs in various pieces of Logitech
- hardware (keyboards and USB speakers).
- hardware.logitech.lcd.enable enables
- support for all hardware supported by the
- g15daemon
- project.
-
-
-
-
- The GRUB module gained support for basic password
- protection, which allows to restrict non-default entries
- in the boot menu to one or more users. The users and
- passwords are defined via the option
- boot.loader.grub.users. Note: Password
- support is only available in GRUB version 2.
-
-
-
-
-
-
- NixOS module changes:
-
-
-
-
- The NixOS module system now supports freeform modules as a
- mix between types.attrsOf and
- types.submodule. These allow you to
- explicitly declare a subset of options while still
- permitting definitions without an associated option. See
- for how to use
- them.
-
-
-
-
- Following its deprecation in 20.03, the Perl NixOS test
- driver has been removed. All remaining tests have been
- ported to the Python test framework. Code outside nixpkgs
- using make-test.nix or
- testing.nix needs to be ported to
- make-test-python.nix and
- testing-python.nix respectively.
-
-
-
-
- Subordinate GID and UID mappings are now set up
- automatically for all normal users. This will make
- container tools like Podman work as non-root users out of
- the box.
-
-
-
-
-
-
- Starting with this release, the hydra-build-result
- nixos-YY.MM branches no longer exist in the
- deprecated
- nixpkgs-channels repository. These branches are now in
- the main
- nixpkgs repository.
-
-
-
-
-
- New Services
-
- In addition to 1119 new, 118 updated, and 476 removed options; 61
- new modules were added since the last release:
-
-
-
-
- Hardware:
-
-
-
-
- hardware.system76.firmware-daemon.enable
- adds easy support of system76 firmware
-
-
-
-
- hardware.uinput.enable
- loads uinput kernel module
-
-
-
-
- hardware.video.hidpi.enable
- enable good defaults for HiDPI displays
-
-
-
-
- hardware.wooting.enable
- support for Wooting keyboards
-
-
-
-
- hardware.xpadneo.enable
- xpadneo driver for Xbox One wireless controllers
-
-
-
-
-
-
- Programs:
-
-
-
-
- programs.hamster.enable
- enable hamster time tracking
-
-
-
-
- programs.steam.enable
- adds easy enablement of steam and related system
- configuration
-
-
-
-
-
-
- Security:
-
-
-
-
- security.doas.enable
- alternative to sudo, allows non-root users to execute
- commands as root
-
-
-
-
- security.tpm2.enable
- add Trusted Platform Module 2 support
-
-
-
-
-
-
- System:
-
-
-
-
- boot.initrd.network.openvpn.enable
- start an OpenVPN client during initrd boot
-
-
-
-
-
-
- Virtualization:
-
-
-
-
- boot.enableContainers
- use nixos-containers
-
-
-
-
- virtualisation.oci-containers.containers
- run OCI (Docker) containers
-
-
-
-
- virtualisation.podman.enable
- daemonless container engine
-
-
-
-
-
-
- Services:
-
-
-
-
- services.ankisyncd.enable
- Anki sync server
-
-
-
-
- services.bazarr.enable
- Subtitle manager for Sonarr and Radarr
-
-
-
-
- services.biboumi.enable
- Biboumi XMPP gateway to IRC
-
-
-
-
- services.blockbook-frontend
- Blockbook-frontend, a service for the Trezor wallet
-
-
-
-
- services.cage.enable
- Wayland cage service
-
-
-
-
- services.convos.enable
- IRC daemon, which can be accessed throught the browser
-
-
-
-
- services.engelsystem.enable
- Tool for coordinating volunteers and shifts on large
- events
-
-
-
-
- services.espanso.enable
- text-expander written in rust
-
-
-
-
- services.foldingathome.enable
- Folding@home client
-
-
-
-
- services.gerrit.enable
- Web-based team code collaboration tool
-
-
-
-
- services.go-neb.enable
- Matrix bot
-
-
-
-
- services.hardware.xow.enable
- xow as a systemd service
-
-
-
-
- services.hercules-ci-agent.enable
- Hercules CI build agent
-
-
-
-
- services.jicofo.enable
- Jitsi Conference Focus, component of Jitsi Meet
-
-
-
-
- services.jirafeau.enable
- A web file repository
-
-
-
-
- services.jitsi-meet.enable
- Secure, simple and scalable video conferences
-
-
-
-
- services.jitsi-videobridge.enable
- Jitsi Videobridge, a WebRTC compatible router
-
-
-
-
- services.jupyterhub.enable
- Jupyterhub development server
-
-
-
-
- services.k3s.enable
- Lightweight Kubernetes distribution
-
-
-
-
- services.magic-wormhole-mailbox-server.enable
- Magic Wormhole Mailbox Server
-
-
-
-
- services.malcontent.enable
- Parental Control support
-
-
-
-
- services.matrix-appservice-discord.enable
- Matrix and Discord bridge
-
-
-
-
- services.mautrix-telegram.enable
- Matrix-Telegram puppeting/relaybot bridge
-
-
-
-
- services.mirakurun.enable
- Japanese DTV Tuner Server Service
-
-
-
-
- services.molly-brown.enable
- Molly-Brown Gemini server
-
-
-
-
- services.mullvad-vpn.enable
- Mullvad VPN daemon
-
-
-
-
- services.ncdns.enable
- Namecoin to DNS bridge
-
-
-
-
- services.nextdns.enable
- NextDNS to DoH Proxy service
-
-
-
-
- services.nix-store-gcs-proxy
- Google storage bucket to be used as a nix store
-
-
-
-
- services.onedrive.enable
- OneDrive sync service
-
-
-
-
- services.pinnwand.enable
- Pastebin-like service
-
-
-
-
- services.pixiecore.enable
- Manage network booting of machines
-
-
-
-
- services.privacyidea.enable
- Privacy authentication server
-
-
-
-
- services.quorum.enable
- Quorum blockchain daemon
-
-
-
-
- services.robustirc-bridge.enable
- RobustIRC bridge
-
-
-
-
- services.rss-bridge.enable
- Generate RSS and Atom feeds
-
-
-
-
- services.rtorrent.enable
- rTorrent service
-
-
-
-
- services.smartdns.enable
- SmartDNS DNS server
-
-
-
-
- services.sogo.enable
- SOGo groupware
-
-
-
-
- services.teeworlds.enable
- Teeworlds game server
-
-
-
-
- services.torque.mom.enable
- torque computing node
-
-
-
-
- services.torque.server.enable
- torque server
-
-
-
-
- services.tuptime.enable
- A total uptime service
-
-
-
-
- services.urserver.enable
- X11 remote server
-
-
-
-
- services.wasabibackend.enable
- Wasabi backend service
-
-
-
-
- services.yubikey-agent.enable
- Yubikey agent
-
-
-
-
- services.zigbee2mqtt.enable
- Zigbee to MQTT bridge
-
-
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- MariaDB has been updated to 10.4, MariaDB Galera to 26.4.
- Before you upgrade, it would be best to take a backup of your
- database. For MariaDB Galera Cluster, see
- Upgrading
- from MariaDB 10.3 to MariaDB 10.4 with Galera Cluster
- instead. Before doing the upgrade read
- Incompatible
- Changes Between 10.3 and 10.4. After the upgrade you
- will need to run mysql_upgrade. MariaDB
- 10.4 introduces a number of changes to the authentication
- process, intended to make things easier and more intuitive.
- See
- Authentication
- from MariaDB 10.4. unix_socket auth plugin does not use
- a password, and uses the connecting user’s UID instead. When a
- new MariaDB data directory is initialized, two MariaDB users
- are created and can be used with new unix_socket auth plugin,
- as well as traditional mysql_native_password plugin:
- root@localhost and mysql@localhost. To actually use the
- traditional mysql_native_password plugin method, one must run
- the following:
-
-
-{
-services.mysql.initialScript = pkgs.writeText "mariadb-init.sql" ''
- ALTER USER root@localhost IDENTIFIED VIA mysql_native_password USING PASSWORD("verysecret");
-'';
-}
-
-
- When MariaDB data directory is just upgraded (not
- initialized), the users are not created or modified.
-
-
-
-
- MySQL server is now started with additional systemd
- sandbox/hardening options for better security. The PrivateTmp,
- ProtectHome, and ProtectSystem options may be problematic when
- MySQL is attempting to read from or write to your filesystem
- anywhere outside of its own state directory, for example when
- calling
- LOAD DATA INFILE or SELECT * INTO OUTFILE.
- In this scenario a variant of the following may be required: -
- allow MySQL to read from /home and /tmp directories when using
- LOAD DATA INFILE
-
-
-{
- systemd.services.mysql.serviceConfig.ProtectHome = lib.mkForce "read-only";
-}
-
-
- - allow MySQL to write to custom folder
- /var/data when using
- SELECT * INTO OUTFILE, assuming the mysql
- user has write access to /var/data
-
-
-{
- systemd.services.mysql.serviceConfig.ReadWritePaths = [ "/var/data" ];
-}
-
-
- The MySQL service no longer runs its
- systemd service startup script as
- root anymore. A dedicated non
- root super user account is required for
- operation. This means users with an existing MySQL or MariaDB
- database server are required to run the following SQL
- statements as a super admin user before upgrading:
-
-
-CREATE USER IF NOT EXISTS 'mysql'@'localhost' identified with unix_socket;
-GRANT ALL PRIVILEGES ON *.* TO 'mysql'@'localhost' WITH GRANT OPTION;
-
-
- If you use MySQL instead of MariaDB please replace
- unix_socket with
- auth_socket. If you have changed the value
- of
- services.mysql.user
- from the default of mysql to a different
- user please change 'mysql'@'localhost' to
- the corresponding user instead.
-
-
-
-
- Zabbix now defaults to 5.0, updated from 4.4. Please carefully
- read through
- the
- upgrade guide and apply any changes required. Be sure
- to take special note of the section on
- enabling
- extended range of numeric (float) values as you will
- need to apply this database migration manually.
-
-
- If you are using Zabbix Server with a MySQL or MariaDB
- database you should note that using a character set of
- utf8 and a collate of
- utf8_bin has become mandatory with this
- release. See the upstream
- issue
- for further discussion. Before upgrading you should check the
- character set and collation used by your database and ensure
- they are correct:
-
-
-SELECT
- default_character_set_name,
- default_collation_name
-FROM
- information_schema.schemata
-WHERE
- schema_name = 'zabbix';
-
-
- If these values are not correct you should take a backup of
- your database and convert the character set and collation as
- required. Here is an
- example
- of how to do so, taken from the Zabbix forums:
-
-
-ALTER DATABASE `zabbix` DEFAULT CHARACTER SET utf8 COLLATE utf8_bin;
-
--- the following will produce a list of SQL commands you should subsequently execute
-SELECT CONCAT("ALTER TABLE ", TABLE_NAME," CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin;") AS ExecuteTheString
-FROM information_schema.`COLUMNS`
-WHERE table_schema = "zabbix" AND COLLATION_NAME = "utf8_general_ci";
-
-
-
-
- maxx package removed along with
- services.xserver.desktopManager.maxx
- module. Please migrate to cdesktopenv and
- services.xserver.desktopManager.cde module.
-
-
-
-
- The
- matrix-synapse
- module no longer includes optional dependencies by default,
- they have to be added through the
- plugins
- option.
-
-
-
-
- buildGoModule now internally creates a
- vendor directory in the source tree for downloaded modules
- instead of using go’s
- module
- proxy protocol. This storage format is simpler and
- therefore less likely to break with future versions of go. As
- a result buildGoModule switched from
- modSha256 to the
- vendorSha256 attribute to pin fetched
- version data.
-
-
-
-
- Grafana is now built without support for phantomjs by default.
- Phantomjs support has been
- deprecated
- in Grafana and the phantomjs project is
- currently
- unmaintained. It can still be enabled by providing
- phantomJsSupport = true to the package
- instantiation:
-
-
-{
- services.grafana.package = pkgs.grafana.overrideAttrs (oldAttrs: rec {
- phantomJsSupport = true;
- });
-}
-
-
-
-
- The
- supybot
- module now uses /var/lib/supybot as its
- default
- stateDir
- path if stateVersion is 20.09 or higher. It
- also enables a number of
- systemd
- sandboxing options which may possibly interfere with
- some plugins. If this is the case you can disable the options
- through attributes in
- systemd.services.supybot.serviceConfig.
-
-
-
-
- The security.duosec.skey option, which
- stored a secret in the nix store, has been replaced by a new
- security.duosec.secretKeyFile
- option for better security.
-
-
- security.duosec.ikey has been renamed to
- security.duosec.integrationKey.
-
-
-
-
- vmware has been removed from the
- services.x11.videoDrivers defaults. For
- VMWare guests set
- virtualisation.vmware.guest.enable to
- true which will include the appropriate
- drivers.
-
-
-
-
- The initrd SSH support now uses OpenSSH rather than Dropbear
- to allow the use of Ed25519 keys and other OpenSSH-specific
- functionality. Host keys must now be in the OpenSSH format,
- and at least one pre-generated key must be specified.
-
-
- If you used the
- boot.initrd.network.ssh.host*Key options,
- you’ll get an error explaining how to convert your host keys
- and migrate to the new
- boot.initrd.network.ssh.hostKeys option.
- Otherwise, if you don’t have any host keys set, you’ll need to
- generate some; see the hostKeys option
- documentation for instructions.
-
-
-
-
- Since this release there’s an easy way to customize your PHP
- install to get a much smaller base PHP with only wanted
- extensions enabled. See the following snippet installing a
- smaller PHP with the extensions imagick,
- opcache, pdo and
- pdo_mysql loaded:
-
-
-{
- environment.systemPackages = [
- (pkgs.php.withExtensions
- ({ all, ... }: with all; [
- imagick
- opcache
- pdo
- pdo_mysql
- ])
- )
- ];
-}
-
-
- The default php attribute hasn’t lost any
- extensions. The opcache extension has been
- added. All upstream PHP extensions are available under
- php.extensions.<name?>.
-
-
- All PHP config flags have been removed for
- the following reasons:
-
-
-
-
- The updated php attribute is now easily
- customizable to your liking by using
- php.withExtensions or
- php.buildEnv instead of writing config
- files or changing configure flags.
-
-
-
-
- The remaining configuration flags can now be set directly on
- the php attribute. For example, instead of
-
-
-{
- php.override {
- config.php.embed = true;
- config.php.apxs2 = false;
- }
-}
-
-
- you should now write
-
-
-{
- php.override {
- embedSupport = true;
- apxs2Support = false;
- }
-}
-
-
-
-
- The ACME module has been overhauled for simplicity and
- maintainability. Cert generation now implicitly uses the
- acme user, and the
- security.acme.certs._name_.user option has
- been removed. Instead, certificate access from other services
- is now managed through group permissions. The module no longer
- runs lego twice under certain conditions, and will correctly
- renew certificates if their configuration is changed. Services
- which reload nginx and httpd after certificate renewal are now
- properly configured too so you no longer have to do this
- manually if you are using HTTPS enabled virtual hosts. A
- mechanism for regenerating certs on demand has also been added
- and documented.
-
-
-
-
- Gollum received a major update to version 5.x and you may have
- to change some links in your wiki when migrating from gollum
- 4.x. More information can be found
- here.
-
-
-
-
- Deluge 2.x was added and is used as default for new NixOS
- installations where stateVersion is >= 20.09. If you are
- upgrading from a previous NixOS version, you can set
- service.deluge.package = pkgs.deluge-2_x to
- upgrade to Deluge 2.x and migrate the state to the new format.
- Be aware that backwards state migrations are not supported by
- Deluge.
-
-
-
-
- Nginx web server now starting with additional
- sandbox/hardening options. By default, write access to
- /var/log/nginx and
- /var/cache/nginx is allowed. To allow
- writing to other folders, use
- systemd.services.nginx.serviceConfig.ReadWritePaths
-
-
-{
- systemd.services.nginx.serviceConfig.ReadWritePaths = [ "/var/www" ];
-}
-
-
- Nginx is also started with the systemd option
- ProtectHome = mkDefault true; which forbids
- it to read anything from /home,
- /root and /run/user (see
- ProtectHome
- docs for details). If you require serving files from
- home directories, you may choose to set e.g.
-
-
-{
- systemd.services.nginx.serviceConfig.ProtectHome = "read-only";
-}
-
-
-
-
- The NixOS options nesting.clone and
- nesting.children have been deleted, and
- replaced with named
- specialisation
- configurations.
-
-
- Replace a nesting.clone entry with:
-
-
-{
- specialisation.example-sub-configuration = {
- configuration = {
- ...
- };
-};
-
-
- Replace a nesting.children entry with:
-
-
-{
- specialisation.example-sub-configuration = {
- inheritParentConfig = false;
- configuration = {
- ...
- };
-};
-
-
- To switch to a specialised configuration at runtime you need
- to run:
-
-
-$ sudo /run/current-system/specialisation/example-sub-configuration/bin/switch-to-configuration test
-
-
- Before you would have used:
-
-
-$ sudo /run/current-system/fine-tune/child-1/bin/switch-to-configuration test
-
-
-
-
- The Nginx log directory has been moved to
- /var/log/nginx, the cache directory to
- /var/cache/nginx. The option
- services.nginx.stateDir has been removed.
-
-
-
-
- The httpd web server previously started its main process as
- root privileged, then ran worker processes as a less
- privileged identity user. This was changed to start all of
- httpd as a less privileged user (defined by
- services.httpd.user
- and
- services.httpd.group).
- As a consequence, all files that are needed for httpd to run
- (included configuration fragments, SSL certificates and keys,
- etc.) must now be readable by this less privileged user/group.
-
-
- The default value for
- services.httpd.mpm
- has been changed from prefork to
- event. Along with this change the default
- value for
- services.httpd.virtualHosts.<name>.http2
- has been set to true.
-
-
-
-
- The systemd-networkd option
- systemd.network.networks.<name>.dhcp.CriticalConnection
- has been removed following upstream systemd’s deprecation of
- the same. It is recommended to use
- systemd.network.networks.<name>.networkConfig.KeepConfiguration
- instead. See systemd.network 5 for details.
-
-
-
-
- The systemd-networkd option
- systemd.network.networks._name_.dhcpConfig
- has been renamed to
- systemd.network.networks.name.dhcpV4Config
- following upstream systemd’s documentation change. See
- systemd.network 5 for details.
-
-
-
-
- In the picom module, several options that
- accepted floating point numbers encoded as strings (for
- example
- services.picom.activeOpacity)
- have been changed to the (relatively) new native
- float type. To migrate your configuration
- simply remove the quotes around the numbers.
-
-
-
-
- When using buildBazelPackage from Nixpkgs,
- flat hash mode is now used for dependencies
- instead of recursive. This is to better
- allow using hashed mirrors where needed. As a result, these
- hashes will have changed.
-
-
-
-
- The syntax of the PostgreSQL configuration file is now checked
- at build time. If your configuration includes a file
- inaccessible inside the build sandbox, set
- services.postgresql.checkConfig to
- false.
-
-
-
-
- The rkt module has been removed, it was archived by upstream.
-
-
-
-
- The
- Bazaar
- VCS is unmaintained and, as consequence of the Python 2 EOL,
- the packages bazaar and
- bazaarTools were removed. Breezy, the
- backward compatible fork of Bazaar (see the
- announcement),
- was packaged as breezy and can be used
- instead.
-
-
- Regarding Nixpkgs, fetchbzr,
- nix-prefetch-bzr and Bazaar support in
- Hydra will continue to work through Breezy.
-
-
-
-
- In addition to the hostname, the fully qualified domain name
- (FQDN), which consists of
- ${networking.hostName} and
- ${networking.domain} is now added to
- /etc/hosts, to allow local FQDN resolution,
- as used by the hostname --fqdn command and
- other applications that try to determine the FQDN. These new
- entries take precedence over entries from the DNS which could
- cause regressions in some very specific setups. Additionally
- the hostname is now resolved to 127.0.0.2
- instead of 127.0.1.1 to be consistent with
- what nss-myhostname (from systemd) returns.
- The old behaviour can e.g. be restored by using
- networking.hosts = lib.mkForce { "127.0.1.1" = [ config.networking.hostName ]; };.
-
-
-
-
- The hostname (networking.hostName) must now
- be a valid DNS label (see RFC 1035, RFC 1123) and as such must
- not contain the domain part. This means that the hostname must
- start with a letter or digit, end with a letter or digit, and
- have as interior characters only letters, digits, and hyphen.
- The maximum length is 63 characters. Additionally it is
- recommended to only use lower-case characters. If (e.g. for
- legacy reasons) a FQDN is required as the Linux kernel network
- node hostname (uname --nodename) the option
- boot.kernel.sysctl."kernel.hostname"
- can be used as a workaround (but be aware of the 64 character
- limit).
-
-
-
-
- The GRUB specific option
- boot.loader.grub.extraInitrd has been
- replaced with the generic option
- boot.initrd.secrets. This option creates a
- secondary initrd from the specified files, rather than using a
- manually created initrd file. Due to an existing bug with
- boot.loader.grub.extraInitrd, it is not
- possible to directly boot an older generation that used that
- option. It is still possible to rollback to that generation if
- the required initrd file has not been deleted.
-
-
-
-
- The
- DNSChain
- package and NixOS module have been removed from Nixpkgs as the
- software is unmaintained and can’t be built. For more
- information see issue
- #89205.
-
-
-
-
- In the resilio module,
- services.resilio.httpListenAddr
- has been changed to listen to [::1] instead
- of 0.0.0.0.
-
-
-
-
- sslh has been updated to version
- 1.21. The ssl probe must
- be renamed to tls in
- services.sslh.appendConfig.
-
-
-
-
- Users of OpenAFS
- 1.6 must upgrade their services to OpenAFS 1.8! In this
- release, the OpenAFS package version 1.6.24 is marked broken
- but can be used during transition to OpenAFS 1.8.x. Use the
- options
- services.openafsClient.packages.module,
- services.openafsClient.packages.programs
- and services.openafsServer.package to
- select a different OpenAFS package. OpenAFS 1.6 will be
- removed in the next release. The package
- openafs and the service options will then
- silently point to the OpenAFS 1.8 release.
-
-
- See also the OpenAFS
- Administrator
- Guide for instructions. Beware of the following when
- updating servers:
-
-
-
-
- The storage format of the server key has changed and the
- key must be converted before running the new release.
-
-
-
-
- When updating multiple database servers, turn off the
- database servers from the highest IP down to the lowest
- with resting periods in between. Start up in reverse
- order. Do not concurrently run database servers working
- with different OpenAFS releases!
-
-
-
-
- Update servers first, then clients.
-
-
-
-
-
-
- Radicale’s default package has changed from 2.x to 3.x. An
- upgrade checklist can be found
- here.
- You can use the newer version in the NixOS service by setting
- the package to
- radicale3, which is done automatically if
- stateVersion is 20.09 or higher.
-
-
-
-
- udpt experienced a complete rewrite from
- C++ to rust. The configuration format changed from ini to
- toml. The new configuration documentation can be found at
- the
- official website and example configuration is packaged
- in ${udpt}/share/udpt/udpt.toml.
-
-
-
-
- We now have a unified
- services.xserver.displayManager.autoLogin
- option interface to be used for every display-manager in
- NixOS.
-
-
-
-
- The bitcoind module has changed to
- multi-instance, using submodules. Therefore, it is now
- mandatory to name each instance. To use this new
- multi-instance config with an existing bitcoind data directory
- and user, you have to adjust the original config, e.g.:
-
-
-{
- services.bitcoind = {
- enable = true;
- extraConfig = "...";
- ...
- };
-}
-
-
- To something similar:
-
-
-{
- services.bitcoind.mainnet = {
- enable = true;
- dataDir = "/var/lib/bitcoind";
- user = "bitcoin";
- extraConfig = "...";
- ...
- };
-}
-
-
- The key settings are:
-
-
-
-
- dataDir - to continue using the same
- data directory.
-
-
-
-
- user - to continue using the same user
- so that bitcoind maintains access to its files.
-
-
-
-
-
-
- Graylog introduced a change in the LDAP server certificate
- validation behaviour for version 3.3.3 which might break
- existing setups. When updating Graylog from a version before
- 3.3.3 make sure to check the Graylog
- release
- info for information on how to avoid the issue.
-
-
-
-
- The dokuwiki module has changed to
- multi-instance, using submodules. Therefore, it is now
- mandatory to name each instance. Moreover, forcing SSL by
- default has been dropped, so nginx.forceSSL
- and nginx.enableACME are no longer set to
- true. To continue using your service with
- the original SSL settings, you have to adjust the original
- config, e.g.:
-
-
-{
- services.dokuwiki = {
- enable = true;
- ...
- };
-}
-
-
- To something similar:
-
-
-{
- services.dokuwiki."mywiki" = {
- enable = true;
- nginx = {
- forceSSL = true;
- enableACME = true;
- };
- ...
- };
-}
-
-
- The base package has also been upgraded to the 2020-07-29
- Hogfather release. Plugins might be
- incompatible or require upgrading.
-
-
-
-
- The
- services.postgresql.dataDir
- option is now set to
- "/var/lib/postgresql/${cfg.package.psqlSchema}"
- regardless of your
- system.stateVersion.
- Users with an existing postgresql install that have a
- system.stateVersion
- of 17.03 or below should double check what
- the value of their
- services.postgresql.dataDir
- option is (/var/db/postgresql) and then
- explicitly set this value to maintain compatibility:
-
-
-{
- services.postgresql.dataDir = "/var/db/postgresql";
-}
-
-
- The postgresql module now expects there to be a database super
- user account called postgres regardless of
- your
- system.stateVersion.
- Users with an existing postgresql install that have a
- system.stateVersion
- of 17.03 or below should run the following
- SQL statements as a database super admin user before
- upgrading:
-
-
-CREATE ROLE postgres LOGIN SUPERUSER;
-
-
-
-
- The USBGuard module now removes options and instead hardcodes
- values for IPCAccessControlFiles,
- ruleFiles, and
- auditFilePath. Audit logs can be found in
- the journal.
-
-
-
-
- The NixOS module system now evaluates option definitions more
- strictly, allowing it to detect a larger set of problems. As a
- result, what previously evaluated may not do so anymore. See
- the
- PR that changed this for more info.
-
-
-
-
- For NixOS configuration options, the type
- loaOf, after its initial deprecation in
- release 20.03, has been removed. In NixOS and Nixpkgs options
- using this type have been converted to
- attrsOf. For more information on this
- change have look at these links:
- issue
- #1800,
- PR
- #63103.
-
-
-
-
- config.systemd.services.${name}.path now
- returns a list of paths instead of a colon-separated string.
-
-
-
-
- Caddy module now uses Caddy v2 by default. Caddy v1 can still
- be used by setting
- services.caddy.package
- to pkgs.caddy1.
-
-
- New option
- services.caddy.adapter
- has been added.
-
-
-
-
- The
- jellyfin
- module will use and stay on the Jellyfin version
- 10.5.5 if stateVersion
- is lower than 20.09. This is because
- significant changes were made to the database schema, and it
- is highly recommended to backup your instance before
- upgrading. After making your backup, you can upgrade to the
- latest version either by setting your
- stateVersion to 20.09 or
- higher, or set the
- services.jellyfin.package to
- pkgs.jellyfin. If you do not wish to
- upgrade Jellyfin, but want to change your
- stateVersion, you can set the value of
- services.jellyfin.package to
- pkgs.jellyfin_10_5.
-
-
-
-
- The security.rngd service is now disabled
- by default. This choice was made because there’s krngd in the
- linux kernel space making it (for most usecases) functionally
- redundent.
-
-
-
-
- The hardware.nvidia.optimus_prime.enable
- service has been renamed to
- hardware.nvidia.prime.sync.enable and has
- many new enhancements. Related nvidia prime settings may have
- also changed.
-
-
-
-
- The package nextcloud17 has been removed and nextcloud18 was
- marked as insecure since both of them will
-
- will be EOL (end of life) within the lifetime of 20.09.
-
-
- It’s necessary to upgrade to nextcloud19:
-
-
-
-
- From nextcloud17, you have to upgrade to nextcloud18 first
- as Nextcloud doesn’t allow going multiple major revisions
- forward in a single upgrade. This is possible by setting
- services.nextcloud.package
- to nextcloud18.
-
-
-
-
- From nextcloud18, it’s possible to directly upgrade to
- nextcloud19 by setting
- services.nextcloud.package
- to nextcloud19.
-
-
-
-
-
-
- The GNOME desktop manager no longer default installs
- gnome3.epiphany. It was chosen to do this as it has a
- usability breaking issue (see issue
- #98819)
- that makes it unsuitable to be a default app.
-
-
-
- Issue
- #98819
- is now fixed and gnome3.epiphany is once again installed by
- default.
-
-
-
-
-
- If you want to manage the configuration of wpa_supplicant
- outside of NixOS you must ensure that none of
- networking.wireless.networks,
- networking.wireless.extraConfig
- or
- networking.wireless.userControlled.enable
- is being used or true. Using any of those
- options will cause wpa_supplicant to be started with a NixOS
- generated configuration file instead of your own.
-
-
-
-
-
- Other Notable Changes
-
-
-
- SD images are now compressed by default using
- zstd. The compression for ISO images has
- also been changed to zstd, but ISO images
- are still not compressed by default.
-
-
-
-
- services.journald.rateLimitBurst was
- updated from 1000 to
- 10000 to follow the new upstream systemd
- default.
-
-
-
-
- The notmuch package moves its emacs-related binaries and emacs
- lisp files to a separate output. They’re not part of the
- default out output anymore - if you relied
- on the notmuch-emacs-mua binary or the
- emacs lisp files, access them via the
- notmuch.emacs output.
-
-
-
-
- Device tree overlay support was improved in
- #79370
- and now uses
- hardware.deviceTree.kernelPackage
- instead of hardware.deviceTree.base.
- hardware.deviceTree.overlays
- configuration was extended to support .dts
- files with symbols. Device trees can now be filtered by
- setting
- hardware.deviceTree.filter
- option.
-
-
-
-
- The default output of buildGoPackage is now
- $out instead of $bin.
-
-
-
-
- buildGoModuledoCheck
- now defaults to true.
-
-
-
-
- Packages built using buildRustPackage now
- use release mode for the
- checkPhase by default.
-
-
- Please note that Rust packages utilizing a custom
- build/install procedure (e.g. by using a
- Makefile) or test suites that rely on the
- structure of the target/ directory may
- break due to those assumptions. For further information,
- please read the Rust section in the Nixpkgs manual.
-
-
-
-
- The cc- and binutils-wrapper’s infix salt and
- _BUILD_ and _TARGET_
- user infixes have been replaced with with a suffix
- salt and suffixes and _FOR_BUILD
- and _FOR_TARGET. This matches the autotools
- convention for env vars which standard for these things,
- making interfacing with other tools easier.
-
-
-
-
- Additional Git documentation (HTML and text files) is now
- available via the git-doc package.
-
-
-
-
- Default algorithm for ZRAM swap was changed to
- zstd.
-
-
-
-
- The installer now enables sshd by default. This improves
- installation on headless machines especially ARM
- single-board-computer. To login through ssh, either a password
- or an ssh key must be set for the root user or the nixos user.
-
-
-
-
- The scripted networking system now uses
- .link files in
- /etc/systemd/network to configure mac
- address and link MTU, instead of the sometimes buggy
- network-link-* units, which have been
- removed. Bringing the interface up has been moved to the
- beginning of the network-addresses-* unit.
- Note this doesn’t require systemd-networkd
- - it’s udev that parses .link files. Extra
- care needs to be taken in the presence of
- legacy
- udev rules to rename interfaces, as MAC Address and MTU
- defined in these options can only match on the original link
- name. In such cases, you most likely want to create a
- 10-*.link file through
- systemd.network.links
- and set both name and MAC Address / MTU there.
-
-
-
-
- Grafana received a major update to version 7.x. A plugin is
- now needed for image rendering support, and plugins must now
- be signed by default. More information can be found
- in
- the Grafana documentation.
-
-
-
-
- The hardware.u2f module, which was
- installing udev rules was removed, as udev gained native
- support to handle FIDO security tokens.
-
-
-
-
- The services.transmission module was
- enhanced with the new options:
- services.transmission.credentialsFile,
- services.transmission.openFirewall,
- and
- services.transmission.performanceNetParameters.
-
-
- transmission-daemon is now started with
- additional systemd sandbox/hardening options for better
- security. Please
- report
- any use case where this is not working well. In particular,
- the RootDirectory option newly set forbids
- uploading or downloading a torrent outside of the default
- directory configured at
- settings.download-dir.
- If you really need Transmission to access other directories,
- you must include those directories into the
- BindPaths of the service:
-
-
-{
- systemd.services.transmission.serviceConfig.BindPaths = [ "/path/to/alternative/download-dir" ];
-}
-
-
- Also, connection to the RPC (Remote Procedure Call) of
- transmission-daemon is now only available
- on the local network interface by default. Use:
-
-
-{
- services.transmission.settings.rpc-bind-address = "0.0.0.0";
-}
-
-
- to get the previous behavior of listening on all network
- interfaces.
-
-
-
-
- With this release systemd-networkd (when
- enabled through
- networking.useNetworkd)
- has it’s netlink socket created through a
- systemd.socket unit. This gives us control
- over socket buffer sizes and other parameters. For larger
- setups where networkd has to create a lot of (virtual) devices
- the default buffer size (currently 128MB) is not enough.
-
-
- On a machine with >100 virtual interfaces (e.g., wireguard
- tunnels, VLANs, …), that all have to be brought up during
- system startup, the receive buffer size will spike for a brief
- period. Eventually some of the message will be dropped since
- there is not enough (permitted) buffer space available.
-
-
- By having systemd-networkd start with a
- netlink socket created by systemd we can
- configure the ReceiveBufferSize= parameter
- in the socket options (i.e.
- systemd.sockets.systemd-networkd.socketOptions.ReceiveBufferSize)
- without recompiling systemd-networkd.
-
-
- Since the actual memory requirements depend on hardware,
- timing, exact configurations etc. it isn’t currently possible
- to infer a good default from within the NixOS module system.
- Administrators are advised to monitor the logs of
- systemd-networkd for
- rtnl: kernel receive buffer overrun spam
- and increase the memory limit as they see fit.
-
-
- Note: Increasing the ReceiveBufferSize=
- doesn’t allocate any memory. It just increases the upper bound
- on the kernel side. The memory allocation depends on the
- amount of messages that are queued on the kernel side of the
- netlink socket.
-
-
-
-
- Specifying
- mailboxes
- in the dovecot2 module as a list is deprecated and will break
- eval in 21.05. Instead, an attribute-set should be specified
- where the name should be the key of the
- attribute.
-
-
- This means that a configuration like this
-
-
-{
- services.dovecot2.mailboxes = [
- { name = "Junk";
- auto = "create";
- }
- ];
-}
-
-
- should now look like this:
-
-
-{
- services.dovecot2.mailboxes = {
- Junk.auto = "create";
- };
-}
-
-
-
-
- netbeans was upgraded to 12.0 and now defaults to OpenJDK 11.
- This might cause problems if your projects depend on packages
- that were removed in Java 11.
-
-
-
-
- nextcloud has been updated to
- v19.
-
-
- If you have an existing installation, please make sure that
- you’re on nextcloud18 before upgrading to nextcloud19 since
- Nextcloud doesn’t support upgrades across multiple major
- versions.
-
-
-
-
- The nixos-run-vms script now deletes the
- previous run machines states on test startup. You can use the
- --keep-vm-state flag to match the previous
- behaviour and keep the same VM state between different test
- runs.
-
-
-
-
- The
- nix.buildMachines
- option is now type-checked. There are no functional changes,
- however this may require updating some configurations to use
- correct types for all attributes.
-
-
-
-
- The fontconfig module stopped generating
- config and cache files for fontconfig 2.10.x, the
- /etc/fonts/fonts.conf now belongs to the
- latest fontconfig, just like on other Linux distributions, and
- we will
- no
- longer be versioning the config directories.
-
-
- Fontconfig 2.10.x was removed from Nixpkgs since it hasn’t
- been used in any Nixpkgs package for years now.
-
-
-
-
- Nginx module
- nginxModules.fastcgi-cache-purge renamed to
- official name nginxModules.cache-purge.
- Nginx module nginxModules.ngx_aws_auth
- renamed to official name
- nginxModules.aws-auth.
-
-
-
-
- The option defaultPackages was added. It
- installs the packages perl, rsync and strace for now. They
- were added unconditionally to
- systemPackages before, but are not strictly
- necessary for a minimal NixOS install. You can set it to an
- empty list to have a more minimal system. Be aware that some
- functionality might still have an impure dependency on those
- packages, so things might break.
-
-
-
-
- The undervolt option no longer needs to
- apply its settings every 30s. If they still become undone,
- open an issue and restore the previous behaviour using
- undervolt.useTimer.
-
-
-
-
- Agda has been heavily reworked.
-
-
-
-
- agda.mkDerivation has been heavily
- changed and is now located at agdaPackages.mkDerivation.
-
-
-
-
- New top-level packages agda and
- agda.withPackages have been added, the
- second of which sets up agda with access to chosen
- libraries.
-
-
-
-
- All agda libraries now live under
- agdaPackages.
-
-
-
-
- Many broken libraries have been removed.
-
-
-
-
- See the
- new
- documentation for more information.
-
-
-
-
- The deepin package set has been removed
- from nixpkgs. It was a work in progress to package the
- Deepin
- Desktop Environment (DDE), including libraries, tools
- and applications, and it was still missing a service to launch
- the desktop environment. It has shown to no longer be a
- feasible goal due to reasons discussed in
- issue
- #94870. The package
- netease-cloud-music has also been removed,
- as it depends on libraries from deepin.
-
-
-
-
- The opendkim module now uses systemd
- sandboxing features to limit the exposure of the system
- towards the opendkim service.
-
-
-
-
- Kubernetes has been upgraded to 1.19.1, which also means that
- the golang version to build it has been bumped to 1.15. This
- may have consequences for your existing clusters and their
- certificates. Please consider
-
- the release notes for Kubernetes 1.19 carefully before
- upgrading.
-
-
-
-
- For AMD GPUs, Vulkan can now be used by adding
- amdvlk to
- hardware.opengl.extraPackages.
-
-
-
-
- Similarly, still for AMD GPUs, the ROCm OpenCL stack can now
- be used by adding rocm-opencl-icd to
- hardware.opengl.extraPackages.
-
-
-
-
-
- Contributions
-
- I, Jonathan Ringer, would like to thank the following individuals
- for their work on nixpkgs. This release could not be done without
- the hard work of the NixOS community. There were 31282
- contributions across 1313 contributors.
-
-
-
-
- 2288 Mario Rodas
-
-
-
-
- 1837 Frederik Rietdijk
-
-
-
-
- 946 Jörg Thalheim
-
-
-
-
- 925 Maximilian Bosch
-
-
-
-
- 687 Jonathan Ringer
-
-
-
-
- 651 Jan Tojnar
-
-
-
-
- 622 Daniël de Kok
-
-
-
-
- 605 WORLDofPEACE
-
-
-
-
- 597 Florian Klink
-
-
-
-
- 528 José Romildo Malaquias
-
-
-
-
- 281 volth
-
-
-
-
- 101 Robert Scott
-
-
-
-
- 86 Tim Steinbach
-
-
-
-
- 76 WORLDofPEACE
-
-
-
-
- 49 Maximilian Bosch
-
-
-
-
- 42 Thomas Tuegel
-
-
-
-
- 37 Doron Behar
-
-
-
-
- 36 Vladimír Čunát
-
-
-
-
- 27 Jonathan Ringer
-
-
-
-
- 27 Maciej Krüger
-
-
-
-
- I, Jonathan Ringer, would also like to personally thank
- @WORLDofPEACE for their help in mentoring me on the release
- process. Special thanks also goes to Thomas Tuegel for helping
- immensely with stabilizing Qt, KDE, and Plasma5; I would also like
- to thank Robert Scott for his numerous fixes and pull request
- reviews.
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-2105.section.xml b/nixos/doc/manual/from_md/release-notes/rl-2105.section.xml
deleted file mode 100644
index 868c1709879d..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-2105.section.xml
+++ /dev/null
@@ -1,1568 +0,0 @@
-
- Release 21.05 (<quote>Okapi</quote>, 2021.05/31)
-
- Support is planned until the end of December 2021, handing over to
- 21.11.
-
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- Core version changes:
-
-
-
-
- gcc: 9.3.0 -> 10.3.0
-
-
-
-
- glibc: 2.30 -> 2.32
-
-
-
-
- default linux: 5.4 -> 5.10, all supported kernels
- available
-
-
-
-
- mesa: 20.1.7 -> 21.0.1
-
-
-
-
-
-
- Desktop Environments:
-
-
-
-
- GNOME: 3.36 -> 40, see its
- release
- notes
-
-
-
-
- Plasma5: 5.18.5 -> 5.21.3
-
-
-
-
- kdeApplications: 20.08.1 -> 20.12.3
-
-
-
-
- cinnamon: 4.6 -> 4.8.1
-
-
-
-
-
-
- Programming Languages and Frameworks:
-
-
-
-
- Python optimizations were disabled again. Builds with
- optimizations enabled are not reproducible. Optimizations
- can now be enabled with an option.
-
-
-
-
-
-
- The linux_latest kernel was updated to the 5.13 series. It
- currently is not officially supported for use with the zfs
- filesystem. If you use zfs, you should use a different kernel
- version (either the LTS kernel, or track a specific one).
-
-
-
-
-
- New Services
-
- The following new services were added since the last release:
-
-
-
-
- GNURadio
- 3.8 and 3.9 were
- finally
- packaged, along with a rewrite to the Nix expressions,
- allowing users to override the features upstream supports
- selecting to compile or not to. Additionally, the attribute
- gnuradio (3.9),
- gnuradio3_8 and
- gnuradio3_7 now point to an externally
- wrapped by default derivations, that allow you to also add
- `extraPythonPackages` to the Python interpreter used by
- GNURadio. Missing environmental variables needed for
- operational GUI were also added
- (#75478).
-
-
-
-
- Keycloak,
- an open source identity and access management server with
- support for
- OpenID
- Connect, OAUTH
- 2.0 and
- SAML
- 2.0.
-
-
- See the Keycloak
- section of the NixOS manual for more information.
-
-
-
-
- services.samba-wsdd.enable
- Web Services Dynamic Discovery host daemon
-
-
-
-
- Discourse,
- a modern and open source discussion platform.
-
-
- See the Discourse
- section of the NixOS manual for more information.
-
-
-
-
- services.nebula.networks
- Nebula
- VPN
-
-
-
-
-
- Backward Incompatibilities
-
- When upgrading from a previous release, please be aware of the
- following incompatible changes:
-
-
-
-
- GNOME desktop environment was upgraded to 40, see the release
- notes for
- 40.0
- and
- 3.38.
- The gnome3 attribute set has been renamed
- to gnome and so have been the NixOS
- options.
-
-
-
-
- If you are using services.udev.extraRules
- to assign custom names to network interfaces, this may stop
- working due to a change in the initialisation of dhcpcd and
- systemd networkd. To avoid this, either move them to
- services.udev.initrdRules or see the new
- Assigning custom
- names section of the NixOS manual for an example using
- networkd links.
-
-
-
-
- The security.hideProcessInformation module
- has been removed. It was broken since the switch to
- cgroups-v2.
-
-
-
-
- The linuxPackages.ati_drivers_x11 kernel
- modules have been removed. The drivers only supported kernels
- prior to 4.2, and thus have become obsolete.
-
-
-
-
- The systemConfig kernel parameter is no
- longer added to boot loader entries. It has been unused since
- September 2010, but if do have a system generation from that
- era, you will now be unable to boot into them.
-
-
-
-
- systemd-journal2gelf no longer parses json
- and expects the receiving system to handle it. How to achieve
- this with Graylog is described in this
- GitHub
- issue.
-
-
-
-
- If the services.dbus module is enabled,
- then the user D-Bus session is now always socket activated.
- The associated options
- services.dbus.socketActivated and
- services.xserver.startDbusSession have
- therefore been removed and you will receive a warning if they
- are present in your configuration. This change makes the user
- D-Bus session available also for non-graphical logins.
-
-
-
-
- The networking.wireless.iwd module now
- installs the upstream-provided 80-iwd.link file, which sets
- the NamePolicy= for all wlan devices to keep
- kernel, to avoid race conditions between iwd and
- networkd. If you don’t want this, you can set
- systemd.network.links."80-iwd" = lib.mkForce {}.
-
-
-
-
- rubyMinimal was removed due to being unused
- and unusable. The default ruby interpreter includes JIT
- support, which makes it reference it’s compiler. Since JIT
- support is probably needed by some Gems, it was decided to
- enable this feature with all cc references by default, and
- allow to build a Ruby derivation without references to cc, by
- setting jitSupport = false; in an overlay.
- See
- #90151
- for more info.
-
-
-
-
- Setting
- services.openssh.authorizedKeysFiles now
- also affects which keys
- security.pam.enableSSHAgentAuth will use.
- WARNING: If you are using these options in combination do make
- sure that any key paths you use are present in
- services.openssh.authorizedKeysFiles!
-
-
-
-
- The option fonts.enableFontDir has been
- renamed to
- fonts.fontDir.enable.
- The path of font directory has also been changed to
- /run/current-system/sw/share/X11/fonts, for
- consistency with other X11 resources.
-
-
-
-
- A number of options have been renamed in the kicad interface.
- oceSupport has been renamed to
- withOCE, withOCCT has
- been renamed to withOCC,
- ngspiceSupport has been renamed to
- withNgspice, and
- scriptingSupport has been renamed to
- withScripting. Additionally,
- kicad/base.nix no longer provides default
- argument values since these are provided by
- kicad/default.nix.
-
-
-
-
- The socket for the pdns-recursor module was
- moved from /var/lib/pdns-recursor to
- /run/pdns-recursor to match upstream.
-
-
-
-
- Paperwork was updated to version 2. The on-disk format
- slightly changed, and it is not possible to downgrade from
- Paperwork 2 back to Paperwork 1.3. Back your documents up
- before upgrading. See
- this
- thread for more details.
-
-
-
-
- PowerDNS has been updated from 4.2.x to
- 4.3.x. Please be sure to review the
- Upgrade
- Notes provided by upstream before upgrading. Worth
- specifically noting is that the service now runs entirely as a
- dedicated pdns user, instead of starting as
- root and dropping privileges, as well as
- the default socket-dir location changing
- from /var/lib/powerdns to
- /run/pdns.
-
-
-
-
- The mediatomb service is now using by
- default the new and maintained fork gerbera
- package instead of the unmaintained
- mediatomb package. If you want to keep the
- old behavior, you must declare it with:
-
-
-{
- services.mediatomb.package = pkgs.mediatomb;
-}
-
-
- One new option openFirewall has been
- introduced which defaults to false. If you relied on the
- service declaration to add the firewall rules itself before,
- you should now declare it with:
-
-
-{
- services.mediatomb.openFirewall = true;
-}
-
-
-
-
- xfsprogs was update from 4.19 to 5.11. It now enables reflink
- support by default on filesystem creation. Support for
- reflinks was added with an experimental status to kernel 4.9
- and deemed stable in kernel 4.16. If you want to be able to
- mount XFS filesystems created with this release of xfsprogs on
- kernel releases older than those, you need to format them with
- mkfs.xfs -m reflink=0.
-
-
-
-
- The uWSGI server is now built with POSIX capabilities. As a
- consequence, root is no longer required in emperor mode and
- the service defaults to running as the unprivileged
- uwsgi user. Any additional capability can
- be added via the new option
- services.uwsgi.capabilities.
- The previous behaviour can be restored by setting:
-
-
-{
- services.uwsgi.user = "root";
- services.uwsgi.group = "root";
- services.uwsgi.instance =
- {
- uid = "uwsgi";
- gid = "uwsgi";
- };
-}
-
-
- Another incompatibility from the previous release is that
- vassals running under a different user or group need to use
- immediate-{uid,gid} instead of the usual
- uid,gid options.
-
-
-
-
- btc1 has been abandoned upstream, and removed.
-
-
-
-
- cpp_ethereum (aleth) has been abandoned upstream, and removed.
-
-
-
-
- riak-cs package removed along with
- services.riak-cs module.
-
-
-
-
- stanchion package removed along with
- services.stanchion module.
-
-
-
-
- mutt has been updated to a new major version (2.x), which
- comes with some backward incompatible changes that are
- described in the
- release
- notes for Mutt 2.0.
-
-
-
-
- vim and neovim switched
- to Python 3, dropping all Python 2 support.
-
-
-
-
- networking.wireguard.interfaces.<name>.generatePrivateKeyFile,
- which is off by default, had a chmod race
- condition fixed. As an aside, the parent directory’s
- permissions were widened, and the key files were made
- owner-writable. This only affects newly created keys. However,
- if the exact permissions are important for your setup, read
- #121294.
-
-
-
-
- boot.zfs.forceImportAll
- previously did nothing, but has been fixed. However its
- default has been changed to false to
- preserve the existing default behaviour. If you have this
- explicitly set to true, please note that
- your non-root pools will now be forcibly imported.
-
-
-
-
- openafs now points to openafs_1_8, which is the new stable
- release. OpenAFS 1.6 was removed.
-
-
-
-
- The WireGuard module gained a new option
- networking.wireguard.interfaces.<name>.peers.*.dynamicEndpointRefreshSeconds
- that implements refreshing the IP of DNS-based endpoints
- periodically (which WireGuard itself
- cannot
- do).
-
-
-
-
- MariaDB has been updated to 10.5. Before you upgrade, it would
- be best to take a backup of your database and read
-
- Incompatible Changes Between 10.4 and 10.5. After the
- upgrade you will need to run mysql_upgrade.
-
-
-
-
- The TokuDB storage engine dropped in mariadb 10.5 and removed
- in mariadb 10.6. It is recommended to switch to RocksDB. See
- also
- TokuDB
- and
- MDEV-19780:
- Remove the TokuDB storage engine.
-
-
-
-
- The openldap module now has support for
- OLC-style configuration, users of the
- configDir option may wish to migrate. If
- you continue to use configDir, ensure that
- olcPidFile is set to
- /run/slapd/slapd.pid.
-
-
- As a result, extraConfig and
- extraDatabaseConfig are removed. To help
- with migration, you can convert your
- slapd.conf file to OLC configuration with
- the following script (find the location of this configuration
- file by running systemctl status openldap,
- it is the -f option.
-
-
-$ TMPDIR=$(mktemp -d)
-$ slaptest -f /path/to/slapd.conf -F $TMPDIR
-$ slapcat -F $TMPDIR -n0 -H 'ldap:///???(!(objectClass=olcSchemaConfig))'
-
-
- This will dump your current configuration in LDIF format,
- which should be straightforward to convert into Nix settings.
- This does not show your schema configuration, as this is
- unnecessarily verbose for users of the default schemas and
- slaptest is buggy with schemas directly in
- the config file.
-
-
-
-
- Amazon EC2 and OpenStack Compute (nova) images now re-fetch
- instance meta data and user data from the instance metadata
- service (IMDS) on each boot. For example: stopping an EC2
- instance, changing its user data, and restarting the instance
- will now cause it to fetch and apply the new user data.
-
-
-
- Specifically, /etc/ec2-metadata is
- re-populated on each boot. Some NixOS scripts that read from
- this directory are guarded to only run if the files they
- want to manipulate do not already exist, and so will not
- re-apply their changes if the IMDS response changes.
- Examples: root’s SSH key is only added if
- /root/.ssh/authorized_keys does not
- exist, and SSH host keys are only set from user data if they
- do not exist in /etc/ssh.
-
-
-
-
-
- The rspamd services is now sandboxed. It is
- run as a dynamic user instead of root, so secrets and other
- files may have to be moved or their permissions may have to be
- fixed. The sockets are now located in
- /run/rspamd instead of
- /run.
-
-
-
-
- Enabling the Tor client no longer silently also enables and
- configures Privoxy, and the
- services.tor.client.privoxy.enable option
- has been removed. To enable Privoxy, and to configure it to
- use Tor’s faster port, use the following configuration:
-
-
-{
- opt-services.privoxy.enable = true;
- opt-services.privoxy.enableTor = true;
-}
-
-
-
-
- The services.tor module has a new
- exhaustively typed
- services.tor.settings
- option following RFC 0042; backward compatibility with old
- options has been preserved when aliasing was possible. The
- corresponding systemd service has been hardened, but there is
- a chance that the service still requires more permissions, so
- please report any related trouble on the bugtracker. Onion
- services v3 are now supported in
- services.tor.relay.onionServices.
- A new
- services.tor.openFirewall
- option as been introduced for allowing connections on all the
- TCP ports configured.
-
-
-
-
- The options
- services.slurm.dbdserver.storagePass and
- services.slurm.dbdserver.configFile have
- been removed. Use
- services.slurm.dbdserver.storagePassFile
- instead to provide the database password. Extra config options
- can be given via the option
- services.slurm.dbdserver.extraConfig. The
- actual configuration file is created on the fly on startup of
- the service. This avoids that the password gets exposed in the
- nix store.
-
-
-
-
- The wafHook hook does not wrap Python
- anymore. Packages depending on wafHook need
- to include any Python into their
- nativeBuildInputs.
-
-
-
-
- Starting with version 1.7.0, the project formerly named
- CodiMD is now named
- HedgeDoc. New installations will no longer
- use the old name for users, state directories and such, this
- needs to be considered when moving state to a more recent
- NixOS installation. Based on
- system.stateVersion,
- existing installations will continue to work.
-
-
-
-
- The fish-foreign-env package has been replaced with
- fishPlugins.foreign-env, in which the fish functions have been
- relocated to the vendor_functions.d
- directory to be loaded automatically.
-
-
-
-
- The prometheus json exporter is now managed by the prometheus
- community. Together with additional features some backwards
- incompatibilities were introduced. Most importantly the
- exporter no longer accepts a fixed command-line parameter to
- specify the URL of the endpoint serving JSON. It now expects
- this URL to be passed as an URL parameter, when scraping the
- exporter’s /probe endpoint. In the
- prometheus scrape configuration the scrape target might look
- like this:
-
-
-http://some.json-exporter.host:7979/probe?target=https://example.com/some/json/endpoint
-
-
- Existing configuration for the exporter needs to be updated,
- but can partially be re-used. Documentation is available in
- the upstream repository and a small example for NixOS is
- available in the corresponding NixOS test.
-
-
- These changes also affect
- services.prometheus.exporters.rspamd.enable,
- which is just a preconfigured instance of the json exporter.
-
-
- For more information, take a look at the
-
- official documentation of the json_exporter.
-
-
-
-
- Androidenv was updated, removing the
- includeDocs and
- lldbVersions arguments. Docs only covered a
- single version of the Android SDK, LLDB is now bundled with
- the NDK, and both are no longer available to download from the
- Android package repositories. Additionally, since the package
- lists have been updated, some older versions of Android
- packages may not be bundled. If you depend on older versions
- of Android packages, we recommend overriding the repo.
-
-
- Android packages are now loaded from a repo.json file created
- by parsing Android repo XML files. The arguments
- repoJson and repoXmls
- have been added to allow overriding the built-in androidenv
- repo.json with your own. Additionally, license files are now
- written to allow compatibility with Gradle-based tools, and
- the extraLicenses argument has been added
- to accept more SDK licenses if your project requires it. See
- the androidenv documentation for more details.
-
-
-
-
- The attribute mpi is now consistently used
- to provide a default, system-wide MPI implementation. The
- default implementation is openmpi, which has been used before
- by all derivations affects by this change. Note that all
- packages that have used mpi ? null in the
- input for optional MPI builds, have been changed to the
- boolean input paramater useMpi to enable
- building with MPI. Building all packages with
- mpich instead of the default
- openmpi can now be achived like this:
-
-
-self: super:
-{
- mpi = super.mpich;
-}
-
-
-
-
- The Searx module has been updated with the ability to
- configure the service declaratively and uWSGI integration. The
- option services.searx.configFile has been
- renamed to
- services.searx.settingsFile
- for consistency with the new
- services.searx.settings.
- In addition, the searx uid and gid
- reservations have been removed since they were not necessary:
- the service is now running with a dynamically allocated uid.
-
-
-
-
- The libinput module has been updated with the ability to
- configure mouse and touchpad settings separately. The options
- in services.xserver.libinput have been
- renamed to
- services.xserver.libinput.touchpad, while
- there is a new
- services.xserver.libinput.mouse for mouse
- related configuration.
-
-
- Since touchpad options no longer apply to all devices, you may
- want to replicate your touchpad configuration in mouse
- section.
-
-
-
-
- ALSA OSS emulation
- (sound.enableOSSEmulation) is now disabled
- by default.
-
-
-
-
- Thinkfan as been updated to 1.2.x, which
- comes with a new YAML based configuration format. For this
- reason, several NixOS options of the thinkfan module have been
- changed to non-backward compatible types. In addition, a new
- services.thinkfan.settings
- option has been added.
-
-
- Please read the
-
- thinkfan documentation before updating.
-
-
-
-
- Adobe Flash Player support has been dropped from the tree. In
- particular, the following packages no longer support it:
-
-
-
-
- chromium
-
-
-
-
- firefox
-
-
-
-
- qt48
-
-
-
-
- qt5.qtwebkit
-
-
-
-
- Additionally, packages flashplayer and hal-flash were removed
- along with the services.flashpolicyd
- module.
-
-
-
-
- The security.rngd module has been removed.
- It was disabled by default in 20.09 as it was functionally
- redundant with krngd in the linux kernel. It is not necessary
- for any device that the kernel recognises as an hardware RNG,
- as it will automatically run the krngd task to periodically
- collect random data from the device and mix it into the
- kernel’s RNG.
-
-
- The default SMTP port for GitLab has been changed to
- 25 from its previous default of
- 465. If you depended on this default, you
- should now set the
- services.gitlab.smtp.port
- option.
-
-
-
-
- The default version of ImageMagick has been updated from 6 to
- 7. You can use imagemagick6, imagemagick6_light, and
- imagemagick6Big if you need the older version.
-
-
-
-
- services.xserver.videoDrivers
- no longer uses the deprecated cirrus and
- vesa device dependent X drivers by default.
- It also enables both amdgpu and
- nouveau drivers by default now.
-
-
-
-
- The kindlegen package is gone, because it
- is no longer supported or hosted by Amazon. Sadly, its
- replacement, Kindle Previewer, has no Linux support. However,
- there are other ways to generate MOBI files. See
- the
- discussion for more info.
-
-
-
-
- The apacheKafka packages are now built with version-matched
- JREs. Versions 2.6 and above, the ones that recommend it, use
- jdk11, while versions below remain on jdk8. The NixOS service
- has been adjusted to start the service using the same version
- as the package, adjustable with the new
- services.apache-kafka.jre
- option. Furthermore, the default list of
- services.apache-kafka.jvmOptions
- have been removed. You should set your own according to the
- upstream
- documentation for your Kafka version.
-
-
-
-
- The kodi package has been modified to allow concise addon
- management. Consider the following configuration from previous
- releases of NixOS to install kodi, including the
- kodiPackages.inputstream-adaptive and kodiPackages.vfs-sftp
- addons:
-
-
-{
- environment.systemPackages = [
- pkgs.kodi
- ];
-
- nixpkgs.config.kodi = {
- enableInputStreamAdaptive = true;
- enableVFSSFTP = true;
- };
-}
-
-
- All Kodi config flags have been removed,
- and as a result the above configuration should now be written
- as:
-
-
-{
- environment.systemPackages = [
- (pkgs.kodi.withPackages (p: with p; [
- inputstream-adaptive
- vfs-sftp
- ]))
- ];
-}
-
-
-
-
- environment.defaultPackages now includes
- the nano package. If pkgs.nano is not added to the list, make
- sure another editor is installed and the
- EDITOR environment variable is set to it.
- Environment variables can be set using
- environment.variables.
-
-
-
-
- services.minio.dataDir changed type to a
- list of paths, required for specifiyng multiple data
- directories for using with erasure coding. Currently, the
- service doesn’t enforce nor checks the correct number of paths
- to correspond to minio requirements.
-
-
-
-
- All CUDA toolkit versions prior to CUDA 10 have been removed.
-
-
-
-
- The kbdKeymaps package was removed since dvp and neo are now
- included in kbd. If you want to use the Programmer Dvorak
- Keyboard Layout, you have to use
- dvorak-programmer in
- console.keyMap now instead of
- dvp. In
- services.xserver.xkbVariant it’s still
- dvp.
-
-
-
-
- The babeld service is now being run as an unprivileged user.
- To achieve that the module configures
- skip-kernel-setup true and takes care of
- setting forwarding and rp_filter sysctls by itself as well as
- for each interface in
- services.babeld.interfaces.
-
-
-
-
- The services.zigbee2mqtt.config option has
- been renamed to
- services.zigbee2mqtt.settings and now
- follows
- RFC
- 0042.
-
-
-
-
- The yadm dotfile manager has been updated from 2.x to 3.x, which
- has new (XDG) default locations for some data/state files. Most
- yadm commands will fail and print a legacy path warning (which
- describes how to upgrade/migrate your repository). If you have
- scripts, daemons, scheduled jobs, shell profiles, etc. that invoke
- yadm, expect them to fail or misbehave until you perform this
- migration and prepare accordingly.
-
-
-
-
- Instead of determining
- services.radicale.package automatically
- based on system.stateVersion, the latest
- version is always used because old versions are not officially
- supported.
-
-
- Furthermore, Radicale’s systemd unit was hardened which might
- break some deployments. In particular, a non-default
- filesystem_folder has to be added to
- systemd.services.radicale.serviceConfig.ReadWritePaths
- if the deprecated services.radicale.config
- is used.
-
-
-
-
- In the security.acme module, use of
- --reuse-key parameter for Lego has been
- removed. It was introduced for HKPK, but this security feature
- is now deprecated. It is a better security practice to rotate
- key pairs instead of always keeping the same. If you need to
- keep this parameter, you can add it back using
- extraLegoRenewFlags as an option for the
- appropriate certificate.
-
-
-
-
-
- Other Notable Changes
-
-
-
- stdenv.lib has been deprecated and will
- break eval in 21.11. Please use pkgs.lib
- instead. See
- #108938
- for details.
-
-
-
-
- GNURadio
- has a pkgs attribute set, and there’s a
- gnuradio.callPackage function that extends
- pkgs with a
- mkDerivation, and a
- mkDerivationWith, like Qt5. Now all
- gnuradio.pkgs are defined with
- gnuradio.callPackage and some packages that
- depend on gnuradio are defined with this as well.
-
-
-
-
- Privoxy has
- been updated to version 3.0.32 (See
- announcement).
- Compared to the previous release, Privoxy has gained support
- for HTTPS inspection (still experimental), Brotli
- decompression, several new filters and lots of bug fixes,
- including security ones. In addition, the package is now built
- with compression and external filters support, which were
- previously disabled.
-
-
- Regarding the NixOS module, new options for HTTPS inspection
- have been added and
- services.privoxy.extraConfig has been
- replaced by the new
- services.privoxy.settings
- (See
- RFC
- 0042 for the motivation).
-
-
-
-
- Kodi has been
- updated to version 19.1 Matrix. See the
- announcement
- for further details.
-
-
-
-
- The services.packagekit.backend option has
- been removed as it only supported a single setting which would
- always be the default. Instead new
- RFC
- 0042 compliant
- services.packagekit.settings
- and
- services.packagekit.vendorSettings
- options have been introduced.
-
-
-
-
- Nginx has been
- updated to stable version 1.20.0. Now nginx uses the zlib-ng
- library by default.
-
-
-
-
- KDE Gear (formerly KDE Applications) is upgraded to 21.04, see
- its
- release
- notes for details.
-
-
- The kdeApplications package set is now
- kdeGear, in keeping with the new name. The
- old name remains for compatibility, but it is deprecated.
-
-
-
-
- Libreswan has
- been updated to version 4.4. The package now includes example
- configurations and manual pages by default. The NixOS module
- has been changed to use the upstream systemd units and write
- the configuration in the /etc/ipsec.d/
- directory. In addition, two new options have been added to
- specify connection policies
- (services.libreswan.policies)
- and disable send/receive redirects
- (services.libreswan.disableRedirects).
-
-
-
-
- The Mailman NixOS module (services.mailman)
- has a new option
- services.mailman.enablePostfix,
- defaulting to true, that controls integration with Postfix.
-
-
- If this option is disabled, default MTA config becomes not set
- and you should set the options in
- services.mailman.settings.mta according to
- the desired configuration as described in
- Mailman
- documentation.
-
-
-
-
- The default-version of nextcloud is
- nextcloud21. Please note that it’s not
- possible to upgrade nextcloud across
- multiple major versions! This means that it’s e.g. not
- possible to upgrade from nextcloud18 to nextcloud20 in a
- single deploy and most 20.09 users will
- have to upgrade to nextcloud20 first.
-
-
- The package can be manually upgraded by setting
- services.nextcloud.package
- to nextcloud21.
-
-
-
-
- The setting
- services.redis.bind
- defaults to 127.0.0.1 now, making Redis
- listen on the loopback interface only, and not all public
- network interfaces.
-
-
-
-
- NixOS now emits a deprecation warning if systemd’s
- StartLimitInterval setting is used in a
- serviceConfig section instead of in a
- unitConfig; that setting is deprecated and
- now undocumented for the service section by systemd upstream,
- but still effective and somewhat buggy there, which can be
- confusing. See
- #45785
- for details.
-
-
- All services should use
- systemd.services.name.startLimitIntervalSec
- or StartLimitIntervalSec in
- systemd.services.name.unitConfig
- instead.
-
-
-
-
- The mediatomb service declares new options.
- It also adapts existing options so the configuration
- generation is now lazy. The existing option
- customCfg (defaults to false), when
- enabled, stops the service configuration generation
- completely. It then expects the users to provide their own
- correct configuration at the right location (whereas the
- configuration was generated and not used at all before). The
- new option transcodingOption (defaults to
- no) allows a generated configuration. It makes the mediatomb
- service pulls the necessary runtime dependencies in the nix
- store (whereas it was generated with hardcoded values before).
- The new option mediaDirectories allows the
- users to declare autoscan media directories from their nixos
- configuration:
-
-
-{
- services.mediatomb.mediaDirectories = [
- { path = "/var/lib/mediatomb/pictures"; recursive = false; hidden-files = false; }
- { path = "/var/lib/mediatomb/audio"; recursive = true; hidden-files = false; }
- ];
-}
-
-
-
-
- The Unbound DNS resolver service
- (services.unbound) has been refactored to
- allow reloading, control sockets and to fix startup ordering
- issues.
-
-
- It is now possible to enable a local UNIX control socket for
- unbound by setting the
- services.unbound.localControlSocketPath
- option.
-
-
- Previously we just applied a very minimal set of restrictions
- and trusted unbound to properly drop root privs and
- capabilities.
-
-
- As of this we are (for the most part) just using the upstream
- example unit file for unbound. The main difference is that we
- start unbound as unbound user with the
- required capabilities instead of letting unbound do the chroot
- & uid/gid changes.
-
-
- The upstream unit configuration this is based on is a lot
- stricter with all kinds of permissions then our previous
- variant. It also came with the default of having the
- Type set to notify,
- therefore we are now also using the
- unbound-with-systemd package here. Unbound
- will start up, read the configuration files and start
- listening on the configured ports before systemd will declare
- the unit active (running). This will likely
- help with startup order and the occasional race condition
- during system activation where the DNS service is started but
- not yet ready to answer queries. Services depending on
- nss-lookup.target or
- unbound.service are now be able to use
- unbound when those targets have been reached.
-
-
- Additionally to the much stricter runtime environment the
- /dev/urandom mount lines we previously had
- in the code (that randomly failed during the stop-phase) have
- been removed as systemd will take care of those for us.
-
-
- The preStart script is now only required if
- we enabled the trust anchor updates (which are still enabled
- by default).
-
-
- Another benefit of the refactoring is that we can now issue
- reloads via either pkill -HUP unbound and
- systemctl reload unbound to reload the
- running configuration without taking the daemon offline. A
- prerequisite of this was that unbound configuration is
- available on a well known path on the file system. We are
- using the path /etc/unbound/unbound.conf as
- that is the default in the CLI tooling which in turn enables
- us to use unbound-control without passing a
- custom configuration location.
-
-
- The module has also been reworked to be
- RFC
- 0042 compliant. As such,
- sevices.unbound.extraConfig has been
- removed and replaced by
- services.unbound.settings.
- services.unbound.interfaces has been
- renamed to
- services.unbound.settings.server.interface.
-
-
- services.unbound.forwardAddresses and
- services.unbound.allowedAccess have also
- been changed to use the new settings interface. You can follow
- the instructions when executing
- nixos-rebuild to upgrade your configuration
- to use the new interface.
-
-
-
-
- The services.dnscrypt-proxy2 module now
- takes the upstream’s example configuration and updates it with
- the user’s settings. An option has been added to restore the
- old behaviour if you prefer to declare the configuration from
- scratch.
-
-
-
-
- NixOS now defaults to the unified cgroup hierarchy
- (cgroupsv2). See the
- Fedora
- Article for 31 for details on why this is desirable,
- and how it impacts containers.
-
-
- If you want to run containers with a runtime that does not yet
- support cgroupsv2, you can switch back to the old behaviour by
- setting
- systemd.enableUnifiedCgroupHierarchy
- = false; and rebooting.
-
-
-
-
- PulseAudio was upgraded to 14.0, with changes to the handling
- of default sinks. See its
- release
- notes.
-
-
-
-
- GNOME users may wish to delete their
- ~/.config/pulse due to the changes to
- stream routing logic. See
- PulseAudio
- bug 832 for more information.
-
-
-
-
- The zookeeper package does not provide
- zooInspector.sh anymore, as that
- contrib has been dropped from upstream
- releases.
-
-
-
-
- In the ACME module, the data used to build the hash for the
- account directory has changed to accommodate new features to
- reduce account rate limit issues. This will trigger new
- account creation on the first rebuild following this update.
- No issues are expected to arise from this, thanks to the new
- account creation handling.
-
-
-
-
- users.users.name.createHome
- now always ensures home directory permissions to be
- 0700. Permissions had previously been
- ignored for already existing home directories, possibly
- leaving them readable by others. The option’s description was
- incorrect regarding ownership management and has been
- simplified greatly.
-
-
-
-
- When defining a new user, one of
- users.users.name.isNormalUser
- and
- users.users.name.isSystemUser
- is now required. This is to prevent accidentally giving a UID
- above 1000 to system users, which could have unexpected
- consequences, like running user activation scripts for system
- users. Note that users defined with an explicit UID below 500
- are exempted from this check, as
- users.users.name.isSystemUser
- has no effect for those.
-
-
-
-
- The security.apparmor module, for the
- AppArmor
- Mandatory Access Control system, has been substantialy
- improved along with related tools, so that module maintainers
- can now more easily write AppArmor profiles for NixOS. The
- most notable change on the user-side is the new option
- security.apparmor.policies,
- replacing the previous profiles option to
- provide a way to disable a profile and to select whether to
- confine in enforce mode (default) or in complain mode (see
- journalctl -b --grep apparmor).
- Security-minded users may also want to enable
- security.apparmor.killUnconfinedConfinables,
- at the cost of having some of their processes killed when
- updating to a NixOS version introducing new AppArmor profiles.
-
-
-
-
- The GNOME desktop manager once again installs gnome.epiphany
- by default.
-
-
-
-
- NixOS now generates empty /etc/netgroup.
- /etc/netgroup defines network-wide groups
- and may affect to setups using NIS.
-
-
-
-
- Platforms, like stdenv.hostPlatform, no
- longer have a platform attribute. It has
- been (mostly) flattened away:
-
-
-
-
- platform.gcc is now
- gcc
-
-
-
-
- platform.kernel* is now
- linux-kernel.*
-
-
-
-
- Additionally, platform.kernelArch moved to
- the top level as linuxArch to match the
- other *Arch variables.
-
-
- The platform grouping of these things never
- meant anything, and was just a historial/implementation
- artifact that was overdue removal.
-
-
-
-
- services.restic now uses a dedicated cache
- directory for every backup defined in
- services.restic.backups. The old global
- cache directory, /root/.cache/restic, is
- now unused and can be removed to free up disk space.
-
-
-
-
- isync: The isync
- compatibility wrapper was removed and the Master/Slave
- terminology has been deprecated and should be replaced with
- Far/Near in the configuration file.
-
-
-
-
- The nix-gc service now accepts randomizedDelaySec (default: 0)
- and persistent (default: true) parameters. By default nix-gc
- will now run immediately if it would have been triggered at
- least once during the time when the timer was inactive.
-
-
-
-
- The rustPlatform.buildRustPackage function
- is split into several hooks: cargoSetupHook to set up
- vendoring for Cargo-based projects, cargoBuildHook to build a
- project using Cargo, cargoInstallHook to install a project
- using Cargo, and cargoCheckHook to run tests in Cargo-based
- projects. With this change, mixed-language projects can use
- the relevant hooks within builders other than
- buildRustPackage. However, these changes
- also required several API changes to
- buildRustPackage itself:
-
-
-
-
- The target argument was removed.
- Instead, buildRustPackage will always
- use the same target as the C/C++ compiler that is used.
-
-
-
-
- The cargoParallelTestThreads argument
- was removed. Parallel tests are now disabled through
- dontUseCargoParallelTests.
-
-
-
-
-
-
- The rustPlatform.maturinBuildHook hook was
- added. This hook can be used with
- buildPythonPackage to build Python packages
- that are written in Rust and use Maturin as their build tool.
-
-
-
-
- Kubernetes has
- deprecated
- docker as container runtime. As a consequence, the
- Kubernetes module now has support for configuration of custom
- remote container runtimes and enables containerd by default.
- Note that containerd is more strict regarding container image
- OCI-compliance. As an example, images with CMD or ENTRYPOINT
- defined as strings (not lists) will fail on containerd, while
- working fine on docker. Please test your setup and container
- images with containerd prior to upgrading.
-
-
-
-
- The GitLab module now has support for automatic backups. A
- schedule can be set with the
- services.gitlab.backup.startAt
- option.
-
-
-
-
- Prior to this release, systemd would also read system units
- from an undocumented
- /etc/systemd-mutable/system path. This path
- has been dropped from the defaults. That path (or others) can
- be re-enabled by adding it to the
- boot.extraSystemdUnitPaths
- list.
-
-
-
-
- PostgreSQL 9.5 is scheduled EOL during the 21.05 life cycle
- and has been removed.
-
-
-
-
- Xfce4 relies
- on GIO/GVfs for userspace virtual filesystem access in
- applications like
- thunar
- and
- gigolo.
- For that to work, the gvfs nixos service is enabled by
- default, and it can be configured with the specific package
- that provides GVfs. Until now Xfce4 was setting it to use a
- lighter version of GVfs (without support for samba). To avoid
- conflicts with other desktop environments this setting has
- been dropped. Users that still want it should add the
- following to their system configuration:
-
-
-{
- services.gvfs.package = pkgs.gvfs.override { samba = null; };
-}
-
-
-
-
- The newly enabled systemd-pstore.service
- now automatically evacuates crashdumps and panic logs from the
- persistent storage to
- /var/lib/systemd/pstore. This prevents
- NVRAM from filling up, which ensures the latest diagnostic
- data is always stored and alleviates problems with writing new
- boot configurations.
-
-
-
-
- Nixpkgs now contains
- automatically
- packaged GNOME Shell extensions from the
- GNOME
- Extensions portal. You can find them, filed by their
- UUID, under gnome38Extensions attribute for
- GNOME 3.38 and under gnome40Extensions for
- GNOME 40. Finally, the gnomeExtensions
- attribute contains extensions for the latest GNOME Shell
- version in Nixpkgs, listed under a more human-friendly name.
- The unqualified attribute scope also contains manually
- packaged extensions. Note that the automatically packaged
- extensions are provided for convenience and are not checked or
- guaranteed to work.
-
-
-
-
- Erlang/OTP versions older than R21 got dropped. We also
- dropped the cuter package, as it was purely an example of how
- to build a package. We also dropped lfe_1_2
- as it could not build with R21+. Moving forward, we expect to
- only support 3 yearly releases of OTP.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-2111.section.xml b/nixos/doc/manual/from_md/release-notes/rl-2111.section.xml
deleted file mode 100644
index 48a717916535..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-2111.section.xml
+++ /dev/null
@@ -1,2122 +0,0 @@
-
- Release 21.11 (“Porcupine”, 2021/11/30)
-
-
-
- Support is planned until the end of June 2022, handing over to
- 22.05.
-
-
-
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- Nix has been updated to version 2.4, reference its
- release
- notes for more information on what has changed. The
- previous version of Nix, 2.3.16, remains available for the
- time being in the nix_2_3 package.
-
-
-
-
- iptables is now using
- nf_tables under the hood, by using
- iptables-nft, similar to
- Debian
- and
- Fedora.
- This means, ip[6]tables,
- arptables and ebtables
- commands will actually show rules from some specific tables in
- the nf_tables kernel subsystem. In case
- you’re migrating from an older release without rebooting,
- there might be cases where you end up with iptable rules
- configured both in the legacy iptables
- kernel backend, as well as in the nf_tables
- backend. This can lead to confusing firewall behaviour. An
- iptables-save after switching will complain
- about iptables-legacy tables present. It’s
- probably best to reboot after the upgrade, or manually
- removing all legacy iptables rules (via the
- iptables-legacy package).
-
-
-
-
- systemd got an nftables backend, and
- configures (networkd) rules in their own
- io.systemd.* tables. Check
- nft list ruleset to see these rules, not
- iptables-save (which only shows
- iptables-created rules.
-
-
-
-
- PHP now defaults to PHP 8.0, updated from 7.4.
-
-
-
-
- kops now defaults to 1.21.1, which uses containerd as the
- default runtime.
-
-
-
-
- python3 now defaults to Python 3.9, updated
- from Python 3.8.
-
-
-
-
- PostgreSQL now defaults to major version 13.
-
-
-
-
- spark now defaults to spark 3, updated from 2. A
- migration
- guide is available.
-
-
-
-
- Improvements have been made to the Hadoop module and package:
-
-
-
-
- HDFS and YARN now support production-ready highly
- available deployments with automatic failover.
-
-
-
-
- Hadoop now defaults to Hadoop 3, updated from 2.
-
-
-
-
- JournalNode, ZKFS and HTTPFS services have been added.
-
-
-
-
-
-
- Activation scripts can now, optionally, be run during a
- nixos-rebuild dry-activate and can detect
- the dry activation by reading
- $NIXOS_ACTION. This allows activation
- scripts to output what they would change if the activation was
- really run. The users/modules activation script supports this
- and outputs some of is actions.
-
-
-
-
- KDE Plasma now finally works on Wayland.
-
-
-
-
- bash now defaults to major version 5.
-
-
-
-
- Systemd was updated to version 249 (from 247).
-
-
-
-
- Pantheon desktop has been updated to version 6. Due to changes
- of screen locker, if locking doesn’t work for you, please try
- gsettings set org.gnome.desktop.lockdown disable-lock-screen false.
-
-
-
-
- kubernetes-helm now defaults to 3.7.0,
- which introduced some breaking changes to the experimental OCI
- manifest format. See
- HIP
- 6 for more details. helmfile also
- defaults to 0.141.0, which is the minimum compatible version.
-
-
-
-
- GNOME has been upgraded to 41. Please take a look at their
- Release
- Notes for details.
-
-
-
-
- LXD support was greatly improved:
-
-
-
-
- building LXD images from configurations is now directly
- possible with just nixpkgs
-
-
-
-
- hydra is now building nixOS LXD images that can be used
- standalone with full nixos-rebuild support
-
-
-
-
-
-
- OpenSSH was updated to version 8.8p1
-
-
-
-
- This breaks connections to old SSH daemons as ssh-rsa host
- keys and ssh-rsa public keys that were signed with SHA-1
- are disabled by default now
-
-
-
-
- These can be re-enabled, see the
- OpenSSH
- changelog for details
-
-
-
-
-
-
- ORY Kratos was updated to version 0.8.0-alpha.3
-
-
-
-
- This release requires you to run SQL migrations. Please,
- as always, create a backup of your database first!
-
-
-
-
- The SDKs are now generated with tag v0alpha2 to reflect
- that some signatures have changed in a breaking fashion.
- Please update your imports from v0alpha1 to v0alpha2.
-
-
-
-
- The SMTPS scheme used in courier config URL with
- cleartext/StartTLS/TLS SMTP connection types is now only
- supporting implicit TLS. For StartTLS and cleartext SMTP,
- please use the SMTP scheme instead.
-
-
-
-
- for more details, see
- Release
- Notes.
-
-
-
-
-
-
-
- New Services
-
-
-
- btrbk,
- a backup tool for btrfs subvolumes, taking advantage of btrfs
- specific capabilities to create atomic snapshots and transfer
- them incrementally to your backup locations. Available as
- services.btrbk.
-
-
-
-
- clipcat,
- an X11 clipboard manager written in Rust. Available at
- services.clipcat.
-
-
-
-
- dex,
- an OpenID Connect (OIDC) identity and OAuth 2.0 provider.
- Available at
- services.dex.
-
-
-
-
- geoipupdate,
- a GeoIP database updater from MaxMind. Available as
- services.geoipupdate.
-
-
-
-
- Jibri,
- a service for recording or streaming a Jitsi Meet conference.
- Available as
- services.jibri.
-
-
-
-
- Kea, ISCs
- 2nd generation DHCP and DDNS server suite. Available at
- services.kea.
-
-
-
-
- owncast,
- self-hosted video live streaming solution. Available at
- services.owncast.
-
-
-
-
- PeerTube,
- developed by Framasoft, is the free and decentralized
- alternative to video platforms. Available at
- services.peertube.
-
-
-
-
- sourcehut, a
- collection of tools useful for software development. Available
- as
- services.sourcehut.
-
-
-
-
- ucarp,
- an userspace implementation of the Common Address Redundancy
- Protocol (CARP). Available as
- networking.ucarp.
-
-
-
-
- Users of flashrom should migrate to
- programs.flashrom.enable
- and add themselves to the flashrom group to
- be able to access programmers supported by flashrom.
-
-
-
-
- vikunja, a to-do
- list app. Available as
- services.vikunja.
-
-
-
-
- opensnitch,
- an application firewall. Available as
- services.opensnitch.
-
-
-
-
- snapraid, a
- backup program for disk arrays. Available as
- snapraid.
-
-
-
-
- Hockeypuck,
- a OpenPGP Key Server. Available as
- services.hockeypuck.
-
-
-
-
- buildkite-agent-metrics,
- a command-line tool for collecting Buildkite agent metrics,
- now has a Prometheus exporter available as
- services.prometheus.exporters.buildkite-agent.
-
-
-
-
- influxdb-exporter
- a Prometheus exporter that exports metrics received on an
- InfluxDB compatible endpoint is now available as
- services.prometheus.exporters.influxdb.
-
-
-
-
- mx-puppet-discord,
- a discord puppeting bridge for matrix. Available as
- services.mx-puppet-discord.
-
-
-
-
- MeshCentral,
- a remote administration service (TeamViewer but
- self-hosted and with more features) is now available
- with a package and a module:
- services.meshcentral.enable
-
-
-
-
- moonraker,
- an API web server for Klipper. Available as
- moonraker.
-
-
-
-
- influxdb2,
- a Scalable datastore for metrics, events, and real-time
- analytics. Available as
- services.influxdb2.
-
-
-
-
- isso, a
- commenting server similar to Disqus. Available as
- isso
-
-
-
-
- navidrome,
- a personal music streaming server with subsonic-compatible
- api. Available as
- navidrome.
-
-
-
-
- fluidd, a
- Klipper web interface for managing 3d printers using
- moonraker. Available as
- fluidd.
-
-
-
-
- sx,
- a simple alternative to both xinit and startx for starting a
- Xorg server. Available as
- services.xserver.displayManager.sx
-
-
-
-
- postfixadmin,
- a web based virtual user administration interface for Postfix
- mail servers. Available as
- postfixadmin.
-
-
-
-
- prowlarr,
- an indexer manager/proxy built on the popular arr .net/reactjs
- base stack
- services.prowlarr.
-
-
-
-
- soju, a
- user-friendly IRC bouncer. Available as
- services.soju.
-
-
-
-
- nats, a high
- performance cloud and edge messaging system. Available as
- services.nats.
-
-
-
-
- git, a
- distributed version control system. Available as
- programs.git.
-
-
-
-
- parsedmarc,
- a service which parses incoming
- DMARC reports and
- stores or sends them to a downstream service for further
- analysis. Documented in
- its manual
- entry.
-
-
-
-
- spark, a
- unified analytics engine for large-scale data processing.
-
-
-
-
- touchegg,
- a multi-touch gesture recognizer. Available as
- services.touchegg.
-
-
-
-
- pantheon-tweaks,
- an unofficial system settings panel for Pantheon. Available as
- programs.pantheon-tweaks.
-
-
-
-
- joycond,
- a service that uses hid-nintendo to provide
- nintendo joycond pairing and better nintendo switch pro
- controller support.
-
-
-
-
- multipath,
- the device mapper multipath (DM-MP) daemon. Available as
- services.multipath.
-
-
-
-
- seafile,
- an open source file syncing & sharing software. Available
- as
- services.seafile.
-
-
-
-
- rasdaemon,
- a hardware error logging daemon. Available as
- hardware.rasdaemon.
-
-
-
-
- code-server-module now available
-
-
-
-
- xmrig,
- a high performance, open source, cross platform RandomX,
- KawPow, CryptoNight and AstroBWT unified CPU/GPU miner and
- RandomX benchmark.
-
-
-
-
- Auto nice daemons
- ananicy
- and
- ananicy-cpp.
- Available as
- services.ananicy.
-
-
-
-
- smartctl_exporter,
- a Prometheus exporter for
- S.M.A.R.T.
- data. Available as
- services.prometheus.exporters.smartctl.
-
-
-
-
- twingate,
- a high performance, easy to use zero trust solution that
- enables access to private resources from any device with
- better security than a VPN.
-
-
-
-
-
- Backward Incompatibilities
-
-
-
- The NixOS VM test framework,
- pkgs.nixosTest/make-test-python.nix
- (pkgs.testers.nixosTest since 22.05), now
- requires detaching commands such as
- succeed("foo &") and
- succeed("foo | xclip -i") to
- close stdout. This can be done with a redirect such as
- succeed("foo >&2 &").
- This breaking change was necessitated by a race condition
- causing tests to fail or hang. It applies to all methods that
- invoke commands on the nodes, including
- execute, succeed,
- fail,
- wait_until_succeeds,
- wait_until_fails.
-
-
-
-
- The services.wakeonlan option was removed,
- and replaced with
- networking.interfaces.<name>.wakeOnLan.
-
-
-
-
- The security.wrappers option now requires
- to always specify an owner, group and whether the
- setuid/setgid bit should be set. This is motivated by the fact
- that before NixOS 21.11, specifying either setuid or setgid
- but not owner/group resulted in wrappers owned by
- nobody/nogroup, which is unsafe.
-
-
-
-
- Since iptables now uses
- nf_tables backend and
- ipset doesn’t support it, some applications
- (ferm, shorewall, firehol) may have limited functionality.
-
-
-
-
- The paperless module and package have been
- removed. All users should migrate to the successor
- paperless-ng instead. The Paperless project
- has
- been archived and advises all users to use
- paperless-ng instead.
-
-
- Users can use the services.paperless-ng
- module as a replacement while noting the following
- incompatibilities:
-
-
-
-
- services.paperless.ocrLanguages has no
- replacement. Users should migrate to
- services.paperless-ng.extraConfig
- instead:
-
-
-
-
-{
- services.paperless-ng.extraConfig = {
- # Provide languages as ISO 639-2 codes
- # separated by a plus (+) sign.
- # https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes
- PAPERLESS_OCR_LANGUAGE = "deu+eng+jpn"; # German & English & Japanse
- };
-}
-
-
-
-
- If you previously specified
- PAPERLESS_CONSUME_MAIL_* settings in
- services.paperless.extraConfig you
- should remove those options now. You now
- must define those settings in the
- admin interface of paperless-ng.
-
-
-
-
- Option services.paperless.manage no
- longer exists. Use the script at
- ${services.paperless-ng.dataDir}/paperless-ng-manage
- instead. Note that this script only exists after the
- paperless-ng service has been started
- at least once.
-
-
-
-
- After switching to the new system configuration you should
- run the Django management command to reindex your
- documents and optionally create a user, if you don’t have
- one already.
-
-
- To do so, enter the data directory (the value of
- services.paperless-ng.dataDir,
- /var/lib/paperless by default), switch
- to the paperless user and execute the management command
- like below:
-
-
-$ cd /var/lib/paperless
-$ su paperless -s /bin/sh
-$ ./paperless-ng-manage document_index reindex
-# if not already done create a user account, paperless-ng requires a login
-$ ./paperless-ng-manage createsuperuser
-Username (leave blank to use 'paperless'): my-user-name
-Email address: me@example.com
-Password: **********
-Password (again): **********
-Superuser created successfully.
-
-
-
-
-
-
- The staticjinja package has been upgraded
- from 1.0.4 to 4.1.1
-
-
-
-
- Firefox v91 does not support addons with invalid signature
- anymore. Firefox ESR needs to be used for nix addon support.
-
-
-
-
- The erigon ethereum node has moved to a new
- database format in 2021-05-04, and requires
- a full resync
-
-
-
-
- The erigon ethereum node has moved its
- database location in 2021-08-03, users
- upgrading must manually move their chaindata (see
- release
- notes).
-
-
-
-
- users.users.<name>.group
- no longer defaults to nogroup, which was
- insecure. Out-of-tree modules are likely to require
- adaptation: instead of
-
-
-{
- users.users.foo = {
- isSystemUser = true;
- };
-}
-
-
- also create a group for your user:
-
-
-{
- users.users.foo = {
- isSystemUser = true;
- group = "foo";
- };
- users.groups.foo = {};
-}
-
-
-
-
- services.geoip-updater was broken and has
- been replaced by
- services.geoipupdate.
-
-
-
-
- ihatemoney has been updated to version
- 5.1.1
- (release
- notes). If you serve ihatemoney by HTTP rather than
- HTTPS, you must set
- services.ihatemoney.secureCookie
- to false.
-
-
-
-
- PHP 7.3 is no longer supported due to upstream not supporting
- this version for the entire lifecycle of the 21.11 release.
-
-
-
-
- Those making use of buildBazelPackage will
- need to regenerate the fetch hashes (preferred), or set
- fetchConfigured = false;.
-
-
-
-
- consul was upgraded to a new major release
- with breaking changes, see
- upstream
- changelog.
-
-
-
-
- fsharp41 has been removed in preference to use the latest
- dotnet-sdk
-
-
-
-
- The following F#-related packages have been removed for being
- unmaintaned. Please use fetchNuGet for
- specific packages.
-
-
-
-
- ExtCore
-
-
-
-
- Fake
-
-
-
-
- Fantomas
-
-
-
-
- FsCheck
-
-
-
-
- FsCheck262
-
-
-
-
- FsCheckNunit
-
-
-
-
- FSharpAutoComplete
-
-
-
-
- FSharpCompilerCodeDom
-
-
-
-
- FSharpCompilerService
-
-
-
-
- FSharpCompilerTools
-
-
-
-
- FSharpCore302
-
-
-
-
- FSharpCore3125
-
-
-
-
- FSharpCore4001
-
-
-
-
- FSharpCore4117
-
-
-
-
- FSharpData
-
-
-
-
- FSharpData225
-
-
-
-
- FSharpDataSQLProvider
-
-
-
-
- FSharpFormatting
-
-
-
-
- FsLexYacc
-
-
-
-
- FsLexYacc706
-
-
-
-
- FsLexYaccRuntime
-
-
-
-
- FsPickler
-
-
-
-
- FsUnit
-
-
-
-
- Projekt
-
-
-
-
- Suave
-
-
-
-
- UnionArgParser
-
-
-
-
- ExcelDnaRegistration
-
-
-
-
- MathNetNumerics
-
-
-
-
-
-
- programs.x2goserver is now
- services.x2goserver
-
-
-
-
- The following dotnet-related packages have been removed for
- being unmaintaned. Please use fetchNuGet
- for specific packages.
-
-
-
-
- Autofac
-
-
-
-
- SystemValueTuple
-
-
-
-
- MicrosoftDiaSymReader
-
-
-
-
- MicrosoftDiaSymReaderPortablePdb
-
-
-
-
- SystemCollectionsImmutable
-
-
-
-
- SystemCollectionsImmutable131
-
-
-
-
- SystemReflectionMetadata
-
-
-
-
- NUnit350
-
-
-
-
- Deedle
-
-
-
-
- ExcelDna
-
-
-
-
- GitVersionTree
-
-
-
-
- NDeskOptions
-
-
-
-
-
-
-
-
- The antlr package now defaults to the 4.x
- release instead of the old 2.7.7 version.
-
-
-
-
- The pulseeffects package updated to
- version
- 4.x and renamed to easyeffects.
-
-
-
-
- The libwnck package now defaults to the 3.x
- release instead of the old 2.31.0 version.
-
-
-
-
- The bitwarden_rs packages and modules were
- renamed to vaultwarden
- following
- upstream. More specifically,
-
-
-
-
- pkgs.bitwarden_rs,
- pkgs.bitwarden_rs-sqlite,
- pkgs.bitwarden_rs-mysql and
- pkgs.bitwarden_rs-postgresql were
- renamed to pkgs.vaultwarden,
- pkgs.vaultwarden-sqlite,
- pkgs.vaultwarden-mysql and
- pkgs.vaultwarden-postgresql,
- respectively.
-
-
-
-
- Old names are preserved as aliases for backwards
- compatibility, but may be removed in the future.
-
-
-
-
- The bitwarden_rs executable was
- also renamed to vaultwarden in all
- packages.
-
-
-
-
-
-
- pkgs.bitwarden_rs-vault was renamed to
- pkgs.vaultwarden-vault.
-
-
-
-
- pkgs.bitwarden_rs-vault is
- preserved as an alias for backwards compatibility, but
- may be removed in the future.
-
-
-
-
- The static files were moved from
- /usr/share/bitwarden_rs to
- /usr/share/vaultwarden.
-
-
-
-
-
-
- The services.bitwarden_rs config module
- was renamed to services.vaultwarden.
-
-
-
-
- services.bitwarden_rs is preserved
- as an alias for backwards compatibility, but may be
- removed in the future.
-
-
-
-
-
-
- systemd.services.bitwarden_rs,
- systemd.services.backup-bitwarden_rs
- and systemd.timers.backup-bitwarden_rs
- were renamed to
- systemd.services.vaultwarden,
- systemd.services.backup-vaultwarden and
- systemd.timers.backup-vaultwarden,
- respectively.
-
-
-
-
- Old names are preserved as aliases for backwards
- compatibility, but may be removed in the future.
-
-
-
-
-
-
- users.users.bitwarden_rs and
- users.groups.bitwarden_rs were renamed
- to users.users.vaultwarden and
- users.groups.vaultwarden, respectively.
-
-
-
-
- The data directory remains located at
- /var/lib/bitwarden_rs, for backwards
- compatibility.
-
-
-
-
-
-
-
-
- yggdrasil was upgraded to a new major
- release with breaking changes, see
- upstream
- changelog.
-
-
-
-
- icingaweb2 was upgraded to a new release
- which requires a manual database upgrade, see
- upstream
- changelog.
-
-
-
-
- The isabelle package has been upgraded from
- 2020 to 2021
-
-
-
-
- the mingw-64 package has been upgraded from
- 6.0.0 to 9.0.0
-
-
-
-
- tt-rss was upgraded to the commit on
- 2021-06-21, which has breaking changes. If you use
- services.tt-rss.extraConfig you should
- migrate to the putenv-style configuration.
- See
- this
- Discourse post in the tt-rss forums for more details.
-
-
-
-
- The following Visual Studio Code extensions were renamed to
- keep the naming convention uniform.
-
-
-
-
- bbenoist.Nix ->
- bbenoist.nix
-
-
-
-
- CoenraadS.bracket-pair-colorizer ->
- coenraads.bracket-pair-colorizer
-
-
-
-
- golang.Go ->
- golang.go
-
-
-
-
-
-
- services.uptimed now uses
- /var/lib/uptimed as its stateDirectory
- instead of /var/spool/uptimed. Make sure to
- move all files to the new directory.
-
-
-
-
- Deprecated package aliases in emacs.pkgs.*
- have been removed. These aliases were remnants of the old
- Emacs package infrastructure. We now use exact upstream names
- wherever possible.
-
-
-
-
- programs.neovim.runtime switched to a
- linkFarm internally, making it impossible
- to use wildcards in the source argument.
-
-
-
-
- The openrazer and
- openrazer-daemon packages as well as the
- hardware.openrazer module now require users
- to be members of the openrazer group
- instead of plugdev. With this change, users
- no longer need be granted the entire set of
- plugdev group permissions, which can
- include permissions other than those required by
- openrazer. This is desirable from a
- security point of view. The setting
- harware.openrazer.users
- can be used to add users to the openrazer
- group.
-
-
-
-
- The fontconfig service’s dpi option has been removed.
- Fontconfig should use Xft settings by default so there’s no
- need to override one value in multiple places. The user can
- set DPI via ~/.Xresources properly, or at the system level per
- monitor, or as a last resort at the system level with
- services.xserver.dpi.
-
-
-
-
- The yambar package has been split into
- yambar and
- yambar-wayland, corresponding to the xorg
- and wayland backend respectively. Please switch to
- yambar-wayland if you are on wayland.
-
-
-
-
- The services.minio module gained an
- additional option consoleAddress, that
- configures the address and port the web UI is listening, it
- defaults to :9001. To be able to access the
- web UI this port needs to be opened in the firewall.
-
-
-
-
- The varnish package was upgraded from 6.3.x
- to 7.x. varnish60 for the last LTS release
- is also still available.
-
-
-
-
- The kubernetes package was upgraded to
- 1.22. The kubernetes.apiserver.kubeletHttps
- option was removed and HTTPS is always used.
-
-
-
-
- The attribute linuxPackages_latest_hardened
- was dropped because the hardened patches lag behind the
- upstream kernel which made version bumps harder. If you want
- to use a hardened kernel, please pin it explicitly with a
- versioned attribute such as
- linuxPackages_5_10_hardened.
-
-
-
-
- The nomad package now defaults to a 1.1.x
- release instead of 1.0.x
-
-
-
-
- If exfat is included in
- boot.supportedFilesystems and when using
- kernel 5.7 or later, the exfatprogs
- user-space utilities are used instead of
- exfat.
-
-
-
-
- The todoman package was upgraded from 3.9.0
- to 4.0.0. This introduces breaking changes in the
- configuration
- file format.
-
-
-
-
- The datadog-agent,
- datadog-integrations-core and
- datadog-process-agent packages were
- upgraded from 6.11.2 to 7.30.2, git-2018-09-18 to 7.30.1 and
- 6.11.1 to 7.30.2, respectively. As a result
- services.datadog-agent has had breaking
- changes to the configuration file. For details, see the
- upstream
- changelog.
-
-
-
-
- opencv2 no longer includes the non-free
- libraries by default, and consequently
- pfstools no longer includes OpenCV support
- by default. Both packages now support an
- enableUnfree option to re-enable this
- functionality.
-
-
-
-
- services.xserver.displayManager.defaultSession = "plasma5"
- does not work anymore, instead use either
- "plasma" for the Plasma X11
- session or "plasmawayland" for
- the Plasma Wayland sesison.
-
-
-
-
- boot.kernelParams now only accepts one
- command line parameter per string. This change is aimed to
- reduce common mistakes like param = 12, which
- would be parsed as 3 parameters.
-
-
-
-
- nix.daemonNiceLevel and
- nix.daemonIONiceLevel have been removed in
- favour of the new options
- nix.daemonCPUSchedPolicy,
- nix.daemonIOSchedClass
- and
- nix.daemonIOSchedPriority.
- Please refer to the options documentation and the
- sched(7) and
- ioprio_set(2) man pages for guidance on how
- to use them.
-
-
-
-
- The coursier package’s binary was renamed
- from coursier to cs.
- Completions which haven’t worked for a while should now work
- with the renamed binary. To keep using
- coursier, you can create a shell alias.
-
-
-
-
- The services.mosquitto module has been
- rewritten to support multiple listeners and per-listener
- configuration. Module configurations from previous releases
- will no longer work and must be updated.
-
-
-
-
- The fluidsynth_1 attribute has been
- removed, as this legacy version is no longer needed in
- nixpkgs. The actively maintained 2.x series is available as
- fluidsynth unchanged.
-
-
-
-
- Nextcloud 20 (pkgs.nextcloud20) has been
- dropped because it was EOLed by upstream in 2021-10.
-
-
-
-
- The virtualisation.pathsInNixDB option was
- renamed
- virtualisation.additionalPaths.
-
-
-
-
- The services.ddclient.password option was
- removed, and replaced with
- services.ddclient.passwordFile.
-
-
-
-
- The default GNAT version has been changed: The
- gnat attribute now points to
- gnat12 instead of gnat9.
-
-
-
-
- retroArchCores has been removed. This means
- that using nixpkgs.config.retroarch to
- customize RetroArch cores is not supported anymore. Instead,
- use package overrides, for example:
- retroarch.override { cores = with libretro; [ citra snes9x ]; };.
- Also, retroarchFull derivation is available
- for those who want to have all RetroArch cores available.
-
-
-
-
- The Linux kernel for security reasons now restricts access to
- BPF syscalls via BPF_UNPRIV_DEFAULT_OFF=y.
- Unprivileged access can be reenabled via the
- kernel.unprivileged_bpf_disabled sysctl
- knob.
-
-
-
-
- /usr will always be included in the initial
- ramdisk. See the
- fileSystems.<name>.neededForBoot
- option. If any files exist under /usr
- (which is not typical for NixOS), they will be included in the
- initial ramdisk, increasing its size to a possibly problematic
- extent.
-
-
-
-
- pkgs.haskell-language-server will now by
- default be linked dynamically to improve TemplateHaskell
- compatibility. To mitigate the increased closure size it will
- now by default only support our current default ghc (at the
- moment 9.0.2). Add other ghc versions via e.g.
- pkgs.haskell-language-server.override { supportedGhcVersions = [ "90" "92" ]; }.
-
-
-
-
-
- Other Notable Changes
-
-
-
- The linux kernel package infrastructure was moved out of
- all-packages.nix, and restructured. Linux
- related functions and attributes now live under the
- pkgs.linuxKernel attribute set. In
- particular the versioned linuxPackages_*
- package sets (such as linuxPackages_5_4)
- and kernels from pkgs were moved there and
- now live under pkgs.linuxKernel.packages.*.
- The unversioned ones (such as
- linuxPackages_latest) remain untouched.
-
-
-
-
- In NixOS virtual machines (QEMU), the
- virtualisation module has been updated with
- new options:
-
-
-
-
- forwardPorts
- to configure IPv4 port forwarding,
-
-
-
-
- sharedDirectories
- to set up shared host directories,
-
-
-
-
- resolution
- to set the screen resolution,
-
-
-
-
- useNixStoreImage
- to use a disk image for the Nix store instead of 9P.
-
-
-
-
- In addition, the default
- msize
- parameter in 9P filesystems (including /nix/store and all
- shared directories) has been increased to 16K for improved
- performance.
-
-
-
-
- The setting
- services.openssh.logLevel
- "VERBOSE"
- "INFO". This brings NixOS in line
- with upstream and other Linux distributions, and reduces log
- spam on servers due to bruteforcing botnets.
-
-
- However, if
- services.fail2ban.enable
- is true, the fail2ban
- will override the verbosity to
- "VERBOSE", so that
- fail2ban can observe the failed login
- attempts from the SSH logs.
-
-
-
-
- The
- services.xserver.extraLayouts
- no longer cause additional rebuilds when a layout is added or
- modified.
-
-
-
-
- Sway: The terminal emulator rxvt-unicode is
- no longer installed by default via
- programs.sway.extraPackages. The current
- default configuration uses alacritty (and
- soon foot) so this is only an issue when
- using a customized configuration and not installing
- rxvt-unicode explicitly.
-
-
-
-
- python3 now defaults to Python 3.9. Python
- 3.9 introduces many deprecation warnings, please look at the
- What’s
- New In Python 3.9 post for more information.
-
-
-
-
- qtile hase been updated from
- 0.16.0 to 0.18.0, please check
- qtile
- changelog for changes.
-
-
-
-
- The claws-mail package now references the
- new GTK+ 3 release branch, major version 4. To use the GTK+ 2
- releases, one can install the
- claws-mail-gtk2 package.
-
-
-
-
- The wordpress module provides a new interface which allows to
- use different webservers with the new option
- services.wordpress.webserver.
- Currently httpd, caddy
- and nginx are supported. The definitions of
- wordpress sites should now be set in
- services.wordpress.sites.
-
-
- Sites definitions that use the old interface are automatically
- migrated in the new option. This backward compatibility will
- be removed in 22.05.
-
-
-
-
- The dokuwiki module provides a new interface which allows to
- use different webservers with the new option
- services.dokuwiki.webserver.
- Currently caddy and
- nginx are supported. The definitions of
- dokuwiki sites should now be set in
- services.dokuwiki.sites.
-
-
- Sites definitions that use the old interface are automatically
- migrated in the new option. This backward compatibility will
- be removed in 22.05.
-
-
-
-
- The order of NSS (host) modules has been brought in line with
- upstream recommendations:
-
-
-
-
- The myhostname module is placed before
- the resolve (optional) and
- dns entries, but after
- file (to allow overriding via
- /etc/hosts /
- networking.extraHosts, and prevent ISPs
- with catchall-DNS resolvers from hijacking
- .localhost domains)
-
-
-
-
- The mymachines module, which provides
- hostname resolution for local containers (registered with
- systemd-machined) is placed to the
- front, to make sure its mappings are preferred over other
- resolvers.
-
-
-
-
- If systemd-networkd is enabled, the
- resolve module is placed before
- files and
- myhostname, as it provides the same
- logic internally, with caching.
-
-
-
-
- The mdns(_minimal) module has been
- updated to the new priorities.
-
-
-
-
- If you use your own NSS host modules, make sure to update your
- priorities according to these rules:
-
-
-
-
- NSS modules which should be queried before
- resolved DNS resolution should use
- mkBefore.
-
-
-
-
- NSS modules which should be queried after
- resolved, files and
- myhostname, but before
- dns should use the default priority
-
-
-
-
- NSS modules which should come after dns
- should use mkAfter.
-
-
-
-
-
-
- The
- networking.wireless
- module (based on wpa_supplicant) has been heavily reworked,
- solving a number of issues and adding useful features:
-
-
-
-
- The automatic discovery of wireless interfaces at boot has
- been made reliable again (issues
- #101963,
- #23196).
-
-
-
-
- WPA3 and Fast BSS Transition (802.11r) are now enabled by
- default for all networks.
-
-
-
-
- Secrets like pre-shared keys and passwords can now be
- handled safely, meaning without including them in a
- world-readable file
- (wpa_supplicant.conf under /nix/store).
- This is achieved by storing the secrets in a secured
- environmentFile
- and referring to them though environment variables that
- are expanded inside the configuration.
-
-
-
-
- With multiple interfaces declared, independent
- wpa_supplicant daemons are started, one for each interface
- (the services are named
- wpa_supplicant-wlan0,
- wpa_supplicant-wlan1, etc.).
-
-
-
-
- The generated wpa_supplicant.conf file
- is now formatted for easier reading.
-
-
-
-
- A new
- scanOnLowSignal
- option has been added to facilitate fast roaming between
- access points (enabled by default).
-
-
-
-
- A new
- networks.<name>.authProtocols
- option has been added to change the authentication
- protocols used when connecting to a network.
-
-
-
-
-
-
- The
- networking.wireless.iwd
- module has a new
- networking.wireless.iwd.settings
- option.
-
-
-
-
- The
- services.smokeping.host
- option was added and defaulted to
- localhost. Before,
- smokeping listened to all interfaces by
- default. NixOS defaults generally aim to provide
- non-Internet-exposed defaults for databases and internal
- monitoring tools, see e.g.
- #100192.
- Further, the systemd service for smokeping
- got reworked defaults for increased operational stability, see
- PR
- #144127 for details.
-
-
-
-
- The
- services.syncoid.enable
- module now properly drops ZFS permissions after usage. Before
- it delegated permissions to whole pools instead of datasets
- and didn’t clean up after execution. You can manually look
- this up for your pools by running
- zfs allow your-pool-name and use
- zfs unallow syncoid your-pool-name to clean
- this up.
-
-
-
-
- Zfs: latestCompatibleLinuxPackages is now
- exported on the zfs package. One can use
- boot.kernelPackages = config.boot.zfs.package.latestCompatibleLinuxPackages;
- to always track the latest compatible kernel with a given
- version of zfs.
-
-
-
-
- Nginx will use the value of
- sslTrustedCertificate if provided for a
- virtual host, even if enableACME is set.
- This is useful for providers not using the same certificate to
- sign OCSP responses and server certificates.
-
-
-
-
- lib.formats.yaml’s
- generate will not generate JSON anymore,
- but instead use more of the YAML-specific syntax.
-
-
-
-
- MariaDB was upgraded from 10.5.x to 10.6.x. Please read the
- upstream
- release notes for changes and upgrade instructions.
-
-
-
-
- The MariaDB C client library, also known as libmysqlclient or
- mariadb-connector-c, was upgraded from 3.1.x to 3.2.x. While
- this should hopefully not have any impact, this upgrade comes
- with some changes to default behavior, so you might want to
- review the
- upstream
- release notes.
-
-
-
-
- GNOME desktop environment now enables
- QGnomePlatform as the Qt platform theme,
- which should avoid crashes when opening file chooser dialogs
- in Qt apps by using XDG desktop portal. Additionally, it will
- make the apps fit better visually.
-
-
-
-
- rofi has been updated from
- 1.6.1 to 1.7.0, one important
- thing is the removal of the old xresources based configuration
- setup. Read more
- in
- rofi’s changelog.
-
-
-
-
- ipfs now defaults to not listening on you local network. This
- setting was change as server providers won’t accept port
- scanning on their private network. If you have several ipfs
- instances running on a network you own, feel free to change
- the setting ipfs.localDiscovery = true;.
- localDiscovery enables different instances to discover each
- other and share data.
-
-
-
-
- lua and luajit
- interpreters have been patched to avoid looking into /usr/lib
- directories, thus increasing the purity of the build.
-
-
-
-
- Three new options,
- xdg.mime.addedAssociations,
- xdg.mime.defaultApplications,
- and
- xdg.mime.removedAssociations
- have been added to the
- xdg.mime module to
- allow the configuration of
- /etc/xdg/mimeapps.list.
-
-
-
-
- Kopia was upgraded from 0.8.x to 0.9.x. Please read the
- upstream
- release notes for changes and upgrade instructions.
-
-
-
-
- The systemd.network module has gained
- support for the FooOverUDP link type.
-
-
-
-
- The networking module has a new
- networking.fooOverUDP option to configure
- Foo-over-UDP encapsulations.
-
-
-
-
- networking.sits now supports Foo-over-UDP
- encapsulation.
-
-
-
-
- The virtualisation.libvirtd module has been
- refactored and updated with new options:
-
-
-
-
- virtualisation.libvirtd.qemu* options
- (e.g.:
- virtualisation.libvirtd.qemuRunAsRoot)
- were moved to
- virtualisation.libvirtd.qemu
- submodule,
-
-
-
-
- software TPM1/TPM2 support (e.g.: Windows 11 guests)
- (virtualisation.libvirtd.qemu.swtpm),
-
-
-
-
- custom OVMF package (e.g.:
- pkgs.OVMFFull with HTTP, CSM and Secure
- Boot support)
- (virtualisation.libvirtd.qemu.ovmf.package).
-
-
-
-
-
-
- The cawbird Twitter client now uses its own
- API keys to count as different application than upstream
- builds. This is done to evade application-level rate limiting.
- While existing accounts continue to work, users may want to
- remove and re-register their account in the client to enjoy a
- better user experience and benefit from this change.
-
-
-
-
- A new option
- services.prometheus.enableReload has been
- added which can be enabled to reload the prometheus service
- when its config file changes instead of restarting.
-
-
-
-
- The option
- services.prometheus.environmentFile has
- been removed since it was causing
- issues
- and Prometheus now has native support for secret files, i.e.
- basic_auth.password_file and
- authorization.credentials_file.
-
-
-
-
- Dokuwiki now supports caddy! However
-
-
-
-
- the nginx option has been removed, in the new
- configuration, please use the
- dokuwiki.webserver = "nginx"
- instead.
-
-
-
-
- The ${hostname} option has been deprecated,
- please use
- dokuwiki.sites = [ "${hostname}" ]
- instead
-
-
-
-
-
-
- The
- services.unifi
- module has been reworked, solving a number of issues. This
- leads to several user facing changes:
-
-
-
-
- The services.unifi.dataDir option is
- removed and the data is now always located under
- /var/lib/unifi/data. This is done to
- make better use of systemd state direcotiry and thus
- making the service restart more reliable.
-
-
-
-
- The unifi logs can now be found under:
- /var/log/unifi instead of
- /var/lib/unifi/logs.
-
-
-
-
- The unifi run directory can now be found under:
- /run/unifi instead of
- /var/lib/unifi/run.
-
-
-
-
-
-
- security.pam.services.<name>.makeHomeDir
- now uses umask=0077 instead of
- umask=0022 when creating the home
- directory.
-
-
-
-
- Loki has had another release. Some default values have been
- changed for the configuration and some configuration options
- have been renamed. For more details, please check
- the
- upgrade guide.
-
-
-
-
- julia now refers to
- julia-stable instead of
- julia-lts. In practice this means it has
- been upgraded from 1.0.4 to
- 1.5.4.
-
-
-
-
- RetroArch has been upgraded from version
- 1.8.5 to 1.9.13.2. Since
- the previous release was quite old, if you’re having issues
- after the upgrade, please delete your
- $XDG_CONFIG_HOME/retroarch/retroarch.cfg
- file.
-
-
-
-
- hydrus has been upgraded from version 438
- to 463. Since upgrading between releases
- this old is advised against, be sure to have a backup of your
- data before upgrading. For details, see
- the
- hydrus manual.
-
-
-
-
- More jdk and jre versions are now exposed via
- java-packages.compiler.
-
-
-
-
- The sets haskell.packages and
- haskell.compiler now contain for every ghc
- version an attribute with the minor version dropped. E.g. for
- ghc8107 there also now exists
- ghc810. Those attributes point to the same
- compilers and packagesets but have the advantage that e.g.
- ghc92 stays stable when we update from
- ghc925 to ghc926.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-2205.section.xml b/nixos/doc/manual/from_md/release-notes/rl-2205.section.xml
deleted file mode 100644
index 64217c53c3b8..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-2205.section.xml
+++ /dev/null
@@ -1,2840 +0,0 @@
-
- Release 22.05 (“Quokka”, 2022.05/30)
-
-
-
- Support is planned until the end of December 2022, handing over
- to 22.11.
-
-
-
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- Nix has been updated from 2.3 to 2.8. This mainly brings
- experimental support for Flakes, but also marks the
- nix command as experimental which now has
- to be enabled via the configuration explicitly. For more
- information and instructions for upgrades, see the relase
- notes for
- nix-2.4,
- nix-2.5,
- nix-2.6,
- nix-2.7
- and
- nix-2.8
-
-
-
-
- The firefox browser on
- x86_64-linux now makes use of
- profile-guided optimisation, resulting in a much more
- responsive browsing experience.
-
-
-
-
- GNOME has been upgraded to 42. Please take a look at their
- Release
- Notes for details. In particular, it replaces gedit
- with GNOME Text Editor, GNOME Terminal with GNOME Console
- (formerly King’s Cross) and GNOME Screenshot by a tool
- integrated into the Shell.
-
-
-
-
- PHP 8.1 is now available.
-
-
-
-
- systemd services can now set
- systemd.services.<name>.reloadTriggers
- instead of reloadIfChanged for a more
- granular distinction between reloads and restarts.
-
-
-
-
- Systemd has been upgraded to the version 250.
-
-
-
-
- Pulseaudio has been updated to version 15.0 and now optionally
- supports
- additional Bluetooth audio codecs such as aptX or LDAC,
- with codec switching available in
- pavucontrol. This feature is disabled by
- default, but can be enabled with the option
- hardware.pulseaudio.package = pkgs.pulseaudioFull;.
- Existing third-party modules that offered similar functions,
- such as pulseaudio-modules-bt or
- pulseaudio-hsphfpd, are obsolete and have
- been removed.
-
-
-
-
- PostgreSQL now defaults to major version 14.
-
-
-
-
- Module authors can use
- mkRenamedOptionModuleWith to automate the
- deprecation cycle without annoying out-of-tree module authors
- and their users.
-
-
-
-
- The default GHC version has been updated from 8.10.7 to 9.0.2.
- pkgs.haskellPackages and
- pkgs.ghc will now use this version by
- default.
-
-
-
-
- The GNOME and Plasma installation CDs now use
- pkgs.calamares and
- pkgs.calamares-nixos-extensions to allow
- users to easily install and set up NixOS with a GUI.
-
-
-
-
- security.acme.defaults has been added to
- simplify the configuration of settings for many certificates
- at once. This also opens up the option to use DNS-01
- validation when using enableACME web server
- virtual hosts (e.g.
- services.nginx.virtualHosts.*.enableACME).
-
-
-
-
-
- New Services
-
-
-
- 1password,
- command-lines and graphic interface for 1Password. Available
- as
- programs._1password
- and
- programs._1password-gui.
-
-
-
-
- aesmd,
- the Intel SGX Architectural Enclave Service Manager. Available
- as
- services.aesmd.
-
-
-
-
- agate,
- a very simple server for the Gemini hypertext protocol.
- Available as
- services.agate.
-
-
-
-
- apfs,
- a kernel module for mounting the Apple File System (APFS).
-
-
-
-
- argonone,
- a replacement daemon for the Raspberry Pi Argon One power
- button and cooler. Available at
- services.hardware.argonone.
-
-
-
-
- ArchiSteamFarm,
- a C# application with primary purpose of idling Steam cards
- from multiple accounts simultaneously. Available as
- services.archisteamfarm.
-
-
-
-
- BaGet,
- a lightweight NuGet and symbol server. Available at
- services.baget.
-
-
-
-
- bird-lg,
- a BGP looking glass for Bird Routing. Available as
- services.bird-lg.
-
-
-
-
- blocky,
- fast and lightweight DNS proxy as ad-blocker for local network
- with many features. Available as
- services.blocky.
-
-
-
-
- cloudflare-dyndns,
- CloudFlare Dynamic DNS client. Available as
- services.cloudflare-dyndns.
-
-
-
-
- Corosync
- and
- Pacemaker,
- A open-source high availability resource manager. Available as
- services.corosync
- and
- services.pacemaker.
-
-
-
-
- create_ap,
- a module for creating wifi hotspots using the program
- linux-wifi-hotspot. Available as
- services.create_ap.
-
-
-
-
- Envoy, a
- high-performance reverse proxy. Available as
- services.envoy.
-
-
-
-
- ergochat, a modern
- IRC with IRCv3 features. Available as
- services.ergochat.
-
-
-
-
- ethercalc,
- an online collaborative spreadsheet. Available as
- services.ethercalc.
-
-
-
-
- filebeat,
- a lightweight shipper for forwarding and centralizing log
- data. Available as
- services.filebeat.
-
-
-
-
- FRRouting, a
- popular suite of Internet routing protocol daemons (BGP, BFD,
- OSPF, IS-IS, VRRP and others). Available as
- services.frr.
-
-
-
-
- Grafana
- Mimir, an open source, horizontally scalable, highly
- available, multi-tenant, long-term storage for Prometheus.
- Available as
- services.mimir.
-
-
-
-
- Haste,
- a pastebin written in node.js. Available as
- services.haste.
-
-
-
-
- headscale,
- an Open Source implementation of the
- Tailscale
- Control Server. Available as
- services.headscale.
-
-
-
-
- heisenbridge,
- a bouncer-style Matrix IRC bridge. Available as
- services.heisenbridge.
-
-
-
-
- https-dns-proxy,
- DNS to DNS over HTTPS (DoH) proxy. Available as
- services.https-dns-proxy.
-
-
-
-
- input-remapper,
- an easy to use tool to change the mapping of your input device
- buttons. Available at
- services.input-remapper.
-
-
-
-
- InvoicePlane,
- web application for managing and creating invoices. Available
- at
- services.invoiceplane.
-
-
-
-
- k3b,
- the KDE disk burning application. Available as
- programs.k3b.
-
-
-
-
- K40-Whisperer,
- a program to control cheap Chinese laser cutters. Available as
- programs.k40-whisperer.enable.
- Users must add themselves to the k40 group
- to be able to access the device.
-
-
-
-
- kanidm,
- an identity management server written in Rust. Available as
- services.kanidm
-
-
-
-
- Maddy, a free
- an open source mail server. Available as
- services.maddy.
-
-
-
-
- matrix-conduit,
- a simple, fast and reliable chat server powered by matrix.
- Available as
- services.matrix-conduit.
-
-
-
-
- Moosefs, fault
- tolerant petabyte distributed file system. Available as
- moosefs.
-
-
-
-
- mozillavpn,
- the client for the
- Mozilla VPN
- service. Available as
- services.mozillavpn.
-
-
-
-
- mtr-exporter,
- a Prometheus exporter for mtr metrics. Available as
- services.mtr-exporter.
-
-
-
-
- nbd, a
- Network Block Device server. Available as
- services.nbd.
-
-
-
-
- netbox,
- infrastructure resource modeling (IRM) tool. Available as
- services.netbox.
-
-
-
-
- nethoscope,
- listen to your network traffic. Available as
- programs.nethoscope.
-
-
-
-
- nifi, an
- easy to use, powerful, and reliable system to process and
- distribute data. Available as
- services.nifi.
-
-
-
-
- nix-ld,
- Run unpatched dynamic binaries on NixOS. Available as
- programs.nix-ld.
-
-
-
-
- NNCP, NNCP
- (Node to Node copy) utilities and configuration, Available as
- programs.nncp.
-
-
-
-
- pgadmin4,
- an admin interface for the PostgreSQL database. Available at
- services.pgadmin.
-
-
-
-
- PowerDNS-Admin,
- a web interface for the PowerDNS server. Available at
- services.powerdns-admin.
-
-
-
-
- prometheus-pve-exporter,
- a tool that exposes information from the Proxmox VE API for
- use by Prometheus. Available as
- services.prometheus.exporters.pve.
-
-
-
-
- prosody-filer,
- a server for handling XMPP HTTP Upload requests. Available at
- services.prosody-filer.
-
-
-
-
- Public
- Inbox, an archives first approach to
- mailing lists. Available as
- services.public-inbox.
-
-
-
-
- r53-ddns,
- a small tool to run your own DDNS service via AWS Route53.
- Available as
- services.r53-ddns.
-
-
-
-
- rmfakecloud,
- a clone of the cloud sync the remarkable tablet. Available as
- services.rmfakecloud.
-
-
-
-
- rootless
- Docker, a systemd --user Docker
- service which runs without root permissions. Available as
- virtualisation.docker.rootless.enable.
-
-
-
-
- rstudio-server,
- a browser-based version of the RStudio IDE for the R
- programming language. Available as
- services.rstudio-server.
-
-
-
-
- rtsp-simple-server,
- ready-to-use RTSP / RTMP / HLS server and proxy that allows to
- read, publish and proxy video and audio streams. Available as
- services.rtsp-simple-server.
-
-
-
-
- Snipe-IT, a
- free open source IT asset/license management system. Available
- as
- services.snipe-it.
-
-
-
-
- snowflake-proxy,
- a system to defeat internet censorship. Available as
- services.snowflake-proxy.
-
-
-
-
- sslmate-agent,
- a daemon for managing SSL/TLS certificates on a server.
- Available as
- services.sslmate-agent.
-
-
-
-
- starship, a
- minimal, blazing-fast, and infinitely customizable prompt for
- any shell. Available at
- programs.startship.
-
-
-
-
- systembus-notify,
- allow system level notifications to reach the users. Available
- as
- services.systembus-notify.
- Please keep in mind that this service should only be enabled
- on machines with fully trusted users, as any local user is
- able to DoS user sessions by spamming notifications.
-
-
-
-
- teleport,
- allows engineers and security professionals to unify access
- for SSH servers, Kubernetes clusters, web applications, and
- databases across all environments. Available at
- services.teleport.
-
-
-
-
- tetrd, share your
- internet connection from your device to your PC and vice versa
- through a USB cable. Available at
- services.tetrd.
-
-
-
-
- uptermd, an
- open-source solution for sharing terminal sessions instantly
- over the public internet via secure tunnels. Available at
- services.uptermd.
-
-
-
-
- usbrelayd,
- an USB Relay MQTT daemon. Available as
- services.usbrelayd.
-
-
-
-
- webdav-server-rs,
- Webdav server in rust. Available as
- services.webdav-server-rs.
-
-
-
-
- wg-netmanager,
- the Wireguard network manager. Available as
- services.wg-netmanager.
-
-
-
-
- Zammad, a
- web-based, open source user support/ticketing solution.
- Available as
- services.zammad.
-
-
-
-
-
- Backward Incompatibilities
-
-
-
- pkgs.ghc now refers to
- pkgs.targetPackages.haskellPackages.ghc.
- This only makes a difference if you are
- cross-compiling and will ensure that
- pkgs.ghc always runs on the host platform
- and compiles for the target platform (similar to
- pkgs.gcc for example).
- haskellPackages.ghc still behaves as
- before, running on the build platform and compiling for the
- host platform (similar to stdenv.cc). This
- means you don’t have to adjust your derivations if you use
- haskellPackages.callPackage, but when using
- pkgs.callPackage and taking
- ghc as an input, you should now use
- buildPackages.ghc instead to ensure cross
- compilation keeps working (or switch to
- haskellPackages.callPackage).
-
-
-
-
- pkgs.ghc.withPackages as well as
- haskellPackages.ghcWithPackages etc. now
- needs be overridden directly, as opposed to overriding the
- result of calling it. Additionally, the
- withLLVM parameter has been renamed to
- useLLVM. So instead of
- (ghc.withPackages (p: [])).override { withLLVM = true; },
- one needs to use
- (ghc.withPackages.override { useLLVM = true; }) (p: []).
-
-
-
-
- The update of the haskell package set brings with it a new
- version of the xmonad module, which will
- break your configuration if you use launch
- as entrypoint. The example code the corresponding nixos module
- was adjusted, you may want to have a look at it.
-
-
-
-
- The home-assistant module now requires
- users that don’t want their configuration to be managed
- declaratively to set
- services.home-assistant.config = null;.
- This is required due to the way default settings are handled
- with the new settings style.
-
-
- Additionally the default list of
- extraComponents now includes the minimal
- dependencies to successfully complete the
- onboarding
- procedure.
-
-
-
-
- pkgs.emacsPackages.orgPackages is removed
- because org elpa is deprecated. The packages in the top level
- of pkgs.emacsPackages, such as org and
- org-contrib, refer to the ones in
- pkgs.emacsPackages.elpaPackages and
- pkgs.emacsPackages.nongnuPackages where the
- new versions will release.
-
-
-
-
- The configuration and state directories used by
- nixos-containers have been moved from
- /etc/containers and
- /var/lib/containers to
- /etc/nixos-containers and
- /var/lib/nixos-containers.
-
-
- If you are changing system.stateVersion to
- "22.05" manually on an existing
- system you are responsible for migrating these directories
- yourself.
-
-
- This is to improve compatibility with
- libcontainer based software such as Podman
- and Skopeo which assumes they have ownership over
- /etc/containers.
-
-
-
-
- lib.systems.supported has been removed, as
- it was overengineered for determining the systems to support
- in the nixpkgs flake. The list of systems exposed by the
- nixpkgs flake can now be accessed as
- lib.systems.flakeExposed.
-
-
-
-
- For new installations
- virtualisation.oci-containers.backend is
- now set to podman by default. If you still
- want to use Docker on systems where
- system.stateVersion is set to to
- "22.05" set
- virtualisation.oci-containers.backend = "docker";.Old
- systems with older stateVersions stay with
- docker.
-
-
-
-
- security.klogd was removed. Logging of
- kernel messages is handled by systemd since Linux 3.5.
-
-
-
-
- pkgs.ssmtp has been dropped due to the
- program being unmaintained. pkgs.msmtp can
- be used instead as a substitute sendmail
- implementation. The corresponding options
- services.ssmtp.* have been removed as well.
- programs.msmtp.* can be used instead for an
- equivalent setup. For example:
-
-
-{
- # Original ssmtp configuration:
- services.ssmtp = {
- enable = true;
- useTLS = true;
- useSTARTTLS = true;
- hostName = "smtp.example:587";
- authUser = "someone";
- authPassFile = "/secrets/password.txt";
- };
-
- # Equivalent msmtp configuration:
- programs.msmtp = {
- enable = true;
- accounts.default = {
- tls = true;
- tls_starttls = true;
- auth = true;
- host = "smtp.example";
- port = 587;
- user = "someone";
- passwordeval = "cat /secrets/password.txt";
- };
- };
-}
-
-
-
-
- services.kubernetes.addons.dashboard was
- removed due to it being an outdated version.
-
-
-
-
- services.kubernetes.scheduler.{port,address}
- now set --secure-port and
- --bind-address instead of
- --port and --address,
- since the former have been deprecated and are no longer
- functional in kubernetes>=1.23. Ensure that you are not
- relying on the insecure behaviour before upgrading.
-
-
-
-
- In the PowerDNS Recursor module
- (services.pdns-recursor), default values of
- several IP address-related NixOS options have been updated to
- match the default upstream behavior. In particular, Recursor
- by default will:
-
-
-
-
- listen on (and allows connections from) both IPv4 and IPv6
- addresses
- (services.pdns-recursor.dns.address,
- services.pdns-recursor.dns.allowFrom);
-
-
-
-
- allow only local connections to the REST API server
- (services.pdns-recursor.api.allowFrom).
-
-
-
-
-
-
- In the ncdns module, the default value of
- services.ncdns.address has been changed to
- the IPv6 loopback address (::1).
-
-
-
-
- openldap (and therefore the slapd LDAP
- server) were updated to version 2.6.2. The project introduced
- backwards-incompatible changes, namely the removal of the bdb,
- hdb, ndb, and shell backends in slapd. Therefore before
- updating, dump your database slapcat -n 1
- in LDIF format, and reimport it after updating your
- services.openldap.settings, which
- represents your cn=config.
-
-
- Additionally with 2.5 the argon2 module was included in the
- standard distrubtion and renamed from
- pw-argon2 to argon2.
- Remember to update your olcModuleLoad entry
- in cn=config.
-
-
-
-
- openssh has been update to 8.9p1, changing
- the FIDO security key middleware interface.
-
-
-
-
- git no longer hardcodes the path to
- openssh’ ssh binary to reduce the amount of rebuilds. If you
- are using git with ssh remotes and do not have a ssh binary in
- your enviroment consider adding openssh to
- it or switching to gitFull.
-
-
-
-
- services.k3s.enable no longer implies
- systemd.enableUnifiedCgroupHierarchy = false,
- and will default to the systemd cgroup driver
- when using services.k3s.docker = true. This
- change may require a reboot to take effect, and k3s may not be
- able to run if the boot cgroup hierarchy does not match its
- configuration. The previous behavior may be retained by
- explicitly setting
- systemd.enableUnifiedCgroupHierarchy = false
- in your configuration.
-
-
-
-
- fonts.fonts no longer includes ancient
- bitmap fonts when both
- config.services.xserver.enable and
- config.nixpkgs.config.allowUnfree are
- enabled. If you still want these fonts, use:
-
-
-{
- fonts.fonts = [
- pkgs.xorg.fontbhlucidatypewriter100dpi
- pkgs.xorg.fontbhlucidatypewriter75dpi
- pkgs.xorg.fontbh100dpi
- ];
-}
-
-
-
-
- services.prometheus.alertManagerTimeout has
- been removed as it has been deprecated upstream and has no
- effect.
-
-
-
-
- The DHCP server (services.dhcpd4,
- services.dhcpd6) has been hardened. The
- service is now using the systemd’s
- DynamicUser mechanism to run as an
- unprivileged dynamically-allocated user with limited
- capabilities. The dhcpd state files are now always stored in
- /var/lib/dhcpd{4,6} and the
- services.dhcpd4.stateDir and
- service.dhcpd6.stateDir options have been
- removed. If you were depending on root privileges or
- set{uid,gid,cap} binaries in dhcpd shell hooks, you may give
- dhcpd more capabilities with e.g.
- systemd.services.dhcpd6.serviceConfig.AmbientCapabilities.
-
-
-
-
- The mailpile email webclient
- (services.mailpile) has been removed due to
- its reliance on python2.
-
-
-
-
- services.ipfs.extraFlags is now escaped
- with utils.escapeSystemdExecArgs. If you
- rely on systemd interpolating extraFlags in
- the service ExecStart, this will no longer
- work.
-
-
-
-
- hbase version 0.98.24 has been removed. The
- package now defaults to version 2.4.11. Versions 1.7.1 and
- 3.0.0-alpha-2 are also available.
-
-
-
-
- services.paperless-ng was renamed to
- services.paperless. Accordingly, the
- paperless-ng-manage script (located in
- dataDir) was renamed to
- paperless-manage.
- services.paperless now uses
- paperless-ngx.
-
-
-
-
- The matrix-synapse service
- (services.matrix-synapse) has been
- converted to use the settings option
- defined in RFC42. This means that options that are part of
- your homeserver.yaml configuration, and
- that were specified at the top-level of the module
- (services.matrix-synapse) now need to be
- moved into
- services.matrix-synapse.settings. And while
- not all options you may use are defined in there, they are
- still supported, because you can set arbitrary values in this
- freeform type.
-
-
- The listeners.*.bind_address option was
- renamed to bind_addresses in order to match
- the upstream homeserver.yaml option name.
- It is now also a list of strings instead of a string.
-
-
- An example to make the required migration clearer:
-
-
- Before:
-
-
-{
- services.matrix-synapse = {
- enable = true;
-
- server_name = "example.com";
- public_baseurl = "https://example.com:8448";
-
- enable_registration = false;
- registration_shared_secret = "xohshaeyui8jic7uutuDogahkee3aehuaf6ei3Xouz4iicie5thie6nohNahceut";
- macaroon_secret_key = "xoo8eder9seivukaiPh1cheikohquuw8Yooreid0The4aifahth3Ou0aiShaiz4l";
-
- tls_certificate_path = "/var/lib/acme/example.com/fullchain.pem";
- tls_certificate_path = "/var/lib/acme/example.com/fullchain.pem";
-
- listeners = [ {
- port = 8448;
- bind_address = "";
- type = "http";
- tls = true;
- resources = [ {
- names = [ "client" ];
- compress = true;
- } {
- names = [ "federation" ];
- compress = false;
- } ];
- } ];
-
- };
-}
-
-
- After:
-
-
-{
- services.matrix-synapse = {
- enable = true;
-
- # this attribute set holds all values that go into your homeserver.yaml configuration
- # See https://github.com/matrix-org/synapse/blob/develop/docs/sample_config.yaml for
- # possible values.
- settings = {
- server_name = "example.com";
- public_baseurl = "https://example.com:8448";
-
- enable_registration = false;
- # pass `registration_shared_secret` and `macaroon_secret_key` via `extraConfigFiles` instead
-
- tls_certificate_path = "/var/lib/acme/example.com/fullchain.pem";
- tls_certificate_path = "/var/lib/acme/example.com/fullchain.pem";
-
- listeners = [ {
- port = 8448;
- bind_addresses = [
- "::"
- "0.0.0.0"
- ];
- type = "http";
- tls = true;
- resources = [ {
- names = [ "client" ];
- compress = true;
- } {
- names = [ "federation" ];
- compress = false;
- } ];
- } ];
- };
-
- extraConfigFiles = [
- "/run/keys/matrix-synapse/secrets.yaml"
- ];
- };
-}
-
-
- The secrets in your original config should be migrated into a
- YAML file that is included via
- extraConfigFiles. The filename must be
- quoted to prevent nix from copying it to the (world readable)
- store.
-
-
- Additionally a few option defaults have been synced up with
- upstream default values, for example the
- max_upload_size grew from
- 10M to 50M. For the same
- reason, the default media_store_path was
- changed from ${dataDir}/media to
- ${dataDir}/media_store if
- system.stateVersion is at least
- 22.05. Files will need to be manually moved
- to the new location if the stateVersion is
- updated.
-
-
- As of Synapse 1.58.0, the old groups/communities feature has
- been disabled by default. It will be completely removed with
- Synapse 1.61.0.
-
-
-
-
- The Keycloak package (pkgs.keycloak) has
- been switched from the Wildfly version, which will soon be
- deprecated, to the Quarkus based version. The Keycloak service
- (services.keycloak) has been updated to
- accommodate the change and now differs from the previous
- version in a few ways:
-
-
-
-
- services.keycloak.extraConfig has been
- removed in favor of the new
- settings-style
- services.keycloak.settings
- option. The available options correspond directly to
- parameters in conf/keycloak.conf. Some
- of the most important parameters are documented as
- suboptions, the rest can be found in the
- All
- configuration section of the Keycloak Server Installation
- and Configuration Guide. While the new
- configuration is much simpler and cleaner than the old
- JBoss CLI one, this unfortunately mean that there’s no
- straightforward way to convert an old configuration to the
- new format and some settings may not even be available
- anymore.
-
-
-
-
- services.keycloak.frontendUrl was
- removed and the frontend URL is now configured through the
- hostname family of settings in
- services.keycloak.settings
- instead. See the
- Hostname
- section of the Keycloak Server Installation and
- Configuration Guide for more details. Additionally,
- /auth was removed from the default
- context path and needs to be added back in
- services.keycloak.settings.http-relative-path
- if you want to keep compatibility with your current
- clients.
-
-
-
-
- services.keycloak.bindAddress,
- services.keycloak.forceBackendUrlToFrontendUrl,
- services.keycloak.httpPort and
- services.keycloak.httpsPort have been
- removed in favor of their equivalent options in
- services.keycloak.settings.
- httpPort and
- httpsPort have additionally had their
- types changed from str to
- port.
-
-
- The new names are as follows:
-
-
-
-
- bindAddress:
- services.keycloak.settings.http-host
-
-
-
-
- forceBackendUrlToFrontendUrl:
- services.keycloak.settings.hostname-strict-backchannel
-
-
-
-
- httpPort:
- services.keycloak.settings.http-port
-
-
-
-
- httpsPort:
- services.keycloak.settings.https-port
-
-
-
-
-
-
- For example, when using a reverse proxy the migration could
- look like this:
-
-
- Before:
-
-
- services.keycloak = {
- enable = true;
- httpPort = "8080";
- frontendUrl = "https://keycloak.example.com/auth";
- database.passwordFile = "/run/keys/db_password";
- extraConfig = {
- "subsystem=undertow"."server=default-server"."http-listener=default".proxy-address-forwarding = true;
- };
- };
-
-
- After:
-
-
- services.keycloak = {
- enable = true;
- settings = {
- http-port = 8080;
- hostname = "keycloak.example.com";
- http-relative-path = "/auth";
- proxy = "edge";
- };
- database.passwordFile = "/run/keys/db_password";
- };
-
-
-
-
- The MoinMoin wiki engine
- (services.moinmoin) has been removed,
- because Python 2 is being retired from nixpkgs.
-
-
-
-
- Services in the hadoop module previously
- set openFirewall to true by default. This
- has now been changed to false. Node definitions for multi-node
- clusters would need openFirewall = true; to
- be added to to hadoop services when upgrading from NixOS
- 21.11.
-
-
-
-
- services.hadoop.yarn.nodemanager now uses
- cgroup-based CPU limit enforcement by default. Additionally,
- the option useCGroups was added to
- nodemanagers as an easy way to switch back to the old
- behavior.
-
-
-
-
- The wafHook hook now honors
- NIX_BUILD_CORES when
- enableParallelBuilding is not set
- explicitly. Packages can restore the old behaviour by setting
- enableParallelBuilding=false.
-
-
-
-
- pkgs.claws-mail-gtk2, representing Claws
- Mail’s older release version three, was removed in order to
- get rid of Python 2. Please switch to
- claws-mail, which is Claws Mail’s latest
- release based on GTK+3 and Python 3.
-
-
-
-
- The writers.writePython2 and corresponding
- writers.writePython2Bin convenience
- functions to create executable Python 2 scripts in the store
- were removed in preparation of removal of the Python 2
- interpreter. Scripts have to be converted to Python 3 for use
- with writers.writePython3 or
- writers.writePyPy2 needs to be used.
-
-
-
-
- buildGoModule was updated to use
- go_1_17, third party derivations that
- specify >= go 1.17 in the main go.mod
- will need to regenerate their vendorSha256
- hash.
-
-
-
-
- The gnome-passwordsafe package updated to
- version
- 6.x and renamed to gnome-secrets.
-
-
-
-
- services.gnome.experimental-features.realtime-scheduling
- option has been removed, as GNOME Shell now
- uses
- rtkit. Use
- security.rtkit.enable = true; instead. As
- before, you will need to have it enabled using GSettings.
-
-
-
-
- services.telepathy will no longer be
- enabled by default for GNOME desktops, one should enable it in
- their configs if using Empathy or Polari.
-
-
-
-
- If you previously used
- /etc/docker/daemon.json, you need to
- incorporate the changes into the new option
- virtualisation.docker.daemon.settings.
-
-
-
-
- Ntopng (services.ntopng) is updated to
- 5.2.1 and uses a separate Redis instance if
- system.stateVersion is at least
- 22.05. Existing setups shouldn’t be
- affected.
-
-
-
-
- The backward compatibility in
- services.wordpress to configure sites with
- the old interface has been removed. Please use
- services.wordpress.sites instead.
-
-
-
-
- The backward compatibility in
- services.dokuwiki to configure sites with
- the old interface has been removed. Please use
- services.dokuwiki.sites instead.
-
-
-
-
- opensmtpd-extras is no longer build with python2 scripting
- support due to python2 deprecation in nixpkgs
-
-
-
-
- services.miniflux.adminCredentialFiles is
- now required, instead of defaulting to
- admin and password.
-
-
-
-
- The taskserver module no longer implicitly
- opens ports in the firewall configuration. This is now
- controlled through the option
- services.taskserver.openFirewall.
-
-
-
-
- The autorestic package has been upgraded
- from 1.3.0 to 1.5.0 which introduces breaking changes in
- config file, check
- their
- migration guide for more details.
-
-
-
-
- teleport has been upgraded to major version
- 9. Please see upstream
- upgrade
- instructions and
- release
- notes.
-
-
-
-
- For pkgs.python3.pkgs.ipython, its direct
- dependency
- pkgs.python3.pkgs.matplotlib-inline (which
- is really an adapter to integrate matplotlib in ipython if it
- is installed) does not depend on
- pkgs.python3.pkgs.matplotlib anymore. This
- is closer to a non-Nix install of ipython. This has the added
- benefit to reduce the closure size of
- ipython from ~400MB to ~160MB (including
- ~100MB for python itself).
-
-
-
-
- documentation.man has been refactored to
- support choosing a man implementation other than GNU’s
- man-db. For this,
- documentation.man.manualPages has been
- renamed to
- documentation.man.man-db.manualPages. If
- you want to use the new alternative man implementation
- mandoc, add
- documentation.man = { enable = true; man-db.enable = false; mandoc.enable = true; }
- to your configuration.
-
-
-
-
- Normal users (with isNormalUser = true)
- which have non-empty subUidRanges or
- subGidRanges set no longer have additional
- implicit ranges allocated. To enable automatic allocation back
- set autoSubUidGidRange = true.
-
-
-
-
- idris2 now requires
- --package when using packages
- contrib and network,
- while previously these idris2 packages were automatically
- loaded.
-
-
-
-
- The iputils package, which is installed by default, no longer
- provides the legacy tools tftpd and
- traceroute6. More tools
- (ninfod, rarpd, and
- rdisc) are going to be removed in the next
- release. See
- upstream’s
- release notes for more details and available
- replacements.
-
-
-
-
- services.thelounge.private was removed in
- favor of services.thelounge.public, to
- follow with upstream changes.
-
-
-
-
- pkgs.docbookrx was removed since it’s
- unmaintained
-
-
-
-
- pkgs._7zz is now correctly licensed as
- LGPL3+ and BSD3 with optional unfree unRAR licensed code
-
-
-
-
- The vim.customize function produced by
- vimUtils.makeCustomizable now has a
- slightly different interface:
-
-
-
-
- The wrapper now includes everything in the given Vim
- derivation if name is
- "vim" (the default). This
- makes the wrapManual argument obsolete,
- but this behavior can be overridden by setting the
- standalone argument.
-
-
-
-
- All the executables present in the given derivation (or,
- in standalone mode, only the
- *vim ones) are wrapped. This makes the
- wrapGui argument obsolete.
-
-
-
-
- The vimExecutableName and
- gvimExecutableName arguments were
- replaced by a single executableName
- argument in which the shell variable
- $exe can be used to refer to the
- wrapped executable’s name.
-
-
-
-
- See the comments in
- pkgs/applications/editors/vim/plugins/vim-utils.nix
- for more details.
-
-
- vimUtils.vimWithRC was removed. You should
- instead use customize on a Vim derivation,
- which now accepts vimrcFile and
- gvimrcFile arguments.
-
-
-
-
- tilp2 was removed together with its module
-
-
-
-
- The F-PROT antivirus (fprot package) and
- its service module were removed because it reached
- end-of-life.
-
-
-
-
- bird1 and its modules
- services.bird as well as
- services.bird6 have been removed. Upgrade
- to services.bird2.
-
-
-
-
- The options
- networking.interfaces.<name>.ipv4.routes
- and
- networking.interfaces.<name>.ipv6.routes
- are no longer ignored when using networkd instead of the
- default scripted network backend by setting
- networking.useNetworkd to
- true.
-
-
-
-
- The miller package has been upgraded from
- 5.10.3 to
- 6.2.0.
- See
- What’s
- new in Miller 6.
-
-
-
-
- MultiMC has been replaced with the fork PrismLauncher due to
- upstream developers being hostile to 3rd party package
- maintainers. PrismLauncher removes all MultiMC branding and is
- aimed at providing proper 3rd party packages like the one
- contained in Nixpkgs. This change affects the data folder
- where game instances and other save and configuration files
- are stored. Users with existing installations should rename
- ~/.local/share/multimc to
- ~/.local/share/PrismLauncher. The main
- config file’s path has also moved from
- ~/.local/share/multimc/multimc.cfg to
- ~/.local/share/PrismLauncher/prismlauncher.cfg.
-
-
-
-
- systemd-nspawn@.service settings have been
- reverted to the default systemd behaviour. User namespaces are
- now activated by default. If you want to keep running nspawn
- containers without user namespaces you need to set
- systemd.nspawn.<name>.execConfig.PrivateUsers = false
-
-
-
-
- systemd-shutdown is now properly linked on
- shutdown to unmount all filesystems and device mapper devices
- cleanly. This can be disabled using
- systemd.shutdownRamfs.enable.
-
-
-
-
- The Tor SOCKS proxy is now actually disabled if
- services.tor.client.enable is set to
- false (the default). If you are using this
- functionality but didn’t change the setting or set it to
- false, you now need to set it to
- true.
-
-
-
-
- services.github-runner has been hardened.
- Notably address families and system calls have been
- restricted, which may adversely affect some kinds of testing,
- e.g. using AF_BLUETOOTH to test bluetooth
- devices.
-
-
-
-
- The terraform 0.12 compatibility has been removed and the
- terraform.withPlugins and
- terraform-providers.mkProvider
- implementations simplified. Providers now need to be stored
- under
- $out/libexec/terraform-providers/<registry>/<owner>/<name>/<version>/<os>_<arch>/terraform-provider-<name>_v<version>
- (which mkProvider does).
-
-
- This breaks back-compat so it’s not possible to mix-and-match
- with previous versions of nixpkgs. In exchange, it now becomes
- possible to use the providers from
- nixpkgs-terraform-providers-bin
- directly.
-
-
-
-
- The dendrite package has been upgraded from
- 0.5.1 to
- 0.6.5.
- Instances configured with split sqlite databases, which has
- been the default in NixOS, require merging of the federation
- sender and signing key databases. See upstream
- release
- notes on version 0.6.0 for details on database changes.
-
-
-
-
- The existing pkgs.opentelemetry-collector
- has been moved to
- pkgs.opentelemetry-collector-contrib to
- match the actual source being the contrib
- edition. pkgs.opentelemetry-collector is
- now the actual core release of opentelemetry-collector. If you
- use the community contributions you should change the package
- you refer to. If you don’t need them update your commands from
- otelcontribcol to
- otelcorecol and enjoy a 7x smaller binary.
-
-
-
-
- services.zookeeper has a new option
- jre for specifying the JRE to start
- zookeeper with. It defaults to the JRE that
- pkgs.zookeeper was wrapped with, instead of
- pkgs.jre. This changes the JRE to
- pkgs.jdk11_headless by default.
-
-
-
-
- pkgs.pgadmin now refers to
- pkgs.pgadmin4. pgadmin3
- has been removed.
-
-
-
-
- pkgs.minetestclient_4 and
- pkgs.minetestserver_4 have been removed, as
- the last 4.x release was in 2018.
- pkgs.minetestclient (equivalent to
- pkgs.minetest ) and
- pkgs.minetestserver can be used instead.
-
-
-
-
- pkgs.noto-fonts-cjk is now deprecated in
- favor of pkgs.noto-fonts-cjk-sans and
- pkgs.noto-fonts-cjk-serif because they each
- have different release schedules. To maintain compatibility
- with prior releases of Nixpkgs,
- pkgs.noto-fonts-cjk is currently an alias
- of pkgs.noto-fonts-cjk-sans and doesn’t
- include serif fonts.
-
-
-
-
- pkgs.epgstation has been upgraded from v1
- to v2, resulting in incompatible changes in the database
- scheme and configuration format.
-
-
-
-
- Some top-level settings under
- services.epgstation
- is now deprecated because it was redudant due to the same
- options being present in
- services.epgstation.settings.
-
-
-
-
- The option services.epgstation.basicAuth
- was removed because basic authentication support was dropped
- by upstream.
-
-
-
-
- The option
- services.epgstation.database.passwordFile
- no longer has a default value. Make sure to set this option
- explicitly before upgrading. Change the database password if
- necessary.
-
-
-
-
- The
- services.epgstation.settings
- option now expects options for config.yml
- in EPGStation v2.
-
-
-
-
- Existing data for the
- services.epgstation
- module would have to be backed up prior to the upgrade. To
- back up exising data to
- /tmp/epgstation.bak, run
- sudo -u epgstation epgstation run backup /tmp/epgstation.bak.
- To import that data after to the upgrade, run
- sudo -u epgstation epgstation run v1migrate /tmp/epgstation.bak
-
-
-
-
- switch-to-configuration (the script that is
- run when running nixos-rebuild switch for
- example) has been reworked
-
-
-
-
- The interface that allows activation scripts to restart
- units has been streamlined. Restarting and reloading is
- now done by a single file
- /run/nixos/activation-restart-list that
- honors restartIfChanged and
- reloadIfChanged of the units.
-
-
-
-
- Preferring to reload instead of restarting can still
- be achieved using
- /run/nixos/activation-reload-list.
-
-
-
-
-
-
- The script now uses a proper ini-file parser to parse
- systemd units. Some values are now only searched in one
- section instead of in the entire unit. This is only
- relevant for units that don’t use the NixOS systemd moule.
-
-
-
-
- RefuseManualStop,
- X-OnlyManualStart,
- X-StopOnRemoval,
- X-StopOnReconfiguration are only
- searched in the [Unit] section
-
-
-
-
- X-ReloadIfChanged,
- X-RestartIfChanged,
- X-StopIfChanged are only searched
- in the [Service] section
-
-
-
-
-
-
-
-
- The services.bookstack.cacheDir option has
- been removed, since the cache directory is now handled by
- systemd.
-
-
-
-
- The services.bookstack.extraConfig option
- has been replaced by
- services.bookstack.config which implements
- a
- settings-style
- configuration.
-
-
-
-
- lib.assertMsg and
- lib.assertOneOf no longer return
- false if the passed condition is
- false, throwing the
- given error message instead (which makes the resulting error
- message less cluttered). This will not impact the behaviour of
- code using these functions as intended, namely as top-level
- wrapper for assert conditions.
-
-
-
-
- The vpnc package has been changed to use
- GnuTLS instead of OpenSSL by default for licensing reasons.
-
-
-
-
- The default version of nextcloud is
- nextcloud24. Please note
- that it’s not possible to
- upgrade nextcloud across multiple major
- versions! This means it’s e.g. not possible to upgrade from
- nextcloud22 to
- nextcloud24 in a single deploy and most
- 21.11 users will have to upgrade to
- nextcloud23 first.
-
-
-
-
- pkgs.vimPlugins.onedark-nvim now refers to
- navarasu/onedark.nvim
- (formerly refers to
- olimorris/onedarkpro.nvim).
-
-
-
-
- services.pipewire.enable will default to
- enabling the WirePlumber session manager instead of
- pipewire-media-session. pipewire-media-session is deprecated
- by upstream and not recommended, but can still be manually
- enabled by setting
- services.pipewire.media-session.enable to
- true and
- services.pipewire.wireplumber.enable to
- false.
-
-
-
-
- pkgs.makeDesktopItem has been refactored to
- provide a more idiomatic API. Specifically:
-
-
-
-
- All valid options as of FDO Desktop Entry specification
- version 1.4 can now be passed in as explicit arguments
-
-
-
-
- exec can now be null, for entries that
- are not of type Application
-
-
-
-
- mimeType argument is renamed to
- mimeTypes for consistency
-
-
-
-
- mimeTypes,
- categories,
- implements,
- keywords, onlyShowIn
- and notShowIn take lists of strings
- instead of one string with semicolon separators
-
-
-
-
- extraDesktopEntries renamed to
- extraConfig for consistency
-
-
-
-
- Actions should now be provided as an attrset
- actions, the Actions
- line will be autogenerated.
-
-
-
-
- extraEntries is removed.
-
-
-
-
- Additional validation is added both at eval time and at
- build time.
-
-
-
-
- See the vscode package for a more detailed
- example.
-
-
-
-
- Existing resholve* functions have been
- renamed and nested under pkgs.resholve.
- Update uses to:
-
-
-
-
- resholvePackage ->
- resholve.mkDerivation
-
-
-
-
- resholveScript ->
- resholve.writeScript
-
-
-
-
- resholveScriptBin ->
- resholve.writeScriptBin
-
-
-
-
-
-
- pkgs.cosmopolitan no longer provides the
- cosmoc command. It has been moved to
- pkgs.cosmoc.
-
-
-
-
- pkgs.graalvmXX-ce packages no longer
- provide support for Python/Ruby/WASM, instead focusing only in
- Java and Native Image Support. If you need to add support
- back, please see the
- pkgs.graalvmCEPackages.mkGraal function to
- create your own customized version of GraalVM with support for
- what you need.
-
-
-
-
-
- Other Notable Changes
-
-
-
- The option
- services.redis.servers
- was added to support per-application
- redis-server which is more secure since
- Redis databases are only mere key prefixes without any
- configuration or ACL of their own. Backward-compatibility is
- preserved by mapping old
- services.redis.settings to
- services.redis.servers."".settings,
- but you are strongly encouraged to name each
- redis-server instance after the application
- using it, instead of keeping that nameless one. Except for the
- nameless
- services.redis.servers."" still
- accessible at 127.0.0.1:6379, and to the
- members of the Unix group redis through the
- Unix socket /run/redis/redis.sock, all
- other services.redis.servers.${serverName}
- are only accessible by default to the members of the Unix
- group redis-${serverName} through the Unix
- socket /run/redis-${serverName}/redis.sock.
-
-
-
-
- The option
- virtualisation.vmVariant
- was added to allow users to make changes to the
- nixos-rebuild build-vm configuration that
- do not apply to their normal system.
-
-
- The config.system.build.vm attribute now
- always exists and defaults to the value from
- vmVariant. Configurations that import the
- virtualisation/qemu-vm.nix module
- themselves will override this value, such that
- vmVariant is not used.
-
-
- Similarly
- virtualisation.vmVariantWithBootloader
- was added.
-
-
-
-
- The configuration portion of the nix-daemon
- module has been reworked and exposed as
- nix.settings:
-
-
-
-
- Legacy options have been mapped to the corresponding
- options under under
- nix.settings
- and will be deprecated when NixOS 21.11 reaches end of
- life.
-
-
-
-
- nix.buildMachines.publicHostKey
- has been added.
-
-
-
-
-
-
- kops
- defaults to 1.23.2, which will enable
- Instance
- Metadata Service Version 2 and require tokens on new
- clusters with Kubernetes >= 1.22. This will increase
- security by default, but may break some types of workloads.
- The default behaviour for
- spec.kubeDNS.nodeLocalDNS.forwardToKubeDNS
- has changed from true to
- false. Cilium now has
- disable-cnp-status-updates: true by
- default. Set this to false if you rely on the
- CiliumNetworkPolicy status fields. Support for Kubernetes
- 1.17, the Lyft CNI, Weave CNI on Kubernetes >= 1.23, CentOS
- 7 and 8, Debian 9, RHEL 7, and Ubuntu 16.05 (Xenial) has been
- removed. See the
- 1.22
- release notes and
- 1.23
- release notes for more details, including other
- significant changes.
-
-
-
-
- Mattermost has been upgraded to extended support version 6.3
- as the previously packaged extended support version 5.37 is
- reaching
- end of life. Migration may take some time, see the
- changelog
- and
- important
- upgrade notes.
-
-
-
-
- The
- writers.writePyPy2/writers.writePyPy3
- and corresponding
- writers.writePyPy2Bin/writers.writePyPy3Bin
- convenience functions to create executable Python 2/3 scripts
- using the PyPy interpreter were added.
-
-
-
-
- Some improvements have been made to the
- hadoop module:
-
-
-
-
- A gatewayRole option has been added,
- for deploying hadoop cluster configuration files to a node
- that does not have any active services
-
-
-
-
- Support for older versions of hadoop have been added to
- the module
-
-
-
-
- Overriding and extending site XML files has been made
- easier
-
-
-
-
-
-
- The auto-upgrade service now accepts persistent (default:
- true) parameter. By default auto-upgrade will now run
- immediately if it would have been triggered at least once
- during the time when the timer was inactive.
-
-
-
-
- Mastodon now uses services.redis.servers to
- start a new redis server, instead of using a global redis
- server. This improves compatibility with other services that
- use redis.
-
-
- Note that this will recreate the redis database, although
- according to the
- Mastodon
- docs, this is almost harmless:
-
-
-
- Losing the Redis database is almost harmless: The only
- irrecoverable data will be the contents of the Sidekiq
- queues and scheduled retries of previously failed jobs. The
- home and list feeds are stored in Redis, but can be
- regenerated with tootctl.
-
-
-
- If you do want to save the redis database, you can use the
- following commands:
-
-
-redis-cli save
-cp /var/lib/redis/dump.rdb "/var/lib/redis-mastodon/dump.rdb"
-
-
-
-
- Peertube now uses services.redis.servers to start a new redis
- server, instead of using a global redis server. This improves
- compatibility with other services that use redis.
-
-
- Redis database is used for storage only cache and job queue.
- More information can be found here -
- Peertube
- architecture.
-
-
- If you do want to save the redis database, you can use the
- following commands before upgrade OS:
-
-
-redis-cli save
-sudo mkdir /var/lib/redis-peertube
-sudo cp /var/lib/redis/dump.rdb /var/lib/redis-peertube/dump.rdb
-
-
-
-
- Added the keter NixOS module. Keter reverse
- proxies requests to your loaded application based on virtual
- hostnames.
-
-
-
-
- If you are using Wayland you can choose to use the Ozone
- Wayland support in Chrome and several Electron apps by setting
- the environment variable NIXOS_OZONE_WL=1
- (for example via
- environment.sessionVariables.NIXOS_OZONE_WL = "1").
- This is not enabled by default because Ozone Wayland is still
- under heavy development and behavior is not always flawless.
- Furthermore, not all Electron apps use the latest Electron
- versions.
-
-
-
-
- A new option group
- systemd.network.wait-online was added, with
- options to configure
- systemd-networkd-wait-online.service:
-
-
-
-
- anyInterface allows specifying that the
- network should be considered online when at
- least one interface is online (useful on
- laptops)
-
-
-
-
- timeout defines how long to wait for
- the network to come online
-
-
-
-
- extraArgs for everything else
-
-
-
-
-
-
- The influxdb2 package was split into
- influxdb2-server and
- influxdb2-cli, matching the split that took
- place upstream. A combined influxdb2
- package is still provided in this release for backwards
- compatibilty, but will be removed at a later date.
-
-
-
-
- The unifi package was switched from
- unifi6 to unifi7. Direct
- downgrades from Unifi 7 to Unifi 6 are not possible and
- require restoring from a backup made by Unifi 6.
-
-
-
-
- programs.zsh.autosuggestions.strategy now
- takes a list of strings instead of a string.
-
-
-
-
- The asterisk and
- asterisk-stable packages were switched from
- asterisk_18 to the newly-packaged
- asterisk_19. Asterisk 13 and 17 have been
- removed as they have reached their end of life.
-
-
-
-
- The services.unifi.openPorts option default
- value of true is now deprecated and will be
- changed to false in 22.11. Configurations
- using this default will print a warning when rebuilt.
-
-
-
-
- The services.unifi-video.openPorts option
- default value of true is now deprecated and
- will be changed to false in 22.11.
- Configurations using this default will print a warning when
- rebuilt.
-
-
-
-
- security.acme certificates will now
- correctly check for CA revokation before reaching their
- minimum age.
-
-
-
-
- Removing domains from
- security.acme.certs._name_.extraDomainNames
- will now correctly remove those domains during rebuild/renew.
-
-
-
-
- MariaDB is now offered in several versions, not just the
- newest one. So if you have a need for running MariaDB 10.4 for
- example, you can now just set
- services.mysql.package = pkgs.mariadb_104;.
- In general, it is recommended to run the newest version, to
- get the newest features, while sticking with an LTS version
- will most likely provide a more stable experience. Sometimes
- software is also incompatible with the newest version of
- MariaDB.
-
-
-
-
- The option
- programs.ssh.enableAskPassword
- was added, decoupling the setting of
- SSH_ASKPASS from
- services.xserver.enable. This allows easy
- usage in non-X11 environments, e.g. Wayland.
-
-
-
-
- programs.ssh.knownHosts
- has gained an extraHostNames option to
- augment hostNames. It is now possible to
- use the attribute name of a knownHosts
- entry as the primary host name and specify secondary host
- names using extraHostNames without having
- to duplicate the primary host name.
-
-
-
-
- The services.stubby module was converted to
- a
- settings-style
- configuration.
-
-
-
-
- The option
- services.xserver.desktopManager.runXdgAutostartIfNone
- was added in order to automatically run XDG autostart files
- for sessions without a desktop manager. This replaces helpers
- like the dex package.
-
-
-
-
- When setting
- i18n.inputMethod.enabled
- to fcitx5, it no longer creates
- corresponding systemd user services. It now relies on XDG
- autostart files to start and work properly in your desktop
- sessions. If you are using only a window manager without a
- desktop manager, you need to enable
- services.xserver.desktopManager.runXdgAutostartIfNone
- or using the dex package to make
- fcitx5 work.
-
-
-
-
- The option services.duplicati.dataDir has
- been added to allow changing the location of duplicati’s
- files.
-
-
-
-
- The options boot.extraModprobeConfig and
- boot.blacklistedKernelModules now also take
- effect in the initrd by copying the file
- /etc/modprobe.d/nixos.conf into the initrd.
-
-
-
-
- nixos-generate-config now puts the dhcp
- configuration in hardware-configuration.nix
- instead of configuration.nix.
-
-
-
-
- ORY Kratos was updated to version 0.9.0-alpha.3, which
- introduces some breaking changes:
-
-
-
-
- All endpoints at the Admin API are now exposed at
- /admin/. For example, endpoint
- https://kratos:4434/identities is now
- exposed at
- https://kratos:4434/admin/identities
-
-
-
-
- Configuration key
- selfservice.whitelisted_return_urls has
- been renamed to allowed_return_urls
-
-
-
-
- The password_identifier form field of
- the password login strategy has been renamed to
- identifier to make compatibility with
- passwordless flows possible.
-
-
-
-
- Instead of having a global
- default_schema_url which developers
- used to update their schema, you now need to define the
- default_schema_id which must reference
- schema ID in your config.
-
-
-
-
- Calling /self-service/recovery without
- flow ID or with an invalid flow ID while authenticated
- will now respond with an error instead of redirecting to
- the default page.
-
-
-
-
- If you are relying on the SQLite images, update your
- Docker Pull commands as follows:
-
-
-
-
- docker pull oryd/kratos:{version}
-
-
-
-
-
-
- Additionally, all passwords now have to be at least 8
- characters long.
-
-
-
-
- For more details, see:
-
-
-
-
- Release
- Notes for v0.8.1-alpha-1
-
-
-
-
- Release
- Notes for v0.8.2-alpha-1
-
-
-
-
- Release
- Notes for v0.9.0-alpha-1
-
-
-
-
- Release
- Notes for v0.9.0-alpha-3
-
-
-
-
-
-
-
-
- fetchFromSourcehut now allows fetching
- repositories recursively using fetchgit or
- fetchhg if the argument
- fetchSubmodules is set to
- true.
-
-
-
-
- A module for declarative configuration of openconnect VPN
- profiles was added under
- networking.openconnect.
-
-
-
-
- The element-desktop package now has an
- useKeytar option (defaults to
- true), which allows disabling
- keytar and in turn
- libsecret usage (which binds to native
- credential managers / keychain libraries).
-
-
-
-
- The option services.thelounge.plugins has
- been added to allow installing plugins for The Lounge. Plugins
- can be found in
- pkgs.theLoungePlugins.plugins and
- pkgs.theLoungePlugins.themes.
-
-
-
-
- The option
- services.xserver.videoDriver = [ "nvidia" ];
- will now also install
- nvidia
- VA-API drivers by default.
-
-
-
-
- The firmwareLinuxNonfree package has been
- renamed to linux-firmware.
-
-
-
-
- It is now possible to specify wordlists to include as handy to
- access environment variables using the
- config.environment.wordlist configuration
- options.
-
-
-
-
- The services.mbpfan module was converted to
- a
- RFC
- 0042 configuration.
-
-
-
-
- The default value for
- programs.spacefm.settings.graphical_su got
- unset. It previously pointed to gksu which
- has been removed.
-
-
-
-
- The Dino XMPP client
- was updated to 0.3, adding support for audio and video calls.
-
-
-
-
- services.mattermost.plugins has been added
- to allow the declarative installation of Mattermost plugins.
- Plugins are automatically repackaged using autoPatchelf.
-
-
-
-
- services.logrotate.enable
- now defaults to true if any rotate path has been defined, and
- some paths have been added by default.
-
-
-
-
- The logrotate module also has been updated to freeform syntax:
- services.logrotate.paths and
- services.logrotate.extraConfig will work,
- but issue deprecation warnings and
- services.logrotate.settings
- should now be used instead.
-
-
-
-
- security.pam.ussh has been added, which
- allows authorizing PAM sessions based on SSH
- certificates held within an SSH agent,
- using
- pam-ussh.
-
-
-
-
- The vscode-extensions.ionide.ionide-fsharp
- package has been updated to 6.0.0 and now requires .NET 6.0.
-
-
-
-
- The phpPackages.box package has been
- updated from 2.7.5 to 3.16.0. See the
- upgrade
- guide for more details.
-
-
-
-
- The zrepl package has been updated from
- 0.4.0 to 0.5:
-
-
-
-
- The RPC protocol version was bumped; all zrepl daemons in
- a setup must be updated and restarted before replication
- can resume.
-
-
-
-
- A bug involving encrypt-on-receive has been fixed. Read
- the
- zrepl
- documentation and check the output of
- zfs get -r encryption,zrepl:placeholder PATH_TO_ROOTFS
- on the receiver.
-
-
-
-
-
-
- The polybar package has been updated from
- 3.5.7 to 3.6.2. See
- the
- changelog for more details.
-
-
-
-
- Breaking changes include changes to escaping rules in
- configuration values, changes in behavior when
- encountering invalid tag names, and changes to
- inter-process-messaging (IPC).
-
-
-
-
-
-
- Renamed option
- services.openssh.challengeResponseAuthentication
- to
- services.openssh.kbdInteractiveAuthentication.
- Reason is that the old name has been deprecated upstream.
- Using the old option name will still work, but produce a
- warning.
-
-
-
-
- services.autorandr now allows for adding
- hooks and profiles declaratively.
-
-
-
-
- The pomerium-cli command has been moved out
- of the pomerium package into the
- pomerium-cli package, following upstream’s
- repository split. If you are using the
- pomerium-cli command, you should now
- install the pomerium-cli package.
-
-
-
-
- The option
- services.networking.networkmanager.enableFccUnlock
- was added to support FCC unlock procedures. Since release
- 1.18.4, the ModemManager daemon no longer automatically
- performs the FCC unlock procedure by default. See
- the
- docs for more details.
-
-
-
-
- programs.tmux has a new option
- plugins that accepts a list of packages
- from the tmuxPlugins group. The specified
- packages are added to the system and loaded by
- tmux.
-
-
-
-
- The polkit service, available at
- security.polkit.enable, is now disabled by
- default. It will automatically be enabled through services and
- desktop environments as needed.
-
-
-
-
- mercury was updated to 22.01.1, which has
- some breaking changes
- (Mercury
- 22.01 news).
-
-
-
-
- xfsprogs was update to version 5.15, which enables inobtcount
- and bigtime by default on filesystem creation. Support for
- these features was added in kernel 5.10 and deemed stable in
- kernel 5.15. If you want to be able to mount XFS filesystems
- created with this release of xfsprogs on kernel releases older
- than 5.10, you need to format them with
- mkfs.xfs -m bigtime=0 -m inobtcount=0.
-
-
-
-
- services.xserver.desktopManager.xfce now
- includes Xfce’s screen locker,
- xfce4-screensaver that is enabled by
- default. You can disable it by setting
- false to
- services.xserver.desktopManager.xfce.enableScreensaver.
-
-
-
-
- The hadoop package has added support for
- aarch64-linux and
- aarch64-darwin as of 3.3.1
- (#158613).
-
-
-
-
- The R package now builds again on
- aarch64-darwin
- (#158992).
-
-
-
-
- The nss package was split into
- nss_esr and nss_latest,
- with nss being an alias for
- nss_esr. This was done to ease maintenance
- of nss and dependent high-profile packages
- like firefox.
-
-
-
-
- The default scribus version is now 1.5,
- while version 1.4 is still available as
- scribus_1_4
- (#172700).
-
-
-
-
- The Nextcloud module now supports to create a Mysql database
- automatically with
- services.nextcloud.database.createLocally
- enabled.
-
-
-
-
- The Nextcloud module now allows setting the value of the
- max-age directive of the
- Strict-Transport-Security HTTP header,
- which is now controlled by the
- services.nextcloud.https option, rather
- than services.nginx.recommendedHttpHeaders.
-
-
-
-
- The spark3 package has been updated from
- 3.1.2 to 3.2.1
- (#160075):
-
-
-
-
- Testing has been enabled for
- aarch64-linux in addition to
- x86_64-linux.
-
-
-
-
- The spark3 package is now usable on
- aarch64-darwin as a result of
- #158613
- and
- #158992.
-
-
-
-
-
-
- The option services.snapserver.openFirewall
- will no longer default to true starting
- with NixOS 22.11. Enable it explicitly if you need to control
- Snapserver remotely or connect streamig clients from other
- hosts.
-
-
-
-
- The option
- networking.useDHCP
- isn’t deprecated anymore. When using
- systemd-networkd,
- a generic .network-unit is added which
- enables DHCP for each interface matching
- en*, eth* or
- wl* with priority 99 (which means that it
- doesn’t have any effect if such an interface is matched by a
- .network-unit with a lower priority). In
- case of scripted networking, no behavior was changed.
-
-
-
-
- The new
- postgresqlTestHook
- runs a PostgreSQL server for the duration of package checks.
-
-
-
-
- zfs was updated from 2.1.4 to 2.1.5,
- enabling it to be used with Linux kernel 5.18.
-
-
-
-
- stdenv.mkDerivation now supports a
- self-referencing finalAttrs: parameter
- containing the final mkDerivation arguments
- including overrides. drv.overrideAttrs now
- supports two parameters
- finalAttrs: previousAttrs:. This allows
- packaging configuration to be overridden in a consistent
- manner by providing an alternative to
- rec {} syntax.
-
-
- Additionally, passthru can now reference
- finalAttrs.finalPackage containing the
- final package, including attributes such as the output paths
- and overrideAttrs.
-
-
- New language integrations can be simplified by overriding a
- prototype package containing the
- language-specific logic. This removes the need for a extra
- layer of overriding for the generic builder
- arguments, thus removing a usability problem and source of
- error.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-2211.section.xml b/nixos/doc/manual/from_md/release-notes/rl-2211.section.xml
deleted file mode 100644
index 2d7226caa5b5..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-2211.section.xml
+++ /dev/null
@@ -1,1841 +0,0 @@
-
- Release 22.11 (“Raccoon”, 2022.11/30)
-
- The NixOS release team is happy to announce a new version of NixOS
- 22.11. NixOS is a Linux distribution, whose set of packages can also
- be used on other Linux systems and macOS.
-
-
- This release is supported until the end of June 2023, handing over
- to NixOS 23.05.
-
-
- To upgrade to the latest release follow the
- upgrade chapter.
-
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- includes the following highlights:
-
-
-
-
- Software that uses the crypt password
- hashing API is now using the implementation provided by
- libxcrypt
- instead of glibc’s, which enables support for more secure
- algorithms.
-
-
-
-
- Support for algorithms that libxcrypt
- does
- not consider strong are
- deprecated as of this
- release, and will be removed in NixOS 23.05.
-
-
-
-
- This includes system login passwords. Given this, we
- strongly encourage all
- users to update their system passwords, as you will be
- unable to login if password hashes are not migrated by the
- time their support is removed.
-
-
-
-
- When using
- users.users.<name>.hashedPassword
- to configure user passwords, run
- mkpasswd, and use the yescrypt hash
- that is provided as the new value.
-
-
-
-
- On the other hand, for interactively configured user
- passwords, simply re-set the passwords for all users
- with passwd.
-
-
-
-
- This release introduces warnings for the use of
- deprecated hash algorithms for both methods of
- configuring passwords. To make sure you migrated
- correctly, run
- nixos-rebuild switch.
-
-
-
-
-
-
-
-
- The NixOS documentation is now generated from markdown. While
- docbook is still part of the documentation build process, it’s
- a big step towards the full migration.
-
-
-
-
- aarch64-linux is now included in the
- nixos-22.11 and
- nixos-22.11-small channels. This means that
- when those channel update, both
- x86_64-linux and
- aarch64-linux will be available in the
- binary cache.
-
-
-
-
- aarch64-linux ISOs are now available on the
- downloads
- page.
-
-
-
-
- nsncd is now available as a replacement of
- nscd.
-
-
- nscd is responsible for resolving
- hostnames, users and more in NixOS and has been a long
- standing source of bugs, such as sporadic network freezes.
-
-
- More context in this
- issue.
-
-
- Help us test the new implementation by setting
- services.nscd.enableNsncd to
- true.
-
-
- We plan to use nsncd by default in NixOS
- 23.05.
-
-
-
-
- Linode cloud images are now supported by importing
- ${modulesPath}/virtualisation/linode-image.nix
- and accessing system.build.linodeImage on
- the output.
-
-
-
-
- hardware.nvidia has a new option,
- hardware.nvidia.open, that can be used to
- enable the usage of NVIDIA’s open-source kernel driver. Note
- that the driver’s support for GeForce and Workstation GPUs is
- still alpha quality, see
- the
- release announcement for more information.
-
-
-
-
- The emacs package now makes use of native
- compilation which means:
-
-
-
-
- Emacs packages from Nixpkgs, builtin or not, will do
- native compilation ahead of time so you can enjoy the
- benefit of native compilation without compiling them on
- you machine;
-
-
-
-
- Emacs packages from somewhere else, e.g.
- package-install, will perform
- asynchronously deferred native compilation. If you do not
- want this, maybe to avoid CPU consumption for compilation,
- you can use
- (setq native-comp-deferred-compilation nil)
- to disable it while still benefiting from native
- compilation for packages from Nixpkgs.
-
-
-
-
-
-
-
- Internal changes
-
-
-
- Haskell ghcWithPackages is now up to 15
- times faster to evaluate, thanks to changing
- lib.closePropagation from a quadratic to
- linear complexity. Please see backward incompatibilities notes
- below.
- https://github.com/NixOS/nixpkgs/pull/194391
-
-
-
-
- For cross-compilation targets that can also run on the
- building machine, we now run tests. This, for example, is the
- case for the pkgsStatic and
- pkgsLLVM package sets or i686 packages on
- x86_64 machines.
-
-
-
-
- To simplify cross-compilation in NixOS, this release
- introduces the nixpkgs.hostPlatform and
- nixpkgs.buildPlatform options. These cover
- and override the
- nixpkgs.{system,localSystem,crossSystem}
- options.
-
-
-
-
- hostPlatform is the platform or
- system string of the
- NixOS system described by the configuration.
-
-
-
-
- buildPlatform is the platform that is
- responsible for building the NixOS configuration. It
- defaults to the hostPlatform, for a
- non-cross build configuration. To cross compile, set
- buildPlatform to a different value.
-
-
-
-
- The new options convey the same information, but with fewer
- options, and following the Nixpkgs terminology.
-
-
- The existing options
- nixpkgs.{system,localSystem,crossSystem}
- have not been formally deprecated, to allow for evaluation of
- the change and to allow for a transition period so that in
- time the ecosystem can switch without breaking compatibility
- with any supported NixOS release.
-
-
-
-
-
- Notable version updates
-
-
-
- Nix has been upgraded from v2.8.1 to v2.11.0. For more
- information, please see the release notes for
- 2.9,
- 2.10
- and
- 2.11.
-
-
-
-
- OpenSSL now defaults to OpenSSL 3, updated from 1.1.1.
-
-
-
-
- GNOME has been upgraded to version 43. Please see the
- release
- notes for details.
-
-
-
-
- KDE Plasma has been upgraded from v5.24 to v5.26. Please see
- the release notes for
- v5.25
- and
- v5.26
- for more details on the included changes.
-
-
-
-
- Cinnamon has been updated to 5.4, and the Cinnamon module now
- defaults to Blueman as the Bluetooth manager and slick-greeter
- as the LightDM greeter, to match upstream.
-
-
-
-
- PHP now defaults to PHP 8.1, updated from 8.0.
-
-
-
-
- Perl has been updated to 5.36, and its core module
- HTTP::Tiny was patched to verify SSL/TLS
- certificates by default.
-
-
-
-
- Python now defaults to 3.10, updated from 3.9.
-
-
-
-
-
- Backward Incompatibilities
-
-
-
- Nixpkgs now requires Nix 2.3 or newer.
-
-
-
-
- The isCompatible predicate checking CPU
- compatibility is no longer exposed by the platform sets
- generated using lib.systems.elaborate. In
- most cases you will want to use the new
- canExecute predicate instead which also
- takes the kernel / syscall interface into account.
- lib.systems.parse.isCompatible still
- exists, but has changed semantically: Architectures with
- differing endianness modes are no longer considered
- compatible.
-
-
-
-
- ngrok has been upgraded from 2.3.40 to
- 3.0.4. Please see
- the
- upgrade guide and
- changelog.
- Notably, breaking changes are that the config file format has
- changed and support for single hyphen arguments was dropped.
-
-
-
-
- i18n.supportedLocales is now only generated
- with the locales set in i18n.defaultLocale
- and i18n.extraLocaleSettings.
-
-
-
-
- This reduces the final system closure size by up to 200MB.
-
-
-
-
- If you require all locales installed, set the option to
- [ "all" ].
-
-
-
-
-
-
- Deprecated settings logrotate.paths and
- logrotate.extraConfig have been removed.
- Please convert any uses to
- services.logrotate.settings
- instead.
-
-
-
-
- The isPowerPC predicate, found on
- platform attrsets
- (hostPlatform,
- buildPlatform,
- targetPlatform, etc) has been removed in
- order to reduce confusion. The predicate was was defined such
- that it matches only the 32-bit big-endian members of the
- POWER/PowerPC family, despite having a name which would imply
- a broader set of systems. If you were using this predicate,
- you can replace foo.isPowerPC with
- (with foo; isPower && is32bit && isBigEndian).
-
-
-
-
- The fetchgit fetcher now uses
- cone
- mode by default for sparse checkouts.
- Non-cone
- mode can be enabled by passing
- nonConeMode = true, but note that non-cone
- mode is deprecated and this option may be removed alongside a
- future Git update without notice.
-
-
-
-
- The fetchgit fetcher supports sparse
- checkouts via the sparseCheckout option.
- This used to accept a multi-line string with
- directories/patterns to check out, but now requires a list of
- strings.
-
-
-
-
- openssh was updated to version 9.1,
- disabling the generation of DSA keys when using
- ssh-keygen -A as they are insecure. Also,
- SetEnv directives in
- ssh_config and
- sshd_config are now first-match-wins.
-
-
-
-
- bsp-layout no longer uses the command
- cycle to switch to other window layouts, as
- it got replaced by the commands previous
- and next.
-
-
-
-
- The Barco ClickShare driver/client package
- pkgs.clickshare-csc1 and the option
- programs.clickshare-csc1.enable have been
- removed, as it requires qt4, which reached
- its end-of-life 2015 and will no longer be supported by
- nixpkgs.
- According
- to Barco many of their base unit models can be used
- with Google Chrome and the Google Cast extension.
-
-
-
-
- services.hbase has been renamed to
- services.hbase-standalone. For production
- HBase clusters, use services.hadoop.hbase
- instead.
-
-
-
-
- The p4 package now only includes the
- open-source Perforce Helix Core command-line client and APIs.
- It no longer installs the unfree Helix Core Server binaries
- p4d, p4broker, and
- p4p. To install the Helix Core Server
- binaries, use the p4d package instead.
-
-
-
-
- The OpenSSL extension for the PHP interpreter used by
- Nextcloud is built against OpenSSL 1.1 if
- is below
- 22.11. This is to make sure that people
- using
- server-side
- encryption don’t lose access to their files.
-
-
- In any other case, it’s safe to use OpenSSL 3 for PHP’s
- OpenSSL extension. This can be done by setting
-
- to false.
-
-
-
-
- The coq package and versioned variants
- starting at coq_8_14 no longer include
- CoqIDE, which is now available through
- coqPackages.coqide. It is still possible to
- get CoqIDE as part of the coq package by
- overriding the buildIde argument of the
- derivation.
-
-
-
-
- PHP 7.4 is no longer supported due to upstream not supporting
- this version for the entire lifecycle of the 22.11 release.
-
-
-
-
- The ipfs package and module were renamed to kubo. The kubo
- module now uses an RFC42-style settings
- option instead of extraConfig and the
- gatewayAddress,
- apiAddress and
- swarmAddress options were renamed. Using
- the old names will print a warning but still work.
-
-
-
-
- pkgs.cosign does not provide the
- cosigned binary anymore. The
- sget binary has been moved into its own
- package.
-
-
-
-
- Emacs now uses the Lucid toolkit by default instead of GTK
- because of stability and compatibility issues. Users who still
- wish to remain using GTK can do so by using
- emacs-gtk.
-
-
-
-
- kanidm has been updated to 1.1.0-alpha.10
- and now requires a TLS certificate and key. It will always
- start https and-–-if enabled-–-an LDAPS
- server and no HTTP and LDAP server anymore.
-
-
-
-
- riak package removed along with
- services.riak module, due to lack of
- maintainer to update the package.
-
-
-
-
- ppd files in pkgs.cups-drv-rastertosag-gdi
- are now gzipped. If you refer to such a ppd file with its path
- (e.g. via
- hardware.printers.ensurePrinters)
- you will need to append .gz to the path.
-
-
-
-
- xow package removed along with the
- hardware.xow module, due to the project
- being deprecated in favor of xone, which is
- available via the hardware.xone module.
-
-
-
-
- dd-agent package removed along with the
- services.dd-agent module, due to the
- project being deprecated in favor of
- datadog-agent, which is available via the
- services.datadog-agent module.
-
-
-
-
- teleport has been upgraded to major version
- 10. Please see upstream
- upgrade
- instructions and
- release
- notes.
-
-
-
-
- lib.closePropagation now needs that all
- gathered sets have an outPath attribute.
-
-
-
-
- lemmy module option
- services.lemmy.settings.database.createLocally
- moved to
- services.lemmy.database.createLocally.
-
-
-
-
- virtlyst package and services.virtlyst
- module removed, due to lack of maintainers.
-
-
-
-
- The nix.checkConfig option now fully
- disables the config check. The new
- nix.checkAllErrors option behaves like
- nix.checkConfig previously did.
-
-
-
-
- generateOptparseApplicativeCompletions and
- generateOptparseApplicativeCompletion from
- haskell.lib.compose (and
- haskell.lib) have been deprecated in favor
- of generateOptparseApplicativeCompletions
- (plural!) as provided by the haskell package sets (so
- haskellPackages.generateOptparseApplicativeCompletions
- etc.). The latter allows for cross-compilation (by
- automatically disabling generation of completion in the cross
- case). For it to work properly you need to make sure that the
- function comes from the same context as the package you are
- trying to override, i.e. always use the same package set as
- your package is coming from or – even better – use
- self.generateOptparseApplicativeCompletions
- if you are overriding a haskell package set. The old functions
- are retained for backwards compatibility, but yield are
- warning.
-
-
-
-
- The services.graphite.api and
- services.graphite.beacon NixOS options, and
- the python3.pkgs.graphite_api,
- python3.pkgs.graphite_beacon and
- python3.pkgs.influxgraph packages, have
- been removed due to lack of upstream maintenance.
-
-
-
-
- The trace binary from
- perf-linux package has been removed, due to
- being a duplicate of the perf binary.
-
-
-
-
- The aws package has been removed due to
- being abandoned by the upstream. It is recommended to use
- awscli or awscli2
- instead.
-
-
-
-
- The
- CEmu
- TI-84 Plus CE emulator package has been renamed to
- cemu-ti. The
- Cemu Wii U
- emulator is now packaged as cemu.
-
-
-
-
- systemd-networkd v250 deprecated, renamed,
- and moved some sections and settings which leads to the
- following breaking module changes:
-
-
-
-
- systemd.network.networks.<name>.dhcpV6PrefixDelegationConfig
- is renamed to
- systemd.network.networks.<name>.dhcpPrefixDelegationConfig.
-
-
-
-
- systemd.network.networks.<name>.dhcpV6Config
- no longer accepts the
- ForceDHCPv6PDOtherInformation= setting.
- Please use the WithoutRA= and
- UseDelegatedPrefix= settings in your
- systemd.network.networks.<name>.dhcpV6Config
- and the DHCPv6Client= setting in your
- systemd.network.networks.<name>.ipv6AcceptRAConfig
- to control when the DHCPv6 client is started and how the
- delegated prefixes are handled by the DHCPv6 client.
-
-
-
-
- systemd.network.networks.<name>.networkConfig
- no longer accepts the IPv6Token=
- setting. Use the Token= setting in your
- systemd.network.networks.<name>.ipv6AcceptRAConfig
- instead. The
- systemd.network.networks.<name>.ipv6Prefixes.*.ipv6PrefixConfig
- now also accepts the Token= setting.
-
-
-
-
-
-
- arangodb versions 3.3, 3.4, and 3.5 have
- been removed because they are at EOL upstream. The default is
- now 3.10.0. Support for aarch64-linux has been removed since
- the target cannot be built reproducibly. By default
- arangodb is now built for the
- haswell architecture. If you wish to build
- for a different architecture, you may override the
- targetArchitecture argument with a value
- from
- this
- list supported upstream. Some architecture specific
- optimizations are also conditionally enabled. You may alter
- this behavior by overriding the
- asmOptimizations parameter. You may also
- add additional architecture support by adding more
- -DHAS_XYZ flags to
- cmakeFlags via
- overrideAttrs.
-
-
-
-
- The meta.mainProgram attribute of packages
- in wineWowPackages now defaults to
- "wine64".
-
-
-
-
- The paperless module now defaults
- PAPERLESS_TIME_ZONE to your configured
- system timezone.
-
-
-
-
- The top-level termonad-with-packages alias
- for termonad has been removed.
-
-
-
-
- Linux 4.9 has been removed because it will reach its end of
- life within the lifespan of 22.11.
-
-
-
-
- (Neo)Vim can not be configured with
- configure.pathogen anymore to reduce
- maintainance burden. Use configure.packages
- instead.
-
-
-
-
- Neovim can not be configured with plug anymore (still works
- for vim).
-
-
-
-
- The adguardhome module no longer uses
- host and port options,
- use settings.bind_host and
- settings.bind_port instead.
-
-
-
-
- The default kops version is now 1.25.1 and
- support for 1.22 and older has been dropped.
-
-
-
-
- The zrepl package has been updated from
- 0.5.0 to 0.6.0. See the
- changelog
- for details.
-
-
-
-
- k3s no longer supports Docker as runtime
- due to upstream dropping support.
-
-
-
-
- cassandra_2_1 and
- cassandra_2_2 have been removed. Please
- update to cassandra_3_11 or
- cassandra_3_0. See the
- changelog
- for more information about the upgrade process.
-
-
-
-
- mysql57 has been removed. Please update to
- mysql80 or mariadb. See
- the
- upgrade
- guide for more information.
-
-
-
-
- Consequently, cqrlog and
- amorok now use mariadb
- instead of mysql57 for their embedded
- databases. Running mysql_upgrade may be
- neccesary.
-
-
-
-
- k3s supports clusterInit
- option, and it is enabled by default, for servers.
-
-
-
-
- percona-server56 has been removed. Please
- migrate to mysql or
- mariadb if possible.
-
-
-
-
- obs-studio hase been updated to version 28.
- If you have packaged custom plugins, check if they are
- compatible. obs-websocket has been
- integrated into obs-studio.
-
-
-
-
- signald has been bumped to
- 0.23.0. For the upgrade, a migration
- process is necessary. It can be done by running a command like
- this before starting signald.service:
-
-
-signald -d /var/lib/signald/db \
- --database sqlite:/var/lib/signald/db \
- --migrate-data
-
-
- For further information, please read the upstream changelogs.
-
-
-
-
- stylua no longer accepts
- lua52Support and
- luauSupport overrides. Use
- features instead, which defaults to
- [ "lua54" "luau" ].
-
-
-
-
- ocamlPackages.ocaml_extlib has been renamed
- to ocamlPackages.extlib.
-
-
-
-
- pkgs.fetchNextcloudApp has been rewritten
- to circumvent impurities in e.g. tarballs from GitHub and to
- make it easier to apply patches. This means that your hashes
- are out-of-date and the (previously required) attributes
- name and version are no
- longer accepted.
-
-
-
-
- The Syncthing service now only allows absolute paths—starting
- with / or ~/—for
- services.syncthing.folders.<name>.path.
- In a future release other paths will be allowed again and
- interpreted relative to
- services.syncthing.dataDir.
-
-
-
-
- services.github-runner and
- services.github-runners.<name> gained
- the option serviceOverrides which allows
- overriding the systemd serviceConfig. If
- you have been overriding the systemd service configuration
- (i.e., by defining
- systemd.services.github-runner.serviceConfig),
- you have to use the serviceOverrides option
- now. Example:
-
-
-services.github-runner.serviceOverrides.SupplementaryGroups = [
- "docker"
-];
-
-
-
-
-
- Other Notable Changes
-
-
-
- PHP is now built in NTS (Non-Thread Safe)
- mode by default.
-
-
-
-
- For Apache and mod_php usage, we enable
- ZTS (Zend Thread Safe) mode. This has
- been a common practice for a long time in other
- distributions.
-
-
-
-
-
-
- firefox, thunderbird and
- librewolf now come with Wayland support by
- default. The firefox-wayland,
- firefox-esr-wayland,
- thunderbird-wayland and
- librewolf-wayland attributes are obsolete
- and have been aliased to their generic attribute.
-
-
-
-
- The xplr package has been updated from
- 0.18.0 to 0.19.0, which brings some breaking changes. See the
- upstream
- release notes for more details.
-
-
-
-
- Configuring multiple GitHub runners is now possible through
- services.github-runners.<name>. The
- options under services.github-runner
- remain, to configure a single runner.
-
-
-
-
- github-runner gained support for ephemeral
- runners and registrations using a personal access token (PAT)
- instead of a registration token. See
- services.github-runner.ephemeral and
- services.github-runner.tokenFile for
- details.
-
-
-
-
- A new module was added to provide hardware support for the
- Saleae Logic device family, providing the options
- hardware.saleae-logic.enable and
- hardware.saleae-logic.package.
-
-
-
-
- ZFS module will no longer allow hibernation by default.
-
-
-
-
- This is a safety measure to prevent data loss cases like
- the ones described at
- OpenZFS/260
- and
- OpenZFS/12842.
-
-
-
-
- Use the boot.zfs.allowHibernation
- option to configure this behaviour.
-
-
-
-
-
-
- Mastodon now automatically removes remote media attachments
- older than 30 days. This is configurable through
- services.mastodon.mediaAutoRemove.
-
-
-
-
- The Redis module now disables RDB persistence when
- services.redis.servers.<name>.save = []
- instead of using the Redis default.
-
-
-
-
- Neo4j was updated from version 3 to version 4. See upstream’s
- migration
- guide for information on how to migrate your instance.
-
-
-
-
- The networking.wireguard module now can set
- the mtu on interfaces and tag its packets with an fwmark.
-
-
-
-
- The option overrideStrategy was added to
- the different systemd unit options
- (systemd.services.<name>,
- systemd.sockets.<name>, …) to allow
- enforcing the creation of a dropin file, rather than the main
- unit file, by setting it to asDropin. This
- is useful in cases where the existence of the main unit file
- is not known to Nix at evaluation time, for example when the
- main unit file is provided by adding a package to
- systemd.packages. See the fix proposed in
- NixOS’s
- systemd abstraction doesn’t work with systemd template
- units for an example.
-
-
-
-
- The polymc package has been removed due to
- a rogue maintainer. It has been replaced by
- prismlauncher, a fork by the rest of the
- maintainers. For more details, see
- the
- PR that made this change and
- the
- issue detailing the vulnerability. Users with existing
- installations should rename
- ~/.local/share/polymc to
- ~/.local/share/PrismLauncher. The main
- config file’s path has also moved from
- ~/.local/share/polymc/polymc.cfg to
- ~/.local/share/PrismLauncher/prismlauncher.cfg.
-
-
-
-
- The bloat package has been updated from
- unstable-2022-03-31 to unstable-2022-10-25, which brings a
- breaking change. See
- this
- upstream commit message for details.
-
-
-
-
- Synapse’s systemd unit has been hardened.
-
-
-
-
- The module services.grafana was refactored
- to be compliant with
- RFC
- 0042. To be precise, this means that the following
- things have changed:
-
-
-
-
- The newly introduced option
- is an
- attribute-set that will be converted into Grafana’s INI
- format. This means that the configuration from
- Grafana’s
- configuration reference can be directly written as
- attribute-set in Nix within this option.
-
-
-
-
- The option
- services.grafana.extraOptions has been
- removed. This option was an association of environment
- variables for Grafana. If you had an expression like
-
-
-{
- services.grafana.extraOptions.SECURITY_ADMIN_USER = "foobar";
-}
-
-
- your Grafana instance was running with
- GF_SECURITY_ADMIN_USER=foobar in its
- environment.
-
-
- For the migration, it is recommended to turn it into the
- INI format, i.e. to declare
-
-
-{
- services.grafana.settings.security.admin_user = "foobar";
-}
-
-
- instead.
-
-
- The keys in
- services.grafana.extraOptions have the
- format
- <INI section name>_<Key Name>.
- Further details are outlined in the
- configuration
- reference.
-
-
- Alternatively you can also set all your values from
- extraOptions to
- systemd.services.grafana.environment,
- make sure you don’t forget to add the
- GF_ prefix though!
-
-
-
-
- Previously, the options
- services.grafana.provision.datasources
- and
- services.grafana.provision.dashboards
- expected lists of datasources or dashboards for the
- declarative
- provisioning.
-
-
- To declare lists of
-
-
-
-
- datasources, please
- rename your declarations to
- services.grafana.provision.datasources.settings.datasources.
-
-
-
-
- dashboards, please
- rename your declarations to
- services.grafana.provision.dashboards.settings.providers.
-
-
-
-
- This change was made to support more features for that:
-
-
-
-
- It’s possible to declare the
- apiVersion of your dashboards and
- datasources by
- services.grafana.provision.datasources.settings.apiVersion
- (or
- services.grafana.provision.dashboards.settings.apiVersion).
-
-
-
-
- Instead of declaring datasources and dashboards in
- pure Nix, it’s also possible to specify configuration
- files (or directories) with YAML instead using
- services.grafana.provision.datasources.path
- (or
- services.grafana.provision.dashboards.path.
- This is useful when having provisioning files from
- non-NixOS Grafana instances that you also want to
- deploy to NixOS.
-
-
- Note: secrets from
- these files will be leaked into the store unless you
- use a
- file-provider
- or env-var for secrets!
-
-
-
-
- services.grafana.provision.notifiers
- is not affected by this change because this feature is
- deprecated by Grafana and will probably be removed in
- Grafana 10. It’s recommended to use
- services.grafana.provision.alerting.contactPoints
- instead.
-
-
-
-
-
-
-
-
- The services.grafana.provision.alerting
- option was added. It includes suboptions for every
- alerting-related objects (with the exception of
- notifiers), which means it’s now possible
- to configure modern Grafana alerting declaratively.
-
-
-
-
- Synapse now requires entries in the
- state_group_edges table to be unique, in
- order to prevent accidentally introducing duplicate
- information (for example, because a database backup was
- restored multiple times). If your Synapse database already has
- duplicate rows in this table, this could fail with an error
- and require manual remediation.
-
-
-
-
- The diamond package has been update from
- 0.8.36 to 2.0.15. See the
- upstream
- release notes for more details.
-
-
-
-
- The guake package has been updated from
- 3.6.3 to 3.9.0, see the
- changelog
- for more details.
-
-
-
-
- The netlify-cli package has been updated
- from 6.13.2 to 12.2.4, see the
- changelog
- for more details.
-
-
-
-
- dockerTools.buildImage’s
- contents parameter has been deprecated in
- favor of copyToRoot. Use
- copyToRoot = buildEnv { ... }; or similar
- if you intend to add packages to /bin.
-
-
-
-
- The proxmox.qemuConf.bios option was added,
- it corresponds to Hardware->BIOS field
- in Proxmox web interface. Use
- "ovmf" value to build UEFI image,
- default value remains "bios". New
- option proxmox.partitionTableType defaults
- to either "legacy" or
- "efi", depending on the
- bios value. Setting
- partitionTableType to
- "hybrid" results in an image,
- which supports both methods
- ("bios" and
- "ovmf"), thereby remaining
- bootable after change to Proxmox
- Hardware->BIOS field.
-
-
-
-
- memtest86+ was updated from 5.00-coreboot-002 to 6.00-beta2.
- It is now the upstream version from https://www.memtest.org/,
- as coreboot’s fork is no longer available.
-
-
-
-
- Option descriptions, examples, and defaults writing in DocBook
- are now deprecated. Using CommonMark is preferred and will
- become the default in a future release.
-
-
-
-
- The
- documentation.nixos.options.allowDocBook
- option was added to ease the transition to CommonMark option
- documentation. Setting this option to false
- causes an error for every option included in the manual that
- uses DocBook documentation; it defaults to
- true to preserve the previous behavior and
- will be removed once the transition to CommonMark is complete.
-
-
-
-
- The Redis module now persists each instance’s configuration
- file in the state directory, in order to support some more
- advanced use cases like Sentinel.
-
-
-
-
- protonup has been aliased to and replaced
- by protonup-ng due to upstream not
- maintaining it.
-
-
-
-
- The udisks2 service, available at
- services.udisks2.enable, is now disabled by
- default. It will automatically be enabled through services and
- desktop environments as needed. This also means that polkit
- will now actually be disabled by default. The default for
- security.polkit.enable was already flipped
- in the previous release, but udisks2 being enabled by default
- re-enabled it.
-
-
-
-
- Nextcloud has been updated to version
- 25. Additionally the
- following things have changed for Nextcloud in NixOS:
-
-
-
-
- For Nextcloud >=24,
- the default PHP version is 8.1.
-
-
-
-
- Nextcloud 23 has been
- removed since it will reach its
- end
- of life in December 2022.
-
-
-
-
- If system.stateVersion is
- >=22.11, Nextcloud
- 25 will be installed by default. For older versions,
- Nextcloud 24 will be installed.
-
-
-
-
- Please ensure that you only upgrade one major release at a
- time! Nextcloud doesn’t support upgrades across multiple
- versions, i.e. an upgrade from
- 23 to
- 25 is only possible
- when upgrading to 24
- first.
-
-
-
-
-
-
- systemd-oomd is enabled by default. Depending on which systemd
- units have ManagedOOMSwap=kill or
- ManagedOOMMemoryPressure=kill, systemd-oomd
- will SIGKILL all the processes under the appropriate
- descendant cgroups when the configured limits are exceeded.
- NixOS does currently not configure cgroups with oomd by
- default, this can be enabled using
- systemd.oomd.enableRootSlice,
- systemd.oomd.enableSystemSlice,
- and
- systemd.oomd.enableUserServices.
-
-
-
-
- The tt-rss service performs two database
- migrations when you first use its web UI after upgrade.
- Consider backing up its database before updating.
-
-
-
-
- The pass-secret-service package now
- includes systemd units from upstream, so adding it to the
- NixOS services.dbus.packages option will
- make it start automatically as a systemd user service when an
- application tries to talk to the libsecret D-Bus API.
-
-
-
-
- The Wordpress module now has support for installing language
- packs through a new option,
- services.wordpress.sites.<site>.languages.
-
-
-
-
- The default package for
- services.mullvad-vpn.package was changed to
- pkgs.mullvad, allowing cross-platform usage
- of Mullvad. pkgs.mullvad only contains the
- Mullvad CLI tool, so users who rely on the Mullvad GUI will
- want to change it back to pkgs.mullvad-vpn,
- or add pkgs.mullvad-vpn to their
- environment.
-
-
-
-
- PowerDNS has been updated from v4.6.2 to v4.7.2. Please be
- sure to review the
- Upgrade
- Notes provided by upstream before upgrading. Worth
- specifically noting is that the new Catalog Zones feature
- comes with a mandatory schema change for the GSQL database
- backends, which has to be manually applied.
-
-
-
-
- There is a new module for the thunar
- program (the Xfce file manager), which depends on the
- xfconf dbus service, and also has a dbus
- service and a systemd unit. The option
- services.xserver.desktopManager.xfce.thunarPlugins
- has been renamed to
- programs.thunar.plugins, and may be removed
- in a future release.
-
-
-
-
- There is a new module for xfconf (the Xfce
- configuration storage system), which has a dbus service.
-
-
-
-
- The Mastodon package has been upgraded to v4.0.0. See the
- v4.0.0
- release notes for a list of changes. On standard
- setups, no manual migration steps are required. Nevertheless,
- a database backup is recommended.
-
-
-
-
- The nomad package now defaults to v1.3,
- which no longer has a downgrade path to v1.2 or older.
-
-
-
-
- The nodePackages package set now defaults
- to the LTS release in the nodejs package
- again, instead of being pinned to
- nodejs-14_x. Several updates to node2nix
- have been made for compatibility with newer Node.js and npm
- versions and a new postRebuild hook has
- been added for packages to perform extra build steps before
- the npm install step prunes dev dependencies.
-
-
-
-
- boot.kernel.sysctl is defined as a
- freeformType and adds a custom merge option for
- net.core.rmem_max (taking the highest value
- defined to avoid conflicts between 2 services trying to set
- that value).
-
-
-
-
- The mame package does not ship with its
- tools anymore in the default output. They were moved to a
- separate tools output instead. For
- convenience, mame-tools package was added
- for those who want to use it.
-
-
-
-
- A NixOS module for Firefox has been added which allows
- preferences and
- policies
- to be set. This also allows extensions to be installed via the
- ExtensionSettings policy. The new options
- are under programs.firefox.
-
-
-
-
- The option
- services.picom.experimentalBackends was
- removed since it is now the default and the option will cause
- picom to quit instead.
-
-
-
-
- haskellPackages.callHackage is not always
- invalidated if all-cabal-hashes changes,
- leading to less rebuilds of haskell dependencies.
-
-
-
-
- haskellPackages.callHackage and
- haskellPackages.callCabal2nix (and related
- functions) no longer keep a reference to the
- cabal2nix call used to generate them. As a
- result, they will be garbage collected more often.
-
-
-
-
-
- New Services
-
-
-
- alps,
- a simple and extensible webmail. Available as
- services.alps.
-
-
-
-
- appvm,
- Nix based app VMs. Available as
- virtualisation.appvm.
-
-
-
-
- AusweisApp2,
- the authentication software for the German ID card. Available
- as
- programs.ausweisapp.
-
-
-
-
- automatic-timezoned.
- a Linux daemon to automatically update the system timezone
- based on location. Available as
- services.automatic-timezoned.
-
-
-
-
- Dolibarr,
- an enterprise resource planning and customer relationship
- manager. Enable using
- services.dolibarr.
-
-
-
-
- dragonflydb,
- a modern replacement for Redis and Memcached. Available as
- services.dragonflydb.
-
-
-
-
- endlessh-go,
- an SSH tarpit that exposes Prometheus metrics. Available as
- services.endlessh-go.
-
-
-
-
- endlessh,
- an SSH tarpit. Available as
- services.endlessh.
-
-
-
-
- EVCC is an EV charge
- controller with PV integration. It supports a multitude of
- chargers, meters, vehicle APIs and more and ties that together
- with a well-tested backend and a lightweight web frontend.
- Available as
- services.evcc.
-
-
-
-
- expressvpn,
- the CLI client for ExpressVPN. Available as
- services.expressvpn.
-
-
-
-
- FreshRSS, a
- free, self-hostable RSS feed aggregator. Available as
- services.freshrss.
-
-
-
-
- Garage,
- a simple object storage server for geodistributed deployments,
- alternative to MinIO. Available as
- services.garage.
-
-
-
-
- go-autoconfig,
- IMAP/SMTP autodiscover server. Available as
- services.go-autoconfig.
-
-
-
-
- Grafana
- Tempo, a distributed tracing store. Available as
- services.tempo.
-
-
-
-
- HBase
- cluster, a distributed, scalable, big data store.
- Available as
- services.hadoop.hbase.
-
-
-
-
- infnoise,
- a hardware True Random Number Generator dongle. Available as
- services.infnoise.
-
-
-
-
- kanata,
- a tool to improve keyboard comfort and usability with advanced
- customization. Available as
- services.kanata.
-
-
-
-
- karma,
- an alert dashboard for Prometheus Alertmanager. Available as
- services.karma
-
-
-
-
- Komga, a free and
- open source comics/mangas media server. Available as
- services.komga.
-
-
-
-
- kthxbye,
- an alert acknowledgement management daemon for Prometheus
- Alertmanager. Available as
- services.kthxbye
-
-
-
-
- languagetool,
- a multilingual grammar, style, and spell checker. Available as
- services.languagetool.
-
-
-
-
- Listmonk, a
- self-hosted newsletter manager. Enable using
- services.listmonk.
-
-
-
-
- Mepo, a
- fast, simple, hackable OSM map viewer for mobile and desktop
- Linux. Available as
- programs.mepo.enable.
-
-
-
-
- merecat,
- a small and easy HTTP server based on thttpd. Available as
- services.merecat
-
-
-
-
- netbird, a zero
- configuration VPN. Available as
- services.netbird.
-
-
-
-
- ntfy.sh, a push
- notification service. Available as
- services.ntfy-sh
-
-
-
-
- OpenRGB,
- a FOSS tool for controlling RGB lighting. Available as
- services.hardware.openrgb.enable.
-
-
-
-
- Outline,
- a wiki and knowledge base similar to Notion. Available as
- services.outline.
-
-
-
-
- Patroni,
- a template for PostgreSQL HA with ZooKeeper, etcd or Consul.
- Available as
- services.patroni.
-
-
-
-
- persistent-evdev,
- a daemon to add virtual proxy devices that mirror a physical
- input device but persist even if the underlying hardware is
- hot-plugged. Available as
- services.persistent-evdev.
-
-
-
-
- Please,
- a Sudo clone written in Rust. Available as
- security.please.
-
-
-
-
- Prometheus
- IPMI exporter, an IPMI exporter for Prometheus.
- Available as
- services.prometheus.exporters.ipmi.
-
-
-
-
- Sachet,
- an SMS alerting tool for the Prometheus Alertmanager.
- Available as
- services.prometheus.sachet.
-
-
-
-
- schleuder, a
- mailing list manager with PGP support. Enable using
- services.schleuder.
-
-
-
-
- syncstorage-rs,
- a self-hostable sync server for Firefox. Available as
- services.firefox-syncserver.
-
-
-
-
- Tandoor Recipes,
- a self-hosted multi-tenant recipe collection. Available as
- services.tandoor-recipes.
-
-
-
-
- TAYGA,
- an out-of-kernel stateless NAT64 implementation. Available as
- services.tayga.
-
-
-
-
- tmate-ssh-server,
- server side part of
- tmate. Available
- as
- services.tmate-ssh-server.
-
-
-
-
- Uptime
- Kuma, a fancy self-hosted monitoring tool. Available as
- services.uptime-kuma.
-
-
-
-
- WriteFreely,
- a simple blogging platform with ActivityPub support. Available
- as
- services.writefreely.
-
-
-
-
- xray,
- a fully compatible v2ray-core replacement. Features XTLS,
- which when enabled on server and client, brings UDP FullCone
- NAT to proxy setups. Available as
- services.xray.
-
-
-
-
-
diff --git a/nixos/doc/manual/from_md/release-notes/rl-2305.section.xml b/nixos/doc/manual/from_md/release-notes/rl-2305.section.xml
deleted file mode 100644
index b6f941e69921..000000000000
--- a/nixos/doc/manual/from_md/release-notes/rl-2305.section.xml
+++ /dev/null
@@ -1,1044 +0,0 @@
-
- Release 23.05 (“Stoat”, 2023.05/??)
-
- Support is planned until the end of December 2023, handing over to
- 23.11.
-
-
- Highlights
-
- In addition to numerous new and upgraded packages, this release
- has the following highlights:
-
-
-
-
- Cinnamon has been updated to 5.6, see
- the
- pull request for what is changed.
-
-
-
-
- nixos-rebuild now supports an extra
- --specialisation option that can be used to
- change specialisation for switch and
- test commands.
-
-
-
-
-
- New Services
-
-
-
- Akkoma, an
- ActivityPub microblogging server. Available as
- services.akkoma.
-
-
-
-
- blesh,
- a line editor written in pure bash. Available as
- programs.bash.blesh.
-
-
-
-
- webhook,
- a lightweight webhook server. Available as
- services.webhook.
-
-
-
-
- cups-pdf-to-pdf,
- a pdf-generating cups backend based on
- cups-pdf.
- Available as
- services.printing.cups-pdf.
-
-
-
-
- Cloudlog,
- a web-based Amateur Radio logging application. Available as
- services.cloudlog.
-
-
-
-
- fzf,
- a command line fuzzyfinder. Available as
- programs.fzf.
-
-
-
-
- gmediarender,
- a simple, headless UPnP/DLNA renderer. Available as
- services.gmediarender.
-
-
-
-
- stevenblack-blocklist,
- A unified hosts file with base extensions for blocking
- unwanted websites. Available as
- networking.stevenblack.
-
-
-
-
- goeland,
- an alternative to rss2email written in golang with many
- filters. Available as
- services.goeland.
-
-
-
-
- atuin,
- a sync server for shell history. Available as
- services.atuin.
-
-
-
-
- mmsd,
- a lower level daemon that transmits and recieves MMSes.
- Available as
- services.mmsd.
-
-
-
-
- QDMR, a
- GUI application and command line tool for programming DMR
- radios
- programs.qdmr
-
-
-
-
- v2rayA, a Linux
- web GUI client of Project V which supports V2Ray, Xray, SS,
- SSR, Trojan and Pingtunnel. Available as
- services.v2raya.
-
-
-
-
- ulogd,
- a userspace logging daemon for netfilter/iptables related
- logging. Available as
- services.ulogd.
-
-
-
-
- photoprism,
- a AI-Powered Photos App for the Decentralized Web. Available
- as
- services.photoprism.
-
-
-
-
- autosuspend,
- a python daemon that suspends a system if certain conditions
- are met, or not met.
-
-
-
-
- sharing,
- a command-line tool to share directories and files from the
- CLI to iOS and Android devices without the need of an extra
- client app. Available as
- programs.sharing.
-
-
-
-
-
- Backward Incompatibilities
-
-
-
- carnix and cratesIO has
- been removed due to being unmaintained, use alternatives such
- as
- naersk
- and
- crate2nix
- instead.
-
-
-
-
- checkInputs have been renamed to
- nativeCheckInputs, because they behave the
- same as nativeBuildInputs when
- doCheck is set.
- checkInputs now denote a new type of
- dependencies, added to buildInputs when
- doCheck is set. As a rule of thumb,
- nativeCheckInputs are tools on
- $PATH used during the tests, and
- checkInputs are libraries which are linked
- to executables built as part of the tests. Similarly,
- installCheckInputs are renamed to
- nativeInstallCheckInputs, corresponding to
- nativeBuildInputs, and
- installCheckInputs are a new type of
- dependencies added to buildInputs when
- doInstallCheck is set. (Note that this
- change will not cause breakage to derivations with
- strictDeps unset, which are most packages
- except python, rust, ocaml and go packages).
-
-
-
-
- buildDunePackage now defaults to
- strictDeps = true which means that any
- library should go into buildInputs or
- checkInputs. Any executable that is run on
- the building machine should go into
- nativeBuildInputs or
- nativeCheckInputs respectively. Example of
- executables are ocaml,
- findlib and menhir. PPXs
- are libraries which are built by dune and should therefore not
- go into nativeBuildInputs.
-
-
-
-
- borgbackup module now has an option for
- inhibiting system sleep while backups are running, defaulting
- to off (not inhibiting sleep), available as
- services.borgbackup.jobs.<name>.inhibitsSleep.
-
-
-
-
- podman now uses the
- netavark network stack. Users will need to
- delete all of their local containers, images, volumes, etc, by
- running podman system reset --force once
- before upgrading their systems.
-
-
-
-
- git-bug has been updated to at least
- version 0.8.0, which includes backwards incompatible changes.
- The git-bug-migration package can be used
- to upgrade existing repositories.
-
-
-
-
- The services.kubo.settings option is now no
- longer stateful. If you changed any of the options in
- services.kubo.settings in the past and then
- removed them from your NixOS configuration again, those
- changes are still in your Kubo configuration file but will now
- be reset to the default. If you’re unsure, you may want to
- make a backup of your configuration file (probably
- /var/lib/ipfs/config) and compare after the update.
-
-
-
-
- The EC2 image module no longer fetches instance metadata in
- stage-1. This results in a significantly smaller initramfs,
- since network drivers no longer need to be included, and
- faster boots, since metadata fetching can happen in parallel
- with startup of other services. This breaks services which
- rely on metadata being present by the time stage-2 is entered.
- Anything which reads EC2 metadata from
- /etc/ec2-metadata should now have an
- after dependency on
- fetch-ec2-metadata.service
-
-
-
-
- minio removed support for its legacy
- filesystem backend in
- RELEASE.2022-10-29T06-21-33Z.
- This means if your storage was created with the old format,
- minio will no longer start. Unfortunately minio doesn’t
- provide a an automatic migration, they only provide
- instructions
- how to manually convert the node. To facilitate this
- migration we keep around the last version that still supports
- the old filesystem backend as
- minio_legacy_fs. Use it via
- services.minio.package = minio_legacy_fs;
- to export your data before switching to the new version. See
- the corresponding
- issue
- for more details.
-
-
-
-
- services.sourcehut.dispatch and the
- corresponding package
- (sourcehut.dispatchsrht) have been removed
- due to
- upstream
- deprecation.
-
-
-
-
- The
- services.snapserver.openFirewall
- module option default value has been changed from
- true to false. You will
- need to explicitly set this option to true,
- or configure your firewall.
-
-
-
-
- The
- services.tmate-ssh-server.openFirewall
- module option default value has been changed from
- true to false. You will
- need to explicitly set this option to true,
- or configure your firewall.
-
-
-
-
- The
- services.unifi-video.openFirewall
- module option default value has been changed from
- true to false. You will
- need to explicitly set this option to true,
- or configure your firewall.
-
-
-
-
- Kime has been updated from 2.5.6 to 3.0.2 and the
- i18n.inputMethod.kime.config option has
- been removed. Users should use
- daemonModules,
- iconColor, and
- extraConfig options under
- i18n.inputMethod.kime instead.
-
-
-
-
- tut has been updated from 1.0.34 to 2.0.0,
- and now uses the TOML format for the configuration file
- instead of INI. Additional information can be found
- here.
-
-
-
-
- The wordpress derivation no longer contains
- any builtin plugins or themes. If you need them you have to
- add them back to prevent your site from breaking. You can find
- them in wordpressPackages.{plugins,themes}.
-
-
-
-
- llvmPackages_rocm.llvm will not contain
- clang or compiler-rt.
- llvmPackages_rocm.clang will not contain
- llvm.
- llvmPackages_rocm.clangNoCompilerRt has
- been removed in favor of using
- llvmPackages_rocm.clang-unwrapped.
-
-
-
-
- The EC2 image module previously detected and automatically
- mounted ext3-formatted instance store devices and partitions
- in stage-1 (initramfs), storing /tmp on the
- first discovered device. This behaviour, which only catered to
- very specific use cases and could not be disabled, has been
- removed. Users relying on this should provide their own
- implementation, and probably use ext4 and perform the mount in
- stage-2.
-
-
-
-
- teleport has been upgraded to major version
- 11. Please see upstream
- upgrade
- instructions and
- release
- notes.
-
-
-
-
- The EC2 image module previously detected and activated
- swap-formatted instance store devices and partitions in
- stage-1 (initramfs). This behaviour has been removed. Users
- relying on this should provide their own implementation.
-
-
-
-
- Calling makeSetupHook without passing a
- name argument is deprecated.
-
-
-
-
- Qt 5.12 and 5.14 have been removed, as the corresponding
- branches have been EOL upstream for a long time. This affected
- under 10 packages in nixpkgs, largely unmaintained upstream as
- well, however, out-of-tree package expressions may need to be
- updated manually.
-
-
-
-
- The
- services.wordpress.sites.<name>.plugins
- and
- services.wordpress.sites.<name>.themes
- options have been converted from sets to attribute sets to
- allow for consumers to specify explicit install paths via
- attribute name.
-
-
-
-
- Nebula now runs as a system user and group created for each
- nebula network, using the CAP_NET_ADMIN
- ambient capability on launch rather than starting as root.
- Ensure that any files each Nebula instance needs to access are
- owned by the correct user and group, by default
- nebula-${networkName}.
-
-
-
-
- In mastodon it is now necessary to specify
- location of file with PostgreSQL database
- password. In
- services.mastodon.database.passwordFile
- parameter default value
- /var/lib/mastodon/secrets/db-password has
- been changed to null.
-
-
-
-
- The --target-host and
- --build-host options of
- nixos-rebuild no longer treat the
- localhost value specially – to build
- on/deploy to local machine, omit the relevant flag.
-
-
-
-
- The nix.readOnlyStore option has been
- renamed to boot.readOnlyNixStore to clarify
- that it configures the NixOS boot process, not the Nix daemon.
-
-
-
-
- Deprecated xlibsWrapper transitional
- package has been removed in favour of direct use of its
- constitutents: xorg.libX11,
- freetype and others.
-
-
-
-
- .NET 5.0 was removed due to being end-of-life, use a newer,
- supported .NET version -
- https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core
-
-
-
-
- The iputils package, which is installed by default, no longer
- provides the ninfod,
- rarpd and rdisc tools.
- See
- upstream’s
- release notes for more details and available
- replacements.
-
-
-
-
-
- Other Notable Changes
-
-
-
- vim_configurable has been renamed to
- vim-full to avoid confusion:
- vim-full’s build-time features are
- configurable, but both vim and
- vim-full are
- customizable (in the sense of user
- configuration, like vimrc).
-
-
-
-
- The module for the application firewall
- opensnitch got the ability to configure
- rules. Available as
- services.opensnitch.rules
-
-
-
-
- The module usbmuxd now has the ability to
- change the package used by the daemon. In case you’re
- experiencing issues with usbmuxd you can
- try an alternative program like usbmuxd2.
- Available as
- services.usbmuxd.package
-
-
-
-
- A few openssh options have been moved from extraConfig to the
- new freeform option settings and renamed as
- follows:
-
-
-
-
- services.openssh.forwardX11 to
- services.openssh.settings.X11Forwarding
-
-
-
-
- services.openssh.kbdInteractiveAuthentication
- ->
- services.openssh.settings.KbdInteractiveAuthentication
-
-
-
-
- services.openssh.passwordAuthentication
- to
- services.openssh.settings.PasswordAuthentication
-
-
-
-
- services.openssh.useDns to
- services.openssh.settings.UseDns
-
-
-
-
- services.openssh.permitRootLogin to
- services.openssh.settings.PermitRootLogin
-
-
-
-
- services.openssh.logLevel to
- services.openssh.settings.LogLevel
-
-
-
-
- services.openssh.kexAlgorithms to
- services.openssh.settings.KexAlgorithms
-
-
-
-
- services.openssh.macs to
- services.openssh.settings.Macs
-
-
-
-
- services.openssh.ciphers to
- services.openssh.settings.Ciphers
-
-
-
-
- services.openssh.gatewayPorts to
- services.openssh.settings.GatewayPorts
-
-
-
-
-
-
- services.mastodon gained a tootctl wrapped
- named mastodon-tootctl similar to
- nextcloud-occ which can be executed from
- any user and switches to the configured mastodon user with
- sudo and sources the environment variables.
-
-
-
-
- DocBook option documentation, which has been deprecated since
- 22.11, will now cause a warning when documentation is built.
- Out-of-tree modules should migrate to using CommonMark
- documentation as outlined in
- to silence this
- warning.
-
-
- DocBook option documentation support will be removed in the
- next release and CommonMark will become the default. DocBook
- option documentation that has not been migrated until then
- will no longer render properly or cause errors.
-
-
-
-
- NixOS now defaults to using nsncd (a non-caching
- reimplementation in Rust) as NSS lookup dispatcher, instead of
- the buggy and deprecated glibc-provided nscd. If you need to
- switch back, set
- services.nscd.enableNsncd = false, but
- please open an issue in nixpkgs so your issue can be fixed.
-
-
-
-
- The dnsmasq service now takes configuration
- via the services.dnsmasq.settings attribute
- set. The option
- services.dnsmasq.extraConfig will be
- deprecated when NixOS 22.11 reaches end of life.
-
-
-
-
- The dokuwiki service now takes
- configuration via the
- services.dokuwiki.sites.<name>.settings
- attribute set, extraConfig is deprecated
- and will be removed. The
- {aclUse,superUser,disableActions}
- attributes have been renamed, pluginsConfig
- now also accepts an attribute set of booleans, passing plain
- PHP is deprecated. Same applies to acl
- which now also accepts structured settings.
-
-
-
-
- The wordpress service now takes
- configuration via the
- services.wordpress.sites.<name>.settings
- attribute set, extraConfig is still
- available to append additional text to
- wp-config.php.
-
-
-
-
- To reduce closure size in
- nixos/modules/profiles/minimal.nix profile
- disabled installation documentations and manuals. Also
- disabled logrotate and
- udisks2 services.
-
-
-
-
- The minimal ISO image now uses the
- nixos/modules/profiles/minimal.nix profile.
-
-
-
-
- The ghcWithPackages and
- ghcWithHoogle wrappers will now also
- symlink GHC’s and all included libraries’ documentation to
- $out/share/doc for convenience. If
- undesired, the old behavior can be restored by overriding the
- builders with
- { installDocumentation = false; }.
-
-
-
-
- mastodon now supports connection to a
- remote PostgreSQL database.
-
-
-
-
- services.peertube now requires you to
- specify the secret file
- secrets.secretsFile. It can be generated by
- running openssl rand -hex 32. Before
- upgrading, read the release notes for PeerTube:
-
-
-
-
- Release
- v5.0.0
-
-
-
-
- And backup your data.
-
-
-
-
- services.chronyd is now started with
- additional systemd sandbox/hardening options for better
- security.
-
-
-
-
- services.dhcpcd service now don’t solicit
- or accept IPv6 Router Advertisements on interfaces that use
- static IPv6 addresses.
-
-
-
-
- The module services.headscale was
- refactored to be compliant with
- RFC
- 0042. To be precise, this means that the following
- things have changed:
-
-
-
-
- Most settings has been migrated under
- services.headscale.settings
- which is an attribute-set that will be converted into
- headscale’s YAML config format. This means that the
- configuration from
- headscale’s
- example configuration can be directly written as
- attribute-set in Nix within this option.
-
-
-
-
-
-
- nixos/lib/make-disk-image.nix can now
- mutate EFI variables, run user-provided EFI firmware or
- variable templates. This is now extensively documented in the
- NixOS manual.
-
-
-
-
- services.grafana listens only on localhost
- by default again. This was changed to upstreams default of
- 0.0.0.0 by accident in the freeform setting
- conversion.
-
-
-
-
- Grafana Tempo has been updated to version 2.0. See the
- upstream
- upgrade guide for migration instructions.
-
-
-
-
- A new virtualisation.rosetta module was
- added to allow running x86_64 binaries
- through
- Rosetta
- inside virtualised NixOS guests on Apple silicon. This feature
- works by default with the
- UTM
- virtualisation
- package.
-
-
-
-
- The new option users.motdFile allows
- configuring a Message Of The Day that can be updated
- dynamically.
-
-
-
-
- The root package is now built with the
- "-Dgnuinstall=ON" CMake flag,
- making the output conform the bin
- libshare layout. In
- this layout, tutorials is under
- share/doc/ROOT/; cmake,
- font, icons,
- js and macro under
- share/root;
- Makefile.comp and
- Makefile.config under
- etc/root.
-
-
-
-
- Enabling global redirect in
- services.nginx.virtualHosts now allows one
- to add exceptions with the locations
- option.
-
-
-
-
- A new option recommendedBrotliSettings has
- been added to services.nginx. Learn more
- about compression in Brotli format
- here.
-
-
-
-
- Updated recommended settings in
- services.nginx.recommendedGzipSettings:
-
-
-
-
- Enables gzip compression for only certain proxied
- requests.
-
-
-
-
- Allow checking and loading of precompressed files.
-
-
-
-
- Updated gzip mime-types.
-
-
-
-
- Increased the minimum length of a response that will be
- gzipped.
-
-
-
-
-
-
- Garage
- version is based on
- system.stateVersion,
- existing installations will keep using version 0.7. New
- installations will use version 0.8. In order to upgrade a
- Garage cluster, please follow
- upstream
- instructions and force
- services.garage.package
- or upgrade accordingly
- system.stateVersion.
-
-
-
-
- Nebula now supports the
- services.nebula.networks.<name>.isRelay
- and
- services.nebula.networks.<name>.relays
- configuration options for setting up or allowing traffic
- relaying. See the
- announcement
- for more details about relays.
-
-
-
-
- hip has been separated into
- hip, hip-common and
- hipcc.
-
-
-
-
- services.nginx.recommendedProxySettings now
- removes the Connection header preventing
- clients from closing backend connections.
-
-
-
-
- Resilio sync secret keys can now be provided using a secrets
- file at runtime, preventing these secrets from ending up in
- the Nix store.
-
-
-
-
- The firewall and nat
- module now has a nftables based implementation. Enable
- networking.nftables to use it.
-
-
-
-
- The services.fwupd module now allows
- arbitrary daemon settings to be configured in a structured
- manner
- (services.fwupd.daemonSettings).
-
-
-
-
- services.xserver.desktopManager.plasma5.phononBackend
- now defaults to vlc according to
- upstrean
- recommendation
-
-
-
-
- The zramSwap is now implemented with
- zram-generator, and the option
- zramSwap.numDevices for using ZRAM devices
- as general purpose ephemeral block devices has been removed.
-
-
-
-
- As Singularity has renamed to
- Apptainer
- to distinguish from
- an
- un-renamed fork by Sylabs Inc., there are now two
- packages of Singularity/Apptainer:
-
-
-
-
- apptainer: From
- github.com/apptainer/apptainer, which
- is the new repo after renaming.
-
-
-
-
- singularity: From
- github.com/sylabs/singularity, which is
- the fork by Sylabs Inc..
-
-
-
-
- programs.singularity got a new
- package option to specify which package to
- use.
-
-
- singularity-tools.buildImage got a new
- input argument singularity to specify which
- package to use.
-
-
-
-
- The new option
- programs.singularity.enableFakeroot, if set
- to true, provides
- --fakeroot support for
- apptainer and
- singularity.
-
-
-
-
- The unifi-poller package and corresponding
- NixOS module have been renamed to unpoller
- to match upstream.
-
-
-
-
- The new option
- services.tailscale.useRoutingFeatures
- controls various settings for using Tailscale features like
- exit nodes and subnet routers. If you wish to use your machine
- as an exit node, you can set this setting to
- server, otherwise if you wish to use an
- exit node you can set this setting to
- client. The strict RPF warning has been
- removed as the RPF will be loosened automatically based on the
- value of this setting.
-
-
-
-
- openjdk from version 11 and above is not
- build with openjfx (i.e.: JavaFX) support
- by default anymore. You can re-enable it by overriding, e.g.:
- openjdk11.override { enableJavaFX = true; };.
-
-
-
-
- Xastir
- can now access AX.25 interfaces via the
- libax25 package.
-
-
-
-
- tvbrowser-bin was removed, and now
- tvbrowser is built from source.
-
-
-
-
- nixos-version now accepts
- --configuration-revision to display more
- information about the current generation revision
-
-
-
-
- The option
- services.nomad.extraSettingsPlugins has
- been fixed to allow more than one plugin in the path.
-
-
-
-
- The option
- services.prometheus.exporters.pihole.interval
- does not exist anymore and has been removed.
-
-
-
-
-
diff --git a/nixos/doc/manual/installation/installing.chapter.md b/nixos/doc/manual/installation/installing.chapter.md
index ac7cf5a7bfc5..e1908017a7e4 100644
--- a/nixos/doc/manual/installation/installing.chapter.md
+++ b/nixos/doc/manual/installation/installing.chapter.md
@@ -15,16 +15,16 @@ To begin the installation, you have to boot your computer from the install drive
::: {.note}
The key to open the boot menu is different across computer brands and even
- models. It can be F12, but also F1,
- F9, F10, Enter, Del,
- Esc or another function key. If you are unsure and don't see
+ models. It can be [F12]{.keycap}, but also [F1]{.keycap},
+ [F9]{.keycap}, [F10]{.keycap}, [Enter]{.keycap}, [Del]{.keycap},
+ [Esc]{.keycap} or another function key. If you are unsure and don't see
it on the early boot screen, you can search online for your computers
brand, model followed by "boot from usb".
The computer might not even have that feature, so you have to go into the
BIOS/UEFI settings to change the boot order. Again, search online for
details about your specific computer model.
- For Apple computers with Intel processors press and hold the ⌥
+ For Apple computers with Intel processors press and hold the [⌥]{.keycap}
(Option or Alt) key until you see the boot menu. On Apple silicon press
and hold the power button.
:::
@@ -41,7 +41,7 @@ To begin the installation, you have to boot your computer from the install drive
3. Shortly after selecting the appropriate boot drive, you should be
presented with a menu with different installer options. Leave the default
- and wait (or press Enter to speed up).
+ and wait (or press [Enter]{.keycap} to speed up).
4. The graphical images will start their corresponding desktop environment
and the graphical installer, which can take some time. The minimal images
@@ -421,7 +421,7 @@ Use the following commands:
specify on which disk the GRUB boot loader is to be installed.
Without it, NixOS cannot boot.
- : If there are other operating systems running on the machine before
+ If there are other operating systems running on the machine before
installing NixOS, the [](#opt-boot.loader.grub.useOSProber)
option can be set to `true` to automatically add them to the grub
menu.
@@ -438,10 +438,10 @@ Use the following commands:
[`boot.loader.systemd-boot`](#opt-boot.loader.systemd-boot.enable)
as well.
- : If you want to use GRUB, set [](#opt-boot.loader.grub.device) to `nodev` and
+ If you want to use GRUB, set [](#opt-boot.loader.grub.device) to `nodev` and
[](#opt-boot.loader.grub.efiSupport) to `true`.
- : With system-boot, you should not need any special configuration to detect
+ With system-boot, you should not need any special configuration to detect
other installed systems. With GRUB, set [](#opt-boot.loader.grub.useOSProber)
to `true`, but this will only detect windows partitions, not other linux
distributions. If you dual boot another linux distribution, use system-boot
@@ -538,9 +538,7 @@ drive (here `/dev/sda`). [Example: NixOS Configuration](#ex-config) shows a
corresponding configuration Nix expression.
::: {#ex-partition-scheme-MBR .example}
-::: {.title}
**Example: Example partition schemes for NixOS on `/dev/sda` (MBR)**
-:::
```ShellSession
# parted /dev/sda -- mklabel msdos
# parted /dev/sda -- mkpart primary 1MB -8GB
@@ -549,9 +547,7 @@ corresponding configuration Nix expression.
:::
::: {#ex-partition-scheme-UEFI .example}
-::: {.title}
**Example: Example partition schemes for NixOS on `/dev/sda` (UEFI)**
-:::
```ShellSession
# parted /dev/sda -- mklabel gpt
# parted /dev/sda -- mkpart primary 512MB -8GB
@@ -562,9 +558,8 @@ corresponding configuration Nix expression.
:::
::: {#ex-install-sequence .example}
-::: {.title}
**Example: Commands for Installing NixOS on `/dev/sda`**
-:::
+
With a partitioned disk.
```ShellSession
@@ -583,9 +578,7 @@ With a partitioned disk.
:::
::: {#ex-config .example}
-::: {.title}
**Example: NixOS Configuration**
-:::
```ShellSession
{ config, pkgs, ... }: {
imports = [
diff --git a/nixos/doc/manual/manual.xml b/nixos/doc/manual/manual.xml
index 158b3507a58e..4440f8e04baa 100644
--- a/nixos/doc/manual/manual.xml
+++ b/nixos/doc/manual/manual.xml
@@ -12,13 +12,12 @@
-
+ Configuration Options
-
diff --git a/nixos/doc/manual/md-to-db.sh b/nixos/doc/manual/md-to-db.sh
deleted file mode 100755
index 4698e94f508b..000000000000
--- a/nixos/doc/manual/md-to-db.sh
+++ /dev/null
@@ -1,52 +0,0 @@
-#! /usr/bin/env nix-shell
-#! nix-shell -I nixpkgs=https://github.com/NixOS/nixpkgs/tarball/22.11 -i bash -p pandoc
-
-# This script is temporarily needed while we transition the manual to
-# CommonMark. It converts the .md files in the regular manual folder
-# into DocBook files in the from_md folder.
-
-DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
-pushd "$DIR"
-
-link_manpages_filter=$(nix-build --no-out-link "$DIR/../../../doc/build-aux/pandoc-filters/link-manpages.nix")
-
-# NOTE: Keep in sync with Nixpkgs manual (/doc/Makefile).
-# TODO: Remove raw-attribute when we can get rid of DocBook altogether.
-pandoc_commonmark_enabled_extensions=+attributes+fenced_divs+footnotes+bracketed_spans+definition_lists+pipe_tables+raw_attribute
-pandoc_flags=(
- # Not needed:
- # - diagram-generator.lua (we do not support that in NixOS manual to limit dependencies)
- # - media extraction (was only required for diagram generator)
- # - docbook-reader/citerefentry-to-rst-role.lua (only relevant for DocBook → MarkDown/rST/MyST)
- "--lua-filter=$DIR/../../../doc/build-aux/pandoc-filters/myst-reader/roles.lua"
- "--lua-filter=$link_manpages_filter"
- "--lua-filter=$DIR/../../../doc/build-aux/pandoc-filters/docbook-writer/rst-roles.lua"
- "--lua-filter=$DIR/../../../doc/build-aux/pandoc-filters/docbook-writer/html-elements.lua"
- "--lua-filter=$DIR/../../../doc/build-aux/pandoc-filters/docbook-writer/labelless-link-is-xref.lua"
- -f "commonmark${pandoc_commonmark_enabled_extensions}+smart"
- -t docbook
-)
-
-OUT="$DIR/from_md"
-mapfile -t MD_FILES < <(find . -type f -regex '.*\.md$')
-
-for mf in ${MD_FILES[*]}; do
- if [ "${mf: -11}" == ".section.md" ]; then
- mkdir -p "$(dirname "$OUT/$mf")"
- OUTFILE="$OUT/${mf%".section.md"}.section.xml"
- pandoc "$mf" "${pandoc_flags[@]}" \
- -o "$OUTFILE"
- grep -q -m 1 "xi:include" "$OUTFILE" && sed -i 's|xmlns:xlink="http://www.w3.org/1999/xlink"| xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude"|' "$OUTFILE"
- fi
-
- if [ "${mf: -11}" == ".chapter.md" ]; then
- mkdir -p "$(dirname "$OUT/$mf")"
- OUTFILE="$OUT/${mf%".chapter.md"}.chapter.xml"
- pandoc "$mf" "${pandoc_flags[@]}" \
- --top-level-division=chapter \
- -o "$OUTFILE"
- grep -q -m 1 "xi:include" "$OUTFILE" && sed -i 's|xmlns:xlink="http://www.w3.org/1999/xlink"| xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude"|' "$OUTFILE"
- fi
-done
-
-popd
diff --git a/nixos/modules/services/misc/nitter.nix b/nixos/modules/services/misc/nitter.nix
index f0cb5cc15138..2d0d91f95985 100644
--- a/nixos/modules/services/misc/nitter.nix
+++ b/nixos/modules/services/misc/nitter.nix
@@ -185,6 +185,13 @@ in
description = lib.mdDoc "Replace YouTube links with links to this instance (blank to disable).";
};
+ replaceReddit = mkOption {
+ type = types.str;
+ default = "";
+ example = "teddit.net";
+ description = lib.mdDoc "Replace Reddit links with links to this instance (blank to disable).";
+ };
+
replaceInstagram = mkOption {
type = types.str;
default = "";
diff --git a/pkgs/applications/editors/emacs/generic.nix b/pkgs/applications/editors/emacs/generic.nix
index feed7ba5b41e..499da2a8f93e 100644
--- a/pkgs/applications/editors/emacs/generic.nix
+++ b/pkgs/applications/editors/emacs/generic.nix
@@ -60,7 +60,7 @@ assert withPgtk -> withGTK3 && !withX && gtk3 != null;
assert withXwidgets -> withGTK3 && webkitgtk != null;
-let emacs = (if withMacport then llvmPackages_6.stdenv else stdenv).mkDerivation (lib.optionalAttrs nativeComp {
+(if withMacport then llvmPackages_6.stdenv else stdenv).mkDerivation (finalAttrs: (lib.optionalAttrs nativeComp {
NATIVE_FULL_AOT = "1";
LIBRARY_PATH = "${lib.getLib stdenv.cc.libc}/lib";
} // {
@@ -69,7 +69,7 @@ let emacs = (if withMacport then llvmPackages_6.stdenv else stdenv).mkDerivation
patches = patches fetchpatch ++ lib.optionals nativeComp [
(substituteAll {
- src = if lib.versionOlder version "29"
+ src = if lib.versionOlder finalAttrs.version "29"
then ./native-comp-driver-options-28.patch
else ./native-comp-driver-options.patch;
backendPath = (lib.concatStringsSep " "
@@ -241,7 +241,7 @@ let emacs = (if withMacport then llvmPackages_6.stdenv else stdenv).mkDerivation
passthru = {
inherit nativeComp;
- pkgs = recurseIntoAttrs (emacsPackagesFor emacs);
+ pkgs = recurseIntoAttrs (emacsPackagesFor finalAttrs.finalPackage);
tests = { inherit (nixosTests) emacs-daemon; };
};
@@ -269,5 +269,4 @@ let emacs = (if withMacport then llvmPackages_6.stdenv else stdenv).mkDerivation
separately.
'';
};
-});
-in emacs
+}))
diff --git a/pkgs/applications/misc/cubiomes-viewer/default.nix b/pkgs/applications/misc/cubiomes-viewer/default.nix
index f6035b3c6c49..1405bc5b90ca 100644
--- a/pkgs/applications/misc/cubiomes-viewer/default.nix
+++ b/pkgs/applications/misc/cubiomes-viewer/default.nix
@@ -9,13 +9,13 @@
stdenv.mkDerivation rec {
pname = "cubiomes-viewer";
- version = "3.1.0";
+ version = "3.1.1";
src = fetchFromGitHub {
owner = "Cubitect";
repo = pname;
rev = version;
- sha256 = "sha256-pA+SWktSjgH7lRqK14yJX2ziLoKpxMCpEIh0H6slpxw=";
+ sha256 = "sha256-5PtMXipULnzAnarESu2biYOeHSlDeKXoX5XnlpvgIAk=";
fetchSubmodules = true;
};
diff --git a/pkgs/applications/misc/logseq/default.nix b/pkgs/applications/misc/logseq/default.nix
index 9a9db9d70f94..f0ed6a07e53c 100644
--- a/pkgs/applications/misc/logseq/default.nix
+++ b/pkgs/applications/misc/logseq/default.nix
@@ -9,11 +9,11 @@
stdenv.mkDerivation rec {
pname = "logseq";
- version = "0.8.16";
+ version = "0.8.17";
src = fetchurl {
url = "https://github.com/logseq/logseq/releases/download/${version}/logseq-linux-x64-${version}.AppImage";
- sha256 = "sha256-0tIDoNQoqSn1nYm+YdgzXh34aH1e5N8wl9lqGbQoOeU=";
+ hash = "sha256-z7v59wXvSIDC7f4IMT8bblPgn+3+J54XqIPzXqWDses=";
name = "${pname}-${version}.AppImage";
};
diff --git a/pkgs/applications/networking/instant-messengers/slack/default.nix b/pkgs/applications/networking/instant-messengers/slack/default.nix
index 7bd88eaa7545..0f2ef4d586ff 100644
--- a/pkgs/applications/networking/instant-messengers/slack/default.nix
+++ b/pkgs/applications/networking/instant-messengers/slack/default.nix
@@ -177,7 +177,8 @@ let
# Fix the desktop link
substituteInPlace $out/share/applications/slack.desktop \
--replace /usr/bin/ $out/bin/ \
- --replace /usr/share/ $out/share/
+ --replace /usr/share/ $out/share/ \
+ --replace bin/slack "bin/slack -s"
runHook postInstall
'';
diff --git a/pkgs/applications/networking/n8n/node-packages.nix b/pkgs/applications/networking/n8n/node-packages.nix
index 34a86c314000..4512f48a6c86 100644
--- a/pkgs/applications/networking/n8n/node-packages.nix
+++ b/pkgs/applications/networking/n8n/node-packages.nix
@@ -310,13 +310,13 @@ let
sha512 = "u3JgK9AwfNpyGwRhtzIVxVfH9yOK5ZNswmaN6W+XFuUXzW9o8CGgnSBEcaUgZ0hdLvHQHyM+3+22HKgbItki/w==";
};
};
- "@codemirror/language-6.4.0" = {
+ "@codemirror/language-6.5.0" = {
name = "_at_codemirror_slash_language";
packageName = "@codemirror/language";
- version = "6.4.0";
+ version = "6.5.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@codemirror/language/-/language-6.4.0.tgz";
- sha512 = "Wzb7GnNj8vnEtbPWiOy9H0m1fBtE28kepQNGLXekU2EEZv43BF865VKITUn+NoV8OpW6gRtvm29YEhqm46927Q==";
+ url = "https://registry.npmjs.org/@codemirror/language/-/language-6.5.0.tgz";
+ sha512 = "dI+dV/u2klIt0Y9kE3TH9vuBidAB3xuuDPofwzvnW8ZKqJnKTbT3EjyV7DeKcmrRgXMhlPTL7AdH1V5KOCYuHQ==";
};
};
"@codemirror/lint-6.1.0" = {
@@ -337,13 +337,13 @@ let
sha512 = "69QXtcrsc3RYtOtd+GsvczJ319udtBf1PTrr2KbLWM/e2CXUPnh0Nz9AUo8WfhSQ7GeL8dPVNUmhQVgpmuaNGA==";
};
};
- "@codemirror/view-6.7.3" = {
+ "@codemirror/view-6.8.1" = {
name = "_at_codemirror_slash_view";
packageName = "@codemirror/view";
- version = "6.7.3";
+ version = "6.8.1";
src = fetchurl {
- url = "https://registry.npmjs.org/@codemirror/view/-/view-6.7.3.tgz";
- sha512 = "Lt+4POnhXrZFfHOdPzXEHxrzwdy7cjqYlMkOWvoFGi6/bAsjzlFfr0NY3B15B/PGx+cDFgM1hlc12wvYeZbGLw==";
+ url = "https://registry.npmjs.org/@codemirror/view/-/view-6.8.1.tgz";
+ sha512 = "bXWs42i1mnBexaktPABaEpYbt4FbJMnlesObDLF0GE8poRiNaRgm7H/2NfXfD5Swas1ULdFgONLLs4ncwHuz8g==";
};
};
"@colors/colors-1.5.0" = {
@@ -418,13 +418,13 @@ let
sha512 = "CA3MAZBTxVsF6SkfkHXDerkhcQs0QPofy43eFdbWJJkZiq3SfiaH1msOkac59rQaqto5EqWnASboY1dBuKen5w==";
};
};
- "@fortawesome/fontawesome-common-types-6.2.1" = {
+ "@fortawesome/fontawesome-common-types-6.3.0" = {
name = "_at_fortawesome_slash_fontawesome-common-types";
packageName = "@fortawesome/fontawesome-common-types";
- version = "6.2.1";
+ version = "6.3.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@fortawesome/fontawesome-common-types/-/fontawesome-common-types-6.2.1.tgz";
- sha512 = "Sz07mnQrTekFWLz5BMjOzHl/+NooTdW8F8kDQxjWwbpOJcnoSg4vUDng8d/WR1wOxM0O+CY9Zw0nR054riNYtQ==";
+ url = "https://registry.npmjs.org/@fortawesome/fontawesome-common-types/-/fontawesome-common-types-6.3.0.tgz";
+ sha512 = "4BC1NMoacEBzSXRwKjZ/X/gmnbp/HU5Qqat7E8xqorUtBFZS+bwfGH5/wqOC2K6GV0rgEobp3OjGRMa5fK9pFg==";
};
};
"@fortawesome/fontawesome-svg-core-1.3.0" = {
@@ -436,13 +436,13 @@ let
sha512 = "UIL6crBWhjTNQcONt96ExjUnKt1D68foe3xjEensLDclqQ6YagwCRYVQdrp/hW0ALRp/5Fv/VKw+MqTUWYYvPg==";
};
};
- "@fortawesome/free-regular-svg-icons-6.2.1" = {
+ "@fortawesome/free-regular-svg-icons-6.3.0" = {
name = "_at_fortawesome_slash_free-regular-svg-icons";
packageName = "@fortawesome/free-regular-svg-icons";
- version = "6.2.1";
+ version = "6.3.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@fortawesome/free-regular-svg-icons/-/free-regular-svg-icons-6.2.1.tgz";
- sha512 = "wiqcNDNom75x+pe88FclpKz7aOSqS2lOivZeicMV5KRwOAeypxEYWAK/0v+7r+LrEY30+qzh8r2XDaEHvoLsMA==";
+ url = "https://registry.npmjs.org/@fortawesome/free-regular-svg-icons/-/free-regular-svg-icons-6.3.0.tgz";
+ sha512 = "cZnwiVHZ51SVzWHOaNCIA+u9wevZjCuAGSvSYpNlm6A4H4Vhwh8481Bf/5rwheIC3fFKlgXxLKaw8Xeroz8Ntg==";
};
};
"@fortawesome/free-solid-svg-icons-5.15.4" = {
@@ -1030,49 +1030,49 @@ let
sha512 = "gW69MEamZ4wk1OsOq1nG1jcyhXIQcnrsX5JwixVw/9xaiav8TCyjESAruu1Rz9yyInhgBXxkNwMeygKnN2uxNA==";
};
};
- "@sentry/core-7.36.0" = {
+ "@sentry/core-7.37.0" = {
name = "_at_sentry_slash_core";
packageName = "@sentry/core";
- version = "7.36.0";
+ version = "7.37.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@sentry/core/-/core-7.36.0.tgz";
- sha512 = "lq1MlcMhvm7QIwUOknFeufkg4M6QREY3s61y6pm1o+o3vSqB7Hz0D19xlyEpP62qMn8OyuttVKOVK1UfGc2EyQ==";
+ url = "https://registry.npmjs.org/@sentry/core/-/core-7.37.0.tgz";
+ sha512 = "2M6aZKIG/1HgfE0hobQ9tKSo6ZsyBrSQqjtQhMVFwVzZJyFw3m1AqcrB+f0myi+1ay2MMPbJ+HhYtBPR3e4EvA==";
};
};
- "@sentry/integrations-7.36.0" = {
+ "@sentry/integrations-7.37.0" = {
name = "_at_sentry_slash_integrations";
packageName = "@sentry/integrations";
- version = "7.36.0";
+ version = "7.37.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@sentry/integrations/-/integrations-7.36.0.tgz";
- sha512 = "wrRoUqdeGi64NNimGVk8U8DBiXamxTYPBux0/faFDyau8EJyQFcv8zOyB78Za4W2Ss3ZXNaE/WtFF8UxalHzBQ==";
+ url = "https://registry.npmjs.org/@sentry/integrations/-/integrations-7.37.0.tgz";
+ sha512 = "8kMHK/QrulSfzV7mubZp+UmP1gOYGkrCfNaf9LkRDs4j1X9Y07Wyoa6C5h7ENDkXM/nk6NmVFDmHMYTT/zvndA==";
};
};
- "@sentry/node-7.36.0" = {
+ "@sentry/node-7.37.0" = {
name = "_at_sentry_slash_node";
packageName = "@sentry/node";
- version = "7.36.0";
+ version = "7.37.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@sentry/node/-/node-7.36.0.tgz";
- sha512 = "nAHAY+Rbn5OlTpNX/i6wYrmw3hT/BtwPZ/vNU52cKgw7CpeE1UrCeFjnPn18rQPB7lIh7x0vNvoaPrfemRzpSQ==";
+ url = "https://registry.npmjs.org/@sentry/node/-/node-7.37.0.tgz";
+ sha512 = "ohkk5K7V3+lK1MtVVpTzqu09xcGNu9IeGK2VjjMD68deojdYrxWXINuO4ta0aE1hmg1rwAlpPebQkmXspo9zOw==";
};
};
- "@sentry/types-7.36.0" = {
+ "@sentry/types-7.37.0" = {
name = "_at_sentry_slash_types";
packageName = "@sentry/types";
- version = "7.36.0";
+ version = "7.37.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@sentry/types/-/types-7.36.0.tgz";
- sha512 = "uvfwUn3okAWSZ948D/xqBrkc3Sn6TeHUgi3+p/dTTNGAXXskzavgfgQ4rSW7f3YD4LL+boZojpoIARVLodMGuA==";
+ url = "https://registry.npmjs.org/@sentry/types/-/types-7.37.0.tgz";
+ sha512 = "p8iw5oGvWLIk7osMgXhxshUpebJD0riiuT3ihBP0DV+Gs8r0qdQ5gtcStl7Cn0D4013p4j/f3T5q85Z9ENE6fA==";
};
};
- "@sentry/utils-7.36.0" = {
+ "@sentry/utils-7.37.0" = {
name = "_at_sentry_slash_utils";
packageName = "@sentry/utils";
- version = "7.36.0";
+ version = "7.37.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@sentry/utils/-/utils-7.36.0.tgz";
- sha512 = "mgDi5X5Bm0sydCzXpnyKD/sD98yc2qnKXyRdNX4HRRwruhC/P53LT0hGhZXsyqsB/l8OAMl0zWXJLg0xONQsEw==";
+ url = "https://registry.npmjs.org/@sentry/utils/-/utils-7.37.0.tgz";
+ sha512 = "CN86EKQ07+SgqfgGehMJsgrCEjc0sl1YDcj2xf9dA0Bn3ma2MTDkCyutxVcRfc2IVWfqAN1rn/L8/BH2v2+eqA==";
};
};
"@servie/events-1.0.0" = {
@@ -1093,22 +1093,22 @@ let
sha512 = "Uy0+khmZqUrUGm5dmMqVlnvufZRSK0FbYzVgp0UMstm+F5+W2/jnEEQyc9vo1ZR/E5ZI/B1WjjoTqBqwJL6Krw==";
};
};
- "@swc/core-1.3.32" = {
+ "@swc/core-1.3.35" = {
name = "_at_swc_slash_core";
packageName = "@swc/core";
- version = "1.3.32";
+ version = "1.3.35";
src = fetchurl {
- url = "https://registry.npmjs.org/@swc/core/-/core-1.3.32.tgz";
- sha512 = "Yx/n1j+uUkcqlJAW8IRg8Qymgkdow6NHJZPFShiR0YiaYq2sXY+JHmvh16O6GkL91Y+gTlDUS7uVgDz50czJUQ==";
+ url = "https://registry.npmjs.org/@swc/core/-/core-1.3.35.tgz";
+ sha512 = "KmiBin0XSVzJhzX19zTiCqmLslZ40Cl7zqskJcTDeIrRhfgKdiAsxzYUanJgMJIRjYtl9Kcg1V/Ip2o2wL8v3w==";
};
};
- "@swc/wasm-1.3.32" = {
+ "@swc/wasm-1.3.35" = {
name = "_at_swc_slash_wasm";
packageName = "@swc/wasm";
- version = "1.3.32";
+ version = "1.3.35";
src = fetchurl {
- url = "https://registry.npmjs.org/@swc/wasm/-/wasm-1.3.32.tgz";
- sha512 = "u27gmXtbe/y4M5fo38NCBKUFeFIWRCmppABxPvM9TsZ8KhO4EdZOI1L9sPHSZvVyAXRpnwC8cjYej/zOAZjAQA==";
+ url = "https://registry.npmjs.org/@swc/wasm/-/wasm-1.3.35.tgz";
+ sha512 = "8xBOgl9eziAuqF4HYwYx4Kh6eHfOQECvO0ZMlrFNW0jgE+ntqxcRjBhuzZ6iWb24nifzXbuGLQntbns4IJYJgQ==";
};
};
"@techteamer/ocsp-1.0.0" = {
@@ -1336,13 +1336,13 @@ let
sha512 = "/SNsDidUFCvqqcWDwxv2feww/yqhNeTRL5CVoL3jU4Goc4kKEL10T7Eye65ZqPNi4HRx8sAEX59pV1aEH7drNA==";
};
};
- "@types/node-18.11.19" = {
+ "@types/node-18.13.0" = {
name = "_at_types_slash_node";
packageName = "@types/node";
- version = "18.11.19";
+ version = "18.13.0";
src = fetchurl {
- url = "https://registry.npmjs.org/@types/node/-/node-18.11.19.tgz";
- sha512 = "YUgMWAQBWLObABqrvx8qKO1enAvBUdjZOAWQ5grBAkp5LQv45jBvYKZ3oFS9iKRCQyFjqw6iuEa1vmFqtxYLZw==";
+ url = "https://registry.npmjs.org/@types/node/-/node-18.13.0.tgz";
+ sha512 = "gC3TazRzGoOnoKAhUx+Q0t8S9Tzs74z7m0ipwGpSqQrleP14hKxP4/JUeEQcD3W1/aIpnWl8pHowI7WokuZpXg==";
};
};
"@types/node-fetch-2.6.2" = {
@@ -1417,6 +1417,15 @@ let
sha512 = "7axfYN8SW9pWg78NgenHasSproWQee5rzyPVLC9HpaQSDgNArsnKJD88EaMfi4Pl48AyciO3agYCFqpHS1gLpg==";
};
};
+ "@types/triple-beam-1.3.2" = {
+ name = "_at_types_slash_triple-beam";
+ packageName = "@types/triple-beam";
+ version = "1.3.2";
+ src = fetchurl {
+ url = "https://registry.npmjs.org/@types/triple-beam/-/triple-beam-1.3.2.tgz";
+ sha512 = "txGIh+0eDFzKGC25zORnswy+br1Ha7hj5cMVwKIU7+s0U2AxxJru/jZSMU6OC9MJWP6+pc/hc6ZjyZShpsyY2g==";
+ };
+ };
"@types/tunnel-0.0.3" = {
name = "_at_types_slash_tunnel";
packageName = "@types/tunnel";
@@ -1966,13 +1975,13 @@ let
sha512 = "9cYNccliXZDByFsFliVwk5GvTq058Fj513CiR4E60ndDwmuXzTJEp/Bp8FyuRmGyYupLjHLs+JA9/CBoVS4/NQ==";
};
};
- "aws-sdk-2.1310.0" = {
+ "aws-sdk-2.1312.0" = {
name = "aws-sdk";
packageName = "aws-sdk";
- version = "2.1310.0";
+ version = "2.1312.0";
src = fetchurl {
- url = "https://registry.npmjs.org/aws-sdk/-/aws-sdk-2.1310.0.tgz";
- sha512 = "D0m9uFUa1UVXWTe4GSyNJP4+6DXwboE2FEG/URkLoo4r9Q8LHxwNFCGkBhaoEwssREyRe2LOYS1Nag/6WyvC6Q==";
+ url = "https://registry.npmjs.org/aws-sdk/-/aws-sdk-2.1312.0.tgz";
+ sha512 = "NG6ERxxxU6p+CDWrq7wLinp0siKRcCNN98iY0qr/2WKZbz5JCtDyiQV/l+6jLmNKP5qIT5z++jnDy9cgNP6ICQ==";
};
};
"aws-sign2-0.7.0" = {
@@ -2380,13 +2389,13 @@ let
sha512 = "MOqV1dKLy1YQgP9m3lFolyMxaU+1+o4afzYYf0H4wNM+x/S0I1QPQfkgGlLiH00EyFrvSmeubeCYFP47rTfpjg==";
};
};
- "bull-4.10.3" = {
+ "bull-4.10.4" = {
name = "bull";
packageName = "bull";
- version = "4.10.3";
+ version = "4.10.4";
src = fetchurl {
- url = "https://registry.npmjs.org/bull/-/bull-4.10.3.tgz";
- sha512 = "pp403srpkn9tYi7Z3Mu0sozehZ7rEEFGNJnN+nLxQwml6MySzefC9bPeCYedZoCkXdZ6VbIB8uNkMZg+hN/dAg==";
+ url = "https://registry.npmjs.org/bull/-/bull-4.10.4.tgz";
+ sha512 = "o9m/7HjS/Or3vqRd59evBlWCXd9Lp+ALppKseoSKHaykK46SmRjAilX98PgmOz1yeVaurt8D5UtvEt4bUjM3eA==";
};
};
"busboy-1.6.0" = {
@@ -5224,13 +5233,13 @@ let
sha512 = "JG3eIAj5V9CwcGvuOmoo6LB9kbAYT8HXffUl6memuszlwDC/qvFAJw49XJ5NROSFNPxp3iQg1GqkFhaY/CR0IA==";
};
};
- "internal-slot-1.0.4" = {
+ "internal-slot-1.0.5" = {
name = "internal-slot";
packageName = "internal-slot";
- version = "1.0.4";
+ version = "1.0.5";
src = fetchurl {
- url = "https://registry.npmjs.org/internal-slot/-/internal-slot-1.0.4.tgz";
- sha512 = "tA8URYccNzMo94s5MQZgH8NB/XTa6HsOo0MLfXTKKEnHVVdegzaQoFZ7Jp44bdvLvY2waT5dc+j5ICEswhi7UQ==";
+ url = "https://registry.npmjs.org/internal-slot/-/internal-slot-1.0.5.tgz";
+ sha512 = "Y+R5hJrzs52QCG2laLn4udYVnxsfny9CpOhNhUvk/SSSVyF6T27FzRbF0sroPidSu3X8oEAkOn2K804mjpt6UQ==";
};
};
"interpret-1.4.0" = {
@@ -5764,13 +5773,13 @@ let
sha512 = "bZ5Sy3YzKo9Fyc8wH2iIQK4JImJ6R0GWI9kL1/k7Z91ZBNgkRXE6U0JfHIizZbort8ZunhSI3jw9I6253ahKfg==";
};
};
- "js-base64-3.7.4" = {
+ "js-base64-3.7.5" = {
name = "js-base64";
packageName = "js-base64";
- version = "3.7.4";
+ version = "3.7.5";
src = fetchurl {
- url = "https://registry.npmjs.org/js-base64/-/js-base64-3.7.4.tgz";
- sha512 = "wpM/wi20Tl+3ifTyi0RdDckS4YTD4Lf953mBRrpG8547T7hInHNPEj8+ck4gB8VDcGyeAWFK++Wb/fU1BeavKQ==";
+ url = "https://registry.npmjs.org/js-base64/-/js-base64-3.7.5.tgz";
+ sha512 = "3MEt5DTINKqfScXKfJFrRbxkrnk2AxPWGBL/ycjz4dK8iqiSJ06UxD8jh8xuh6p10TX4t2+7FsBYVxxQbMg+qA==";
};
};
"js-md4-0.3.2" = {
@@ -6466,13 +6475,13 @@ let
sha512 = "A9SzX4hMKWS25MyalwcOnNoplyHbkNVsjidhTp8ru0Sj23wY9GWBKS8gAIGDSAqeWjIjvE4KBEl24XXAs+v4wQ==";
};
};
- "logform-2.5.0" = {
+ "logform-2.5.1" = {
name = "logform";
packageName = "logform";
- version = "2.5.0";
+ version = "2.5.1";
src = fetchurl {
- url = "https://registry.npmjs.org/logform/-/logform-2.5.0.tgz";
- sha512 = "fsFiH2yjSCTmzotZ5JmEo0brQyJ7iHrc8pQ5pnHg6e1e5WfkqdNMDvgRWSfz+aCr3Y2YxYzHA4UKj+6QoctKrg==";
+ url = "https://registry.npmjs.org/logform/-/logform-2.5.1.tgz";
+ sha512 = "9FyqAm9o9NKKfiAKfZoYo9bGXXuwMkxQiQttkT4YjjVtQVIQtK6LmVtlxmCaFswo6N4AfEkHqZTV0taDtPotNg==";
};
};
"long-4.0.0" = {
@@ -6547,13 +6556,13 @@ let
sha512 = "ysxwsnTKdAx96aTRdhDOCQfDgbHnt8SK0KY8SEjO0wHinhWOFTESbjVCMPbU1uGXg/ch4lifqx0wfjOawU2+WA==";
};
};
- "lru-memoizer-2.1.4" = {
+ "lru-memoizer-2.2.0" = {
name = "lru-memoizer";
packageName = "lru-memoizer";
- version = "2.1.4";
+ version = "2.2.0";
src = fetchurl {
- url = "https://registry.npmjs.org/lru-memoizer/-/lru-memoizer-2.1.4.tgz";
- sha512 = "IXAq50s4qwrOBrXJklY+KhgZF+5y98PDaNo0gi/v2KQBFLyWr+JyFvijZXkGKjQj/h9c0OwoE+JZbwUXce76hQ==";
+ url = "https://registry.npmjs.org/lru-memoizer/-/lru-memoizer-2.2.0.tgz";
+ sha512 = "QfOZ6jNkxCcM/BkIPnFsqDhtrazLRsghi9mBwFAzol5GCvj4EkFT899Za3+QwikCg5sRX8JstioBDwOxEyzaNw==";
};
};
"lru_map-0.3.3" = {
@@ -6853,13 +6862,13 @@ let
sha512 = "lKwV/1brpG6mBUFHtb7NUmtABCb2WZZmm2wNiOA5hAb8VdCS4B3dtMWyvcoViccwAW/COERjXLt0zP1zXUN26g==";
};
};
- "minimist-1.2.7" = {
+ "minimist-1.2.8" = {
name = "minimist";
packageName = "minimist";
- version = "1.2.7";
+ version = "1.2.8";
src = fetchurl {
- url = "https://registry.npmjs.org/minimist/-/minimist-1.2.7.tgz";
- sha512 = "bzfL1YUZsP41gmu/qjrEk0Q6i2ix/cVeAhbCbqH9u3zYutS1cLg00qhrD0M2MVdCcx4Sc0UpP2eBWo9rotpq6g==";
+ url = "https://registry.npmjs.org/minimist/-/minimist-1.2.8.tgz";
+ sha512 = "2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==";
};
};
"minipass-3.3.6" = {
@@ -6871,13 +6880,13 @@ let
sha512 = "DxiNidxSEK+tHG6zOIklvNOwm3hvCrbUrdtzY74U6HKTJxvIDfOUL5W5P2Ghd3DTkhhKPYGqeNUIh5qcM4YBfw==";
};
};
- "minipass-4.0.2" = {
+ "minipass-4.0.3" = {
name = "minipass";
packageName = "minipass";
- version = "4.0.2";
+ version = "4.0.3";
src = fetchurl {
- url = "https://registry.npmjs.org/minipass/-/minipass-4.0.2.tgz";
- sha512 = "4Hbzei7ZyBp+1aw0874YWpKOubZd/jc53/XU+gkYry1QV+VvrbO8icLM5CUtm4F0hyXn85DXYKEMIS26gitD3A==";
+ url = "https://registry.npmjs.org/minipass/-/minipass-4.0.3.tgz";
+ sha512 = "OW2r4sQ0sI+z5ckEt5c1Tri4xTgZwYDxpE54eqWlQloQRoWtXjqt9udJ5Z4dSv7wK+nfFI7FRXyCpBSft+gpFw==";
};
};
"minipass-collect-1.0.2" = {
@@ -7006,13 +7015,13 @@ let
sha512 = "Psm+g3/wHXhjBEktkxXsFMZvd3nemI0r3IPsE0bU+4//PnvNWKkzhZcEsbPcYiWqe8XqXJJEg4Tgtr7Raw67Yw==";
};
};
- "mongodb-4.13.0" = {
+ "mongodb-4.14.0" = {
name = "mongodb";
packageName = "mongodb";
- version = "4.13.0";
+ version = "4.14.0";
src = fetchurl {
- url = "https://registry.npmjs.org/mongodb/-/mongodb-4.13.0.tgz";
- sha512 = "+taZ/bV8d1pYuHL4U+gSwkhmDrwkWbH1l4aah4YpmpscMwgFBkufIKxgP/G7m87/NUuQzc2Z75ZTI7ZOyqZLbw==";
+ url = "https://registry.npmjs.org/mongodb/-/mongodb-4.14.0.tgz";
+ sha512 = "coGKkWXIBczZPr284tYKFLg+KbGPPLlSbdgfKAb6QqCFt5bo5VFZ50O3FFzsw4rnkqjwT6D8Qcoo9nshYKM7Mg==";
};
};
"mongodb-connection-string-url-2.6.0" = {
@@ -7159,13 +7168,13 @@ let
sha512 = "Dd6SdWYDjlhgrpPbof4DFPP4hPdpH9cA+3YkFSCgQLNyCi0RdqiQJqPQ5xQFlNVaxd6a7R69RHy/oNwt6/+cLw==";
};
};
- "n8n-editor-ui-0.180.2" = {
+ "n8n-editor-ui-0.180.3" = {
name = "n8n-editor-ui";
packageName = "n8n-editor-ui";
- version = "0.180.2";
+ version = "0.180.3";
src = fetchurl {
- url = "https://registry.npmjs.org/n8n-editor-ui/-/n8n-editor-ui-0.180.2.tgz";
- sha512 = "5XIIDN6X2CbQtDFwthCOqanvkOgbbFu36h9LZb/eB8KdQKs5dxNFi958lIrKuyZaiPYBQTZCPZWMcqqie+9JIQ==";
+ url = "https://registry.npmjs.org/n8n-editor-ui/-/n8n-editor-ui-0.180.3.tgz";
+ sha512 = "1agrCzViXP7Q7wqdpOqHF/TEl5pE17cSROVdkGmZkTYAOVsxuB3nLZ29ifqUUM9evgiVsMSV7NG78juD5HYt+Q==";
};
};
"n8n-nodes-base-0.212.2" = {
@@ -7294,13 +7303,13 @@ let
sha512 = "fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==";
};
};
- "node-abi-3.32.0" = {
+ "node-abi-3.33.0" = {
name = "node-abi";
packageName = "node-abi";
- version = "3.32.0";
+ version = "3.33.0";
src = fetchurl {
- url = "https://registry.npmjs.org/node-abi/-/node-abi-3.32.0.tgz";
- sha512 = "HkwdiLzE/LeuOMIQq/dJq70oNyRc88+wt5CH/RXYseE00LkA/c4PkS6Ti1vE4OHYUiKjkwuxjWq9pItgrz8UJw==";
+ url = "https://registry.npmjs.org/node-abi/-/node-abi-3.33.0.tgz";
+ sha512 = "7GGVawqyHF4pfd0YFybhv/eM9JwTtPqx0mAanQ146O3FlSh3pA24zf9IRQTOsfTSqXTNzPSP5iagAJ94jjuVog==";
};
};
"node-abort-controller-2.0.0" = {
@@ -7672,13 +7681,13 @@ let
sha512 = "MVHddDVweXZF3awtlAS+6pgKLlm/JgxZ90+/NBurBoQctVOOB/zDdVjcyPzQ+0laDGbsWgrRkflI65sQeOgT9Q==";
};
};
- "open-8.4.0" = {
+ "open-8.4.1" = {
name = "open";
packageName = "open";
- version = "8.4.0";
+ version = "8.4.1";
src = fetchurl {
- url = "https://registry.npmjs.org/open/-/open-8.4.0.tgz";
- sha512 = "XgFPPM+B28FtCCgSb9I+s9szOC1vZRSwgWsRUA5ylIxRTgKozqjOCrVOqGsYABPYK5qnfqClxZTFBa8PKt2v6Q==";
+ url = "https://registry.npmjs.org/open/-/open-8.4.1.tgz";
+ sha512 = "/4b7qZNhv6Uhd7jjnREh1NjnPxlTq+XNWPG88Ydkj5AILcA5m3ajvcg57pB24EQjKv0dK62XnDqk9c/hkIG5Kg==";
};
};
"openapi-types-10.0.0" = {
@@ -8401,13 +8410,13 @@ let
sha512 = "ESF23V4SKG6lVSGZgYNpbsiaAkdab6ZgOxe52p7+Kid3W3u3bxR4Vfd/o21dmN7jSt0IwgZ4v5MUd26FEtXE9w==";
};
};
- "prettier-2.8.3" = {
+ "prettier-2.8.4" = {
name = "prettier";
packageName = "prettier";
- version = "2.8.3";
+ version = "2.8.4";
src = fetchurl {
- url = "https://registry.npmjs.org/prettier/-/prettier-2.8.3.tgz";
- sha512 = "tJ/oJ4amDihPoufT5sM0Z1SKEuKay8LfVAMlbbhnnkvt6BUserZylqo2PN+p9KeljLr0OHa2rXHU1T8reeoTrw==";
+ url = "https://registry.npmjs.org/prettier/-/prettier-2.8.4.tgz";
+ sha512 = "vIS4Rlc2FNh0BySk3Wkd6xmwxB0FpOndW5fisM5H8hsZSxU2VWVB5CWIkIjWvrHjIhxk2g3bfMKM87zNTrZddw==";
};
};
"pretty-bytes-5.6.0" = {
@@ -8545,13 +8554,13 @@ let
sha512 = "xL96WDdCZYdU7Slin569tFX712BxsxslWwAfAhCYjQKGTq7dAU91Lomy6nLLhh/dyGhk/YH4TwTSRxTzhuHyZg==";
};
};
- "protobufjs-7.2.1" = {
+ "protobufjs-7.2.2" = {
name = "protobufjs";
packageName = "protobufjs";
- version = "7.2.1";
+ version = "7.2.2";
src = fetchurl {
- url = "https://registry.npmjs.org/protobufjs/-/protobufjs-7.2.1.tgz";
- sha512 = "L3pCItypTnPK27+CS8nuhZMYtsY+i8dqdq2vZsYHlG17CnWp1DWPQ/sos0vOKrj1fHEAzo3GBqSHLaeZyKUCDA==";
+ url = "https://registry.npmjs.org/protobufjs/-/protobufjs-7.2.2.tgz";
+ sha512 = "++PrQIjrom+bFDPpfmqXfAGSQs40116JRrqqyf53dymUMvvb5d/LMRyicRoF1AUKoXVS1/IgJXlEgcpr4gTF3Q==";
};
};
"proxy-addr-2.0.7" = {
@@ -11359,10 +11368,10 @@ in
n8n = nodeEnv.buildNodePackage {
name = "n8n";
packageName = "n8n";
- version = "0.214.2";
+ version = "0.214.3";
src = fetchurl {
- url = "https://registry.npmjs.org/n8n/-/n8n-0.214.2.tgz";
- sha512 = "9KbRJMT8/f4+5kiCnqZbe+ETKdBnBb5VJtw7DUbtu3Uj327dtGlPeX2E/kgXwwonnkO6XgdOteJZDSiixxozbg==";
+ url = "https://registry.npmjs.org/n8n/-/n8n-0.214.3.tgz";
+ sha512 = "QI5MqWpGd+d8XUDL18DHiHDQXPGTer6b2fpwx1ZZiRhIgVBzLXTmrdsMHSRtuIcTXHmu2Q2bnU2Qdn2oYs4heA==";
};
dependencies = [
(sources."@acuminous/bitsyntax-0.1.2" // {
@@ -11431,7 +11440,7 @@ in
dependencies = [
sources."jwa-2.0.0"
sources."jws-4.0.0"
- sources."open-8.4.0"
+ sources."open-8.4.1"
sources."tslib-2.5.0"
];
})
@@ -11475,10 +11484,10 @@ in
sources."@codemirror/commands-6.2.0"
sources."@codemirror/lang-css-6.0.2"
sources."@codemirror/lang-javascript-6.1.3"
- sources."@codemirror/language-6.4.0"
+ sources."@codemirror/language-6.5.0"
sources."@codemirror/lint-6.1.0"
sources."@codemirror/state-6.2.0"
- sources."@codemirror/view-6.7.3"
+ sources."@codemirror/view-6.8.1"
sources."@colors/colors-1.5.0"
sources."@cspotcode/source-map-support-0.8.1"
sources."@curlconverter/yargs-0.0.2"
@@ -11487,9 +11496,9 @@ in
sources."@fontsource/open-sans-4.5.14"
sources."@fortawesome/fontawesome-common-types-0.3.0"
sources."@fortawesome/fontawesome-svg-core-1.3.0"
- (sources."@fortawesome/free-regular-svg-icons-6.2.1" // {
+ (sources."@fortawesome/free-regular-svg-icons-6.3.0" // {
dependencies = [
- sources."@fortawesome/fontawesome-common-types-6.2.1"
+ sources."@fortawesome/fontawesome-common-types-6.3.0"
];
})
(sources."@fortawesome/free-solid-svg-icons-5.15.4" // {
@@ -11518,7 +11527,7 @@ in
dependencies = [
sources."@grpc/proto-loader-0.7.4"
sources."long-5.2.1"
- sources."protobufjs-7.2.1"
+ sources."protobufjs-7.2.2"
sources."yargs-16.2.0"
];
})
@@ -11633,15 +11642,15 @@ in
sources."domhandler-5.0.3"
];
})
- sources."@sentry/core-7.36.0"
- sources."@sentry/integrations-7.36.0"
- sources."@sentry/node-7.36.0"
- sources."@sentry/types-7.36.0"
- sources."@sentry/utils-7.36.0"
+ sources."@sentry/core-7.37.0"
+ sources."@sentry/integrations-7.37.0"
+ sources."@sentry/node-7.37.0"
+ sources."@sentry/types-7.37.0"
+ sources."@sentry/utils-7.37.0"
sources."@servie/events-1.0.0"
sources."@sqltools/formatter-1.2.5"
- sources."@swc/core-1.3.32"
- sources."@swc/wasm-1.3.32"
+ sources."@swc/core-1.3.35"
+ sources."@swc/wasm-1.3.35"
sources."@techteamer/ocsp-1.0.0"
sources."@tediousjs/connection-string-0.3.0"
sources."@tokenizer/token-0.3.0"
@@ -11666,7 +11675,7 @@ in
sources."@types/long-4.0.2"
sources."@types/mime-3.0.1"
sources."@types/multer-1.4.7"
- sources."@types/node-18.11.19"
+ sources."@types/node-18.13.0"
(sources."@types/node-fetch-2.6.2" // {
dependencies = [
sources."form-data-3.0.1"
@@ -11679,6 +11688,7 @@ in
sources."@types/stack-trace-0.0.29"
sources."@types/stoppable-1.1.1"
sources."@types/tough-cookie-2.3.8"
+ sources."@types/triple-beam-1.3.2"
sources."@types/tunnel-0.0.3"
sources."@types/uuid-9.0.0"
sources."@types/validator-13.7.12"
@@ -11769,7 +11779,7 @@ in
})
sources."available-typed-arrays-1.0.5"
sources."avsc-5.7.7"
- (sources."aws-sdk-2.1310.0" // {
+ (sources."aws-sdk-2.1312.0" // {
dependencies = [
sources."buffer-4.9.2"
sources."events-1.1.1"
@@ -11834,7 +11844,7 @@ in
sources."buffer-more-ints-1.0.0"
sources."buffer-writer-2.0.0"
sources."bufferutil-4.0.7"
- (sources."bull-4.10.3" // {
+ (sources."bull-4.10.4" // {
dependencies = [
sources."cron-parser-4.7.1"
];
@@ -12275,7 +12285,7 @@ in
sources."inherits-2.0.4"
sources."ini-1.3.8"
sources."inquirer-7.3.3"
- sources."internal-slot-1.0.4"
+ sources."internal-slot-1.0.5"
sources."interpret-1.4.0"
(sources."ioredis-5.3.0" // {
dependencies = [
@@ -12335,7 +12345,7 @@ in
sources."jmespath-0.16.0"
sources."join-component-1.1.0"
sources."jquery-3.6.3"
- sources."js-base64-3.7.4"
+ sources."js-base64-3.7.5"
sources."js-md4-0.3.2"
sources."js-nacl-1.4.0"
sources."js-yaml-3.14.1"
@@ -12427,7 +12437,7 @@ in
sources."lodash.uniqby-4.7.0"
sources."lodash.unset-4.5.2"
sources."lodash.zipobject-4.1.3"
- sources."logform-2.5.0"
+ sources."logform-2.5.1"
sources."long-4.0.0"
sources."lossless-json-1.0.5"
(sources."lower-case-2.0.2" // {
@@ -12436,7 +12446,7 @@ in
];
})
sources."lru-cache-4.0.2"
- sources."lru-memoizer-2.1.4"
+ sources."lru-memoizer-2.2.0"
sources."lru_map-0.3.3"
sources."luxon-3.2.1"
(sources."mailparser-3.6.3" // {
@@ -12486,8 +12496,8 @@ in
sources."brace-expansion-1.1.11"
];
})
- sources."minimist-1.2.7"
- sources."minipass-4.0.2"
+ sources."minimist-1.2.8"
+ sources."minipass-4.0.3"
(sources."minipass-collect-1.0.2" // {
dependencies = [
sources."minipass-3.3.6"
@@ -12535,7 +12545,7 @@ in
sources."moment-2.29.4"
sources."moment-timezone-0.5.40"
sources."monaco-editor-0.33.0"
- sources."mongodb-4.13.0"
+ sources."mongodb-4.14.0"
(sources."mongodb-connection-string-url-2.6.0" // {
dependencies = [
sources."tr46-3.0.0"
@@ -12581,7 +12591,7 @@ in
sources."vue2-boring-avatars-0.3.8"
];
})
- sources."n8n-editor-ui-0.180.2"
+ sources."n8n-editor-ui-0.180.3"
(sources."n8n-nodes-base-0.212.2" // {
dependencies = [
sources."chokidar-3.5.2"
@@ -12608,7 +12618,7 @@ in
sources."tslib-2.5.0"
];
})
- sources."node-abi-3.32.0"
+ sources."node-abi-3.33.0"
sources."node-abort-controller-3.1.1"
sources."node-addon-api-4.3.0"
sources."node-ensure-0.0.0"
@@ -12780,7 +12790,7 @@ in
})
sources."prebuild-install-7.1.1"
sources."prelude-ls-1.1.2"
- sources."prettier-2.8.3"
+ sources."prettier-2.8.4"
sources."pretty-bytes-5.6.0"
sources."printj-1.1.2"
sources."prismjs-1.29.0"
diff --git a/pkgs/applications/science/biology/diamond/default.nix b/pkgs/applications/science/biology/diamond/default.nix
index 6cdae4cb53a2..bd878312d8de 100644
--- a/pkgs/applications/science/biology/diamond/default.nix
+++ b/pkgs/applications/science/biology/diamond/default.nix
@@ -2,13 +2,13 @@
stdenv.mkDerivation rec {
pname = "diamond";
- version = "2.1.0";
+ version = "2.1.1";
src = fetchFromGitHub {
owner = "bbuchfink";
repo = "diamond";
rev = "v${version}";
- sha256 = "sha256-tcUVWfb/EtJ6heJjQ3989uNjkWa6FocReJ5gjE35AMY=";
+ sha256 = "sha256-OT5Fi/rC3VmQ97SuqlXOTf8RAT0Zj4/Oy86T1v7hBkA=";
};
diff --git a/pkgs/applications/version-management/commitizen/default.nix b/pkgs/applications/version-management/commitizen/default.nix
index f7ba075114b7..f53c6fb153b4 100644
--- a/pkgs/applications/version-management/commitizen/default.nix
+++ b/pkgs/applications/version-management/commitizen/default.nix
@@ -26,14 +26,13 @@
buildPythonApplication rec {
pname = "commitizen";
- version = "2.39.1";
+ version = "2.41.0";
src = fetchFromGitHub {
owner = "commitizen-tools";
repo = pname;
rev = "v${version}";
- hash = "sha256-QQIYyg2zwV7cfFxGHVsLiTRBgTGs3O7OJcmURvfY3LQ=";
- deepClone = true;
+ hash = "sha256-dzAIRfUdyHSefDRDuPMsr8l2Dsiall2ZUDB6GufTbXE=";
};
format = "pyproject";
diff --git a/pkgs/development/compilers/circt/default.nix b/pkgs/development/compilers/circt/default.nix
index ce06782eb126..a8e36cbc785f 100644
--- a/pkgs/development/compilers/circt/default.nix
+++ b/pkgs/development/compilers/circt/default.nix
@@ -49,7 +49,8 @@ stdenv.mkDerivation rec {
# https://github.com/NixOS/nixpkgs/issues/214945 discusses this issue.
#
# As a temporary fix, we disabled these tests when using clang stdenv
- LIT_FILTER_OUT = lib.optionalString stdenv.cc.isClang "CIRCT :: Target/ExportSystemC/.*\.mlir";
+ # cannot use lib.optionalString as it creates an empty string, disabling all tests
+ LIT_FILTER_OUT = if stdenv.cc.isClang then "CIRCT :: Target/ExportSystemC/.*\.mlir" else null;
preConfigure = ''
substituteInPlace test/circt-reduce/test/annotation-remover.mlir --replace "/usr/bin/env" "${coreutils}/bin/env"
diff --git a/pkgs/development/compilers/hip/default.nix b/pkgs/development/compilers/hip/default.nix
index 610fffa03879..5aa423bbf84b 100644
--- a/pkgs/development/compilers/hip/default.nix
+++ b/pkgs/development/compilers/hip/default.nix
@@ -49,7 +49,7 @@ let
];
in stdenv.mkDerivation (finalAttrs: {
pname = "hip-${hipPlatform}";
- version = "5.4.2";
+ version = "5.4.3";
outputs = [
"out"
diff --git a/pkgs/development/interpreters/php/generic.nix b/pkgs/development/interpreters/php/generic.nix
index b8ceac621a61..74dedcfe2d18 100644
--- a/pkgs/development/interpreters/php/generic.nix
+++ b/pkgs/development/interpreters/php/generic.nix
@@ -333,6 +333,7 @@ let
description = "An HTML-embedded scripting language";
homepage = "https://www.php.net/";
license = licenses.php301;
+ mainProgram = "php";
maintainers = teams.php.members;
platforms = platforms.all;
outputsToInstall = [ "out" "dev" ];
diff --git a/pkgs/development/libraries/cglm/default.nix b/pkgs/development/libraries/cglm/default.nix
index d21c0243bf3d..578b4341e73e 100644
--- a/pkgs/development/libraries/cglm/default.nix
+++ b/pkgs/development/libraries/cglm/default.nix
@@ -6,13 +6,13 @@
stdenv.mkDerivation rec {
pname = "cglm";
- version = "0.8.8";
+ version = "0.8.9";
src = fetchFromGitHub {
owner = "recp";
repo = "cglm";
rev = "v${version}";
- sha256 = "sha256-BzZb8NDgf1NnkZaaxs+0YlVuYod/uiWJxA3geaYN7e0=";
+ sha256 = "sha256-e90N8bHFt3dOzppa4xkB7qra7/bHhAexTEYGXPFXS4s=";
};
nativeBuildInputs = [ cmake ];
diff --git a/pkgs/development/libraries/edencommon/default.nix b/pkgs/development/libraries/edencommon/default.nix
new file mode 100644
index 000000000000..bd61fb603f8b
--- /dev/null
+++ b/pkgs/development/libraries/edencommon/default.nix
@@ -0,0 +1,35 @@
+{ stdenv, lib, cmake, fetchFromGitHub, glog, folly, fmt_8, boost, gtest }:
+
+stdenv.mkDerivation rec {
+ pname = "edencommon";
+ version = "2023.01.30.00";
+
+ src = fetchFromGitHub {
+ owner = "facebookexperimental";
+ repo = "edencommon";
+ rev = "v${version}";
+ sha256 = "sha256-N3/Ey0zrfOfuAaS6qIpEgUUL5GkCZrqpAspJ7OprLPk=";
+ };
+
+ nativeBuildInputs = [ cmake ];
+
+ cmakeFlags = lib.optionals stdenv.isDarwin [
+ "-DCMAKE_OSX_DEPLOYMENT_TARGET=10.14" # For aligned allocation
+ ];
+
+ buildInputs = [
+ glog
+ folly
+ fmt_8
+ boost
+ gtest
+ ];
+
+ meta = with lib; {
+ description = "A shared library for Meta's source control filesystem tools (EdenFS and Watchman)";
+ homepage = "https://github.com/facebookexperimental/edencommon";
+ license = licenses.mit;
+ platforms = platforms.unix;
+ maintainers = with maintainers; [ kylesferrazza ];
+ };
+}
diff --git a/pkgs/development/libraries/fb303/default.nix b/pkgs/development/libraries/fb303/default.nix
new file mode 100644
index 000000000000..2df547d75f92
--- /dev/null
+++ b/pkgs/development/libraries/fb303/default.nix
@@ -0,0 +1,55 @@
+{ stdenv
+, lib
+, fetchFromGitHub
+, cmake
+, glog
+, folly
+, fmt_8
+, boost
+, fbthrift
+, zlib
+, fizz
+, libsodium
+, wangle
+, python3
+}:
+
+stdenv.mkDerivation rec {
+ pname = "fb303";
+ version = "2023.01.30.00";
+
+ src = fetchFromGitHub {
+ owner = "facebook";
+ repo = "fb303";
+ rev = "v${version}";
+ sha256 = "sha256-k0kDaiSLaGNPhgCgksAu/qM9e4ogISQaFvWq4/mZIeI=";
+ };
+
+ nativeBuildInputs = [ cmake ];
+ cmakeFlags = [
+ "-DPYTHON_EXTENSIONS=OFF"
+ ] ++ lib.optionals stdenv.isDarwin [
+ "-DCMAKE_OSX_DEPLOYMENT_TARGET=10.14" # For aligned allocation
+ ];
+
+ buildInputs = [
+ glog
+ folly
+ fmt_8
+ boost
+ fbthrift
+ zlib
+ fizz
+ libsodium
+ wangle
+ python3
+ ];
+
+ meta = with lib; {
+ description = "a base Thrift service and a common set of functionality for querying stats, options, and other information from a service";
+ homepage = "https://github.com/facebook/fb303";
+ license = licenses.asl20;
+ platforms = platforms.unix;
+ maintainers = with maintainers; [ kylesferrazza ];
+ };
+}
diff --git a/pkgs/development/libraries/fbthrift/default.nix b/pkgs/development/libraries/fbthrift/default.nix
new file mode 100644
index 000000000000..bcaae0e60565
--- /dev/null
+++ b/pkgs/development/libraries/fbthrift/default.nix
@@ -0,0 +1,68 @@
+{ stdenv
+, fetchFromGitHub
+, cmake
+, bison
+, boost
+, libevent
+, double-conversion
+, libsodium
+, fizz
+, flex
+, fmt_8
+, folly
+, glog
+, gflags
+, libiberty
+, openssl
+, lib
+, wangle
+, zlib
+, zstd
+}:
+
+stdenv.mkDerivation rec {
+ pname = "fbthrift";
+ version = "2023.01.30.00";
+
+ src = fetchFromGitHub {
+ owner = "facebook";
+ repo = "fbthrift";
+ rev = "v${version}";
+ sha256 = "sha256-poXe2EF4ZcqOZza1WUSAO2cA655jiWpqdo3YYrzAk7I=";
+ };
+
+ nativeBuildInputs = [
+ cmake
+ bison
+ flex
+ ];
+
+ cmakeFlags = lib.optionals stdenv.isDarwin [
+ "-DCMAKE_OSX_DEPLOYMENT_TARGET=10.14" # For aligned allocation
+ ];
+
+ buildInputs = [
+ boost
+ double-conversion
+ fizz
+ fmt_8
+ folly
+ glog
+ gflags
+ libevent
+ libiberty
+ openssl
+ wangle
+ zlib
+ zstd
+ libsodium
+ ];
+
+ meta = with lib; {
+ description = "Facebook's branch of Apache Thrift";
+ homepage = "https://github.com/facebook/fbthrift";
+ license = licenses.asl20;
+ platforms = platforms.unix;
+ maintainers = with maintainers; [ pierreis kylesferrazza ];
+ };
+}
diff --git a/pkgs/development/libraries/fizz/default.nix b/pkgs/development/libraries/fizz/default.nix
new file mode 100644
index 000000000000..2addb5748263
--- /dev/null
+++ b/pkgs/development/libraries/fizz/default.nix
@@ -0,0 +1,65 @@
+{ stdenv
+, fetchFromGitHub
+, cmake
+, boost
+, libevent
+, double-conversion
+, glog
+, lib
+, fmt_8
+, zstd
+, gflags
+, libiberty
+, openssl
+, folly
+, libsodium
+, gtest
+, zlib
+}:
+
+stdenv.mkDerivation rec {
+ pname = "fizz";
+ version = "2023.01.30.00";
+
+ src = fetchFromGitHub {
+ owner = "facebookincubator";
+ repo = "fizz";
+ rev = "v${version}";
+ sha256 = "sha256-WyqDVoByBP91qGohNadr3iGpKEwZrURjr9mEaAdbfvs=";
+ };
+
+ nativeBuildInputs = [ cmake ];
+
+ cmakeDir = "../fizz";
+
+ cmakeFlags = [ "-Wno-dev" ]
+ ++ lib.optionals stdenv.isDarwin [
+ "-DCMAKE_OSX_DEPLOYMENT_TARGET=10.14" # For aligned allocation
+ ];
+
+ NIX_LDFLAGS = "-lz";
+
+ buildInputs = [
+ fmt_8
+ boost
+ double-conversion
+ folly
+ glog
+ gflags
+ gtest
+ libevent
+ libiberty
+ libsodium
+ openssl
+ zlib
+ zstd
+ ];
+
+ meta = with lib; {
+ description = "C++14 implementation of the TLS-1.3 standard";
+ homepage = "https://github.com/facebookincubator/fizz";
+ license = licenses.bsd3;
+ platforms = platforms.unix;
+ maintainers = with maintainers; [ pierreis kylesferrazza ];
+ };
+}
diff --git a/pkgs/development/libraries/folly/default.nix b/pkgs/development/libraries/folly/default.nix
index 573227052f70..9f54350e4e22 100644
--- a/pkgs/development/libraries/folly/default.nix
+++ b/pkgs/development/libraries/folly/default.nix
@@ -1,4 +1,5 @@
-{ lib, stdenv
+{ lib
+, stdenv
, fetchFromGitHub
, boost
, cmake
@@ -57,7 +58,13 @@ stdenv.mkDerivation rec {
propagatedBuildInputs = lib.optional stdenv.isLinux jemalloc;
NIX_CFLAGS_COMPILE = [ "-DFOLLY_MOBILE=${if follyMobile then "1" else "0"}" "-fpermissive" ];
- cmakeFlags = [ "-DBUILD_SHARED_LIBS=ON" ];
+ cmakeFlags = [
+ "-DBUILD_SHARED_LIBS=ON"
+
+ # temporary hack until folly builds work on aarch64,
+ # see https://github.com/facebook/folly/issues/1880
+ "-DCMAKE_LIBRARY_ARCHITECTURE=${if stdenv.isx86_64 then "x86_64" else "dummy"}"
+ ];
postFixup = ''
substituteInPlace "$out"/lib/pkgconfig/libfolly.pc \
diff --git a/pkgs/development/libraries/opensubdiv/default.nix b/pkgs/development/libraries/opensubdiv/default.nix
index 46bbc079aeb8..9511f4f56f7e 100644
--- a/pkgs/development/libraries/opensubdiv/default.nix
+++ b/pkgs/development/libraries/opensubdiv/default.nix
@@ -10,13 +10,13 @@
stdenv.mkDerivation rec {
pname = "opensubdiv";
- version = "3.4.4";
+ version = "3.5.0";
src = fetchFromGitHub {
owner = "PixarAnimationStudios";
repo = "OpenSubdiv";
rev = "v${lib.replaceStrings ["."] ["_"] version}";
- sha256 = "sha256-ejxQ5mGIIrEa/rAfkTrRbIRerrAvEPoWn7e0lIqS1JQ=";
+ sha256 = "sha256-pYD2HxAszE9Ux1xsSJ7s2R13U8ct5tDo3ZP7H0+F9Rc=";
};
outputs = [ "out" "dev" ];
diff --git a/pkgs/development/libraries/rocm-opencl-runtime/default.nix b/pkgs/development/libraries/rocm-opencl-runtime/default.nix
index 114245b7d715..225236b0a961 100644
--- a/pkgs/development/libraries/rocm-opencl-runtime/default.nix
+++ b/pkgs/development/libraries/rocm-opencl-runtime/default.nix
@@ -14,7 +14,7 @@
stdenv.mkDerivation (finalAttrs: {
pname = "rocm-opencl-runtime";
- version = "5.4.2";
+ version = "5.4.3";
src = fetchFromGitHub {
owner = "RadeonOpenCompute";
diff --git a/pkgs/development/libraries/rocm-runtime/default.nix b/pkgs/development/libraries/rocm-runtime/default.nix
index 345a8c8d25d6..d10f7811ccbb 100644
--- a/pkgs/development/libraries/rocm-runtime/default.nix
+++ b/pkgs/development/libraries/rocm-runtime/default.nix
@@ -16,7 +16,7 @@
stdenv.mkDerivation (finalAttrs: {
pname = "rocm-runtime";
- version = "5.4.1";
+ version = "5.4.3";
src = fetchFromGitHub {
owner = "RadeonOpenCompute";
diff --git a/pkgs/development/libraries/rocm-thunk/default.nix b/pkgs/development/libraries/rocm-thunk/default.nix
index a083f57722db..f22a72ac2b3e 100644
--- a/pkgs/development/libraries/rocm-thunk/default.nix
+++ b/pkgs/development/libraries/rocm-thunk/default.nix
@@ -12,7 +12,7 @@
stdenv.mkDerivation (finalAttrs: {
pname = "rocm-thunk";
- version = "5.4.2";
+ version = "5.4.3";
src = fetchFromGitHub {
owner = "RadeonOpenCompute";
diff --git a/pkgs/development/libraries/wangle/default.nix b/pkgs/development/libraries/wangle/default.nix
new file mode 100644
index 000000000000..2dc62f299fc3
--- /dev/null
+++ b/pkgs/development/libraries/wangle/default.nix
@@ -0,0 +1,68 @@
+{ stdenv
+, lib
+, fetchFromGitHub
+, cmake
+, boost
+, libevent
+, double-conversion
+, glog
+, fmt_8
+, gflags
+, openssl
+, fizz
+, folly
+, gtest
+, libsodium
+, zlib
+}:
+
+stdenv.mkDerivation rec {
+ pname = "wangle";
+ version = "2023.01.30.00";
+
+ src = fetchFromGitHub {
+ owner = "facebook";
+ repo = "wangle";
+ rev = "v${version}";
+ sha256 = "sha256-pHBFX9zs1vHXveZw9HCieRuQldLrq5fwJXWzNyLx1Kg=";
+ };
+
+ nativeBuildInputs = [ cmake ];
+
+ cmakeDir = "../wangle";
+
+ cmakeFlags = [
+ "-Wno-dev"
+ ] ++ lib.optionals stdenv.isDarwin [
+ "-DBUILD_TESTS=off" # Tests fail on Darwin due to missing utimensat
+ "-DCMAKE_OSX_DEPLOYMENT_TARGET=10.14" # For aligned allocation
+ ];
+
+ buildInputs = [
+ fmt_8
+ libsodium
+ zlib
+ boost
+ double-conversion
+ fizz
+ folly
+ gtest
+ glog
+ gflags
+ libevent
+ openssl
+ ];
+
+ meta = with lib; {
+ description = "An open-source C++ networking library";
+ longDescription = ''
+ Wangle is a framework providing a set of common client/server
+ abstractions for building services in a consistent, modular, and
+ composable way.
+ '';
+ homepage = "https://github.com/facebook/wangle";
+ license = licenses.asl20;
+ platforms = platforms.unix;
+ maintainers = with maintainers; [ pierreis kylesferrazza ];
+ };
+}
diff --git a/pkgs/development/php-packages/grumphp/default.nix b/pkgs/development/php-packages/grumphp/default.nix
index b2d319d7f404..c7c2d9fc323e 100644
--- a/pkgs/development/php-packages/grumphp/default.nix
+++ b/pkgs/development/php-packages/grumphp/default.nix
@@ -1,11 +1,11 @@
{ mkDerivation, fetchurl, makeWrapper, lib, php }:
-mkDerivation rec {
+mkDerivation (finalAttrs: {
pname = "grumphp";
version = "1.15.0";
src = fetchurl {
- url = "https://github.com/phpro/${pname}/releases/download/v${version}/${pname}.phar";
+ url = "https://github.com/phpro/grumphp/releases/download/v${finalAttrs.version}/grumphp.phar";
sha256 = "sha256-EqzJb7DYZb7PnebErLVI/EZLxj0m26cniZlsu1feif0=";
};
@@ -16,17 +16,17 @@ mkDerivation rec {
installPhase = ''
runHook preInstall
mkdir -p $out/bin
- install -D $src $out/libexec/${pname}/grumphp.phar
+ install -D $src $out/libexec/grumphp/grumphp.phar
makeWrapper ${php}/bin/php $out/bin/grumphp \
- --add-flags "$out/libexec/${pname}/grumphp.phar"
+ --add-flags "$out/libexec/grumphp/grumphp.phar"
runHook postInstall
'';
meta = with lib; {
- changelog = "https://github.com/phpro/grumphp/releases/tag/v${version}";
+ changelog = "https://github.com/phpro/grumphp/releases/tag/v${finalAttrs.version}";
description = "A PHP code-quality tool";
homepage = "https://github.com/phpro/grumphp";
license = licenses.mit;
maintainers = teams.php.members;
};
-}
+})
diff --git a/pkgs/development/python-modules/adafruit-pureio/default.nix b/pkgs/development/python-modules/adafruit-pureio/default.nix
index d3712ba46c24..6d32b9530523 100644
--- a/pkgs/development/python-modules/adafruit-pureio/default.nix
+++ b/pkgs/development/python-modules/adafruit-pureio/default.nix
@@ -1,28 +1,38 @@
{ lib
, buildPythonPackage
, fetchPypi
+, pythonOlder
, setuptools-scm
}:
buildPythonPackage rec {
- pname = "Adafruit-PureIO";
- version = "1.1.9";
+ pname = "adafruit-pureio";
+ version = "1.1.10";
+ format = "setuptools";
+
+ disabled = pythonOlder "3.7";
src = fetchPypi {
pname = "Adafruit_PureIO";
inherit version;
- sha256 = "0yd8hw676s7plq75gac4z0ilfcfydjkk3wv76bc73xy70zxj5brc";
+ hash = "sha256-EgaIN1PAlmMJ5tAtqXBnbpvHtQO7Sib3NuAXOfVqZLk=";
};
- nativeBuildInputs = [ setuptools-scm ];
+ nativeBuildInputs = [
+ setuptools-scm
+ ];
# Physical SMBus is not present
doCheck = false;
- pythonImportsCheck = [ "Adafruit_PureIO" ];
+
+ pythonImportsCheck = [
+ "Adafruit_PureIO"
+ ];
meta = with lib; {
description = "Python interface to Linux IO including I2C and SPI";
homepage = "https://github.com/adafruit/Adafruit_Python_PureIO";
+ changelog = "https://github.com/adafruit/Adafruit_Python_PureIO/releases/tag/${version}";
license = with licenses; [ mit ];
maintainers = with maintainers; [ fab ];
};
diff --git a/pkgs/development/python-modules/aiohttp-jinja2/default.nix b/pkgs/development/python-modules/aiohttp-jinja2/default.nix
index 8e062db87e6d..a9773ff498e1 100644
--- a/pkgs/development/python-modules/aiohttp-jinja2/default.nix
+++ b/pkgs/development/python-modules/aiohttp-jinja2/default.nix
@@ -10,14 +10,14 @@
buildPythonPackage rec {
pname = "aiohttp-jinja2";
- version = "1.5";
+ version = "1.5.1";
format = "setuptools";
disabled = pythonOlder "3.7";
src = fetchPypi {
inherit pname version;
- hash = "sha256-fDul6sBgtpH05QU0ry15/KKnVxLr0rJeb8sSlYWfkQs=";
+ hash = "sha256-jRSbKlfZH3lLM6OU6lvGa1Z/OMdKWmqUd6/CRQ8QXAE=";
};
propagatedBuildInputs = [
diff --git a/pkgs/development/python-modules/aiomisc/default.nix b/pkgs/development/python-modules/aiomisc/default.nix
index b3a65926d6e8..ce000ddb0361 100644
--- a/pkgs/development/python-modules/aiomisc/default.nix
+++ b/pkgs/development/python-modules/aiomisc/default.nix
@@ -20,14 +20,14 @@
buildPythonPackage rec {
pname = "aiomisc";
- version = "16.2.10";
+ version = "16.3.15";
format = "setuptools";
disabled = pythonOlder "3.7";
src = fetchPypi {
inherit pname version;
- hash = "sha256-iQlbd1DoPgxq+Am0BTDYXIBZoC21/54+bywDtcCXlls=";
+ hash = "sha256-lHDjsK8ds1ftovY2IAbJwk3jnn4FoDo6f/Nu/MSAhqM=";
};
propagatedBuildInputs = [
diff --git a/pkgs/development/python-modules/azure-data-tables/default.nix b/pkgs/development/python-modules/azure-data-tables/default.nix
index 1d8ce8d5675a..351a870750d3 100644
--- a/pkgs/development/python-modules/azure-data-tables/default.nix
+++ b/pkgs/development/python-modules/azure-data-tables/default.nix
@@ -7,12 +7,12 @@
buildPythonPackage rec {
pname = "azure-data-tables";
- version = "12.4.1";
+ version = "12.4.2";
src = fetchPypi {
inherit pname version;
extension = "zip";
- sha256 = "sha256-FvEo6PZubKBcB/t4/MxxNJMjHfHYXjPE4lp5yURVhko=";
+ sha256 = "sha256-Oz1dFbKpY+CbSTSx/iuiF/Kd2axRghwXVJ/K+HRwJDQ=";
};
propagatedBuildInputs = [
diff --git a/pkgs/development/python-modules/hahomematic/default.nix b/pkgs/development/python-modules/hahomematic/default.nix
index cfcd3b060565..f019174f8ddc 100644
--- a/pkgs/development/python-modules/hahomematic/default.nix
+++ b/pkgs/development/python-modules/hahomematic/default.nix
@@ -15,7 +15,7 @@
buildPythonPackage rec {
pname = "hahomematic";
- version = "2023.2.5";
+ version = "2023.2.7";
format = "pyproject";
disabled = pythonOlder "3.9";
@@ -24,7 +24,7 @@ buildPythonPackage rec {
owner = "danielperna84";
repo = pname;
rev = "refs/tags/${version}";
- sha256 = "sha256-DD6DZzFuAGOSJZq7PM8yhJMXdEXw6LR6KR/f5XUVZ8Y=";
+ sha256 = "sha256-1y4KdbXMa+25BQTAuLxfpXoQzoqJN8muldb/3b6IoMo=";
};
nativeBuildInputs = [
diff --git a/pkgs/development/python-modules/jupyter_console/default.nix b/pkgs/development/python-modules/jupyter_console/default.nix
index f5d4f12e3073..6159d457b64e 100644
--- a/pkgs/development/python-modules/jupyter_console/default.nix
+++ b/pkgs/development/python-modules/jupyter_console/default.nix
@@ -12,12 +12,12 @@
buildPythonPackage rec {
pname = "jupyter_console";
- version = "6.4.4";
+ version = "6.5.0";
disabled = pythonOlder "3.5";
src = fetchPypi {
inherit pname version;
- sha256 = "sha256-Fy9TNeMdYA32FhOpe38DUvLIJQu9EJLvLWWPdySfifs=";
+ sha256 = "sha256-Z+aPHaFrw/b3jthG3VVD7AZ5Np+FBHNPEL/SBvquOeo=";
};
propagatedBuildInputs = [
diff --git a/pkgs/development/python-modules/patiencediff/default.nix b/pkgs/development/python-modules/patiencediff/default.nix
index 4c5c0744b0e2..4837ffba7c27 100644
--- a/pkgs/development/python-modules/patiencediff/default.nix
+++ b/pkgs/development/python-modules/patiencediff/default.nix
@@ -8,7 +8,7 @@
buildPythonPackage rec {
pname = "patiencediff";
- version = "0.2.12";
+ version = "0.2.13";
format = "pyproject";
disabled = pythonOlder "3.7";
@@ -17,7 +17,7 @@ buildPythonPackage rec {
owner = "breezy-team";
repo = pname;
rev = "refs/tags/v${version}";
- hash = "sha256-BdTsx4UIRRK9fbMXOrgut651YMTowxHDFfitlP7ue2I=";
+ hash = "sha256-Hst/2hRqH8AIKD2EXtJo8m3diOxPBWAmNhtS3TUYT3I=";
};
nativeBuildInputs = [
diff --git a/pkgs/development/python-modules/pontos/default.nix b/pkgs/development/python-modules/pontos/default.nix
index 9383bdbf100e..849dc7b09612 100644
--- a/pkgs/development/python-modules/pontos/default.nix
+++ b/pkgs/development/python-modules/pontos/default.nix
@@ -16,7 +16,7 @@
buildPythonPackage rec {
pname = "pontos";
- version = "23.2.4";
+ version = "23.2.8";
format = "pyproject";
disabled = pythonOlder "3.7";
@@ -25,7 +25,7 @@ buildPythonPackage rec {
owner = "greenbone";
repo = pname;
rev = "refs/tags/v${version}";
- hash = "sha256-tunFd+hgaRx5wc1gRwZaNUEX550Rl1NR9rZfEWUw6H4=";
+ hash = "sha256-yxE+Gx48JQE++7SB8ouwgh2/rKKv8CC0QQSvwaSeFVc=";
};
nativeBuildInputs = [
diff --git a/pkgs/development/python-modules/sentry-sdk/default.nix b/pkgs/development/python-modules/sentry-sdk/default.nix
index e01c1828fe60..d81b055036c9 100644
--- a/pkgs/development/python-modules/sentry-sdk/default.nix
+++ b/pkgs/development/python-modules/sentry-sdk/default.nix
@@ -40,7 +40,7 @@
buildPythonPackage rec {
pname = "sentry-sdk";
- version = "1.14.0";
+ version = "1.15.0";
format = "setuptools";
disabled = pythonOlder "3.7";
@@ -49,7 +49,7 @@ buildPythonPackage rec {
owner = "getsentry";
repo = "sentry-python";
rev = "refs/tags/${version}";
- hash = "sha256-2STQKIAoaGLreGGkqOSrNrByu7j+7oxZihwp9COhuGM=";
+ hash = "sha256-xUDMi2xoRMsDDe7LcQxIxxozo8vV5ZPzZp5zmNld3ew=";
};
propagatedBuildInputs = [
diff --git a/pkgs/development/python-modules/trimesh/default.nix b/pkgs/development/python-modules/trimesh/default.nix
index 1c191cc2991a..d09b5e7824f9 100644
--- a/pkgs/development/python-modules/trimesh/default.nix
+++ b/pkgs/development/python-modules/trimesh/default.nix
@@ -6,11 +6,11 @@
buildPythonPackage rec {
pname = "trimesh";
- version = "3.18.3";
+ version = "3.19.3";
src = fetchPypi {
inherit pname version;
- sha256 = "sha256-lVoBBBrzyhrSmR2FM0xo8UJBCOShwaYOrIpeAwQn76M=";
+ sha256 = "sha256-03C6BPjVmsSTsJSIUnhyxonSqvTEc3ZkBw8xQeAIwWw=";
};
propagatedBuildInputs = [ numpy ];
diff --git a/pkgs/development/tools/analysis/codeql/default.nix b/pkgs/development/tools/analysis/codeql/default.nix
index 0a9cefb57b06..0f560d0b3a15 100644
--- a/pkgs/development/tools/analysis/codeql/default.nix
+++ b/pkgs/development/tools/analysis/codeql/default.nix
@@ -2,7 +2,7 @@
stdenv.mkDerivation rec {
pname = "codeql";
- version = "2.12.1";
+ version = "2.12.2";
dontConfigure = true;
dontBuild = true;
@@ -10,7 +10,7 @@ stdenv.mkDerivation rec {
src = fetchzip {
url = "https://github.com/github/codeql-cli-binaries/releases/download/v${version}/codeql.zip";
- sha256 = "sha256-rJdB1G2/Fbs5zwfXF/Q79k1IztkOJrL7b0sjH5kcEMs=";
+ sha256 = "sha256-n36x50rGA0fzvbwrUDpzWmF7XqwTTxnAfFtBL23gEOE=";
};
nativeBuildInputs = [
diff --git a/pkgs/development/tools/goresym/default.nix b/pkgs/development/tools/goresym/default.nix
index f2cf1f8a48ff..245f86788a59 100644
--- a/pkgs/development/tools/goresym/default.nix
+++ b/pkgs/development/tools/goresym/default.nix
@@ -2,18 +2,18 @@
buildGoModule rec {
pname = "goresym";
- version = "2.1";
+ version = "2.1.1";
src = fetchFromGitHub {
owner = "mandiant";
repo = pname;
rev = "v${version}";
- sha256 = "sha256-v7rZBVpQMuEoIK9JIXCJnSjMDe3wrtJvL766MN6VmFo=";
+ sha256 = "sha256-Tf/oD0f8XLG2CuiQvduVberzWSetojVRBrSd83snK5Q=";
};
subPackages = [ "." ];
- vendorSha256 = "sha256-ElV5edbe1LQWbA1NKv52/rLZJeOLBahE4YBKg9OA7YY=";
+ vendorHash = "sha256-ElV5edbe1LQWbA1NKv52/rLZJeOLBahE4YBKg9OA7YY=";
doCheck = true;
diff --git a/pkgs/development/tools/refurb/default.nix b/pkgs/development/tools/refurb/default.nix
index d0b0000e59a4..ee5308951577 100644
--- a/pkgs/development/tools/refurb/default.nix
+++ b/pkgs/development/tools/refurb/default.nix
@@ -5,14 +5,14 @@
python3Packages.buildPythonApplication rec {
pname = "refurb";
- version = "1.10.0";
+ version = "1.12.0";
format = "pyproject";
src = fetchFromGitHub {
owner = "dosisod";
repo = "refurb";
rev = "refs/tags/v${version}";
- hash = "sha256-wb9E1BX9gjejZ5nTudzEPP+suX2eG4MPT07651+OY88=";
+ hash = "sha256-dS9+S3RogsBlbEHyq5Ll3kGbULwIQHQkwwNjjbsrgio=";
};
nativeBuildInputs = with python3Packages; [
diff --git a/pkgs/development/tools/watchman/Cargo.lock b/pkgs/development/tools/watchman/Cargo.lock
new file mode 100644
index 000000000000..9554b7be1f5b
--- /dev/null
+++ b/pkgs/development/tools/watchman/Cargo.lock
@@ -0,0 +1,994 @@
+# This file is automatically @generated by Cargo.
+# It is not intended for manual editing.
+version = 3
+
+[[package]]
+name = "ahash"
+version = "0.3.8"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e8fd72866655d1904d6b0997d0b07ba561047d070fbe29de039031c641b61217"
+dependencies = [
+ "const-random",
+]
+
+[[package]]
+name = "ansi_term"
+version = "0.12.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d52a9bb7ec0cf484c551830a7ce27bd20d67eac647e1befb56b0be4ee39a55d2"
+dependencies = [
+ "winapi",
+]
+
+[[package]]
+name = "anyhow"
+version = "1.0.68"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "2cb2f989d18dd141ab8ae82f64d1a8cdd37e0840f73a406896cf5e99502fab61"
+
+[[package]]
+name = "atty"
+version = "0.2.14"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
+dependencies = [
+ "hermit-abi 0.1.19",
+ "libc",
+ "winapi",
+]
+
+[[package]]
+name = "autocfg"
+version = "1.1.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
+
+[[package]]
+name = "bitflags"
+version = "1.3.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
+
+[[package]]
+name = "byteorder"
+version = "1.4.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
+
+[[package]]
+name = "bytes"
+version = "1.3.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "dfb24e866b15a1af2a1b663f10c6b6b8f397a84aadb828f12e5b289ec23a3a3c"
+dependencies = [
+ "serde",
+]
+
+[[package]]
+name = "cc"
+version = "1.0.78"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a20104e2335ce8a659d6dd92a51a767a0c062599c73b343fd152cb401e828c3d"
+
+[[package]]
+name = "cfg-if"
+version = "1.0.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
+
+[[package]]
+name = "clap"
+version = "2.34.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a0610544180c38b88101fecf2dd634b174a62eef6946f84dfc6a7127512b381c"
+dependencies = [
+ "ansi_term",
+ "atty",
+ "bitflags",
+ "strsim",
+ "textwrap",
+ "unicode-width",
+ "vec_map",
+]
+
+[[package]]
+name = "const-random"
+version = "0.1.15"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "368a7a772ead6ce7e1de82bfb04c485f3db8ec744f72925af5735e29a22cc18e"
+dependencies = [
+ "const-random-macro",
+ "proc-macro-hack",
+]
+
+[[package]]
+name = "const-random-macro"
+version = "0.1.15"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9d7d6ab3c3a2282db210df5f02c4dab6e0a7057af0fb7ebd4070f30fe05c0ddb"
+dependencies = [
+ "getrandom",
+ "once_cell",
+ "proc-macro-hack",
+ "tiny-keccak",
+]
+
+[[package]]
+name = "core-foundation-sys"
+version = "0.8.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5827cebf4670468b8772dd191856768aedcb1b0278a04f989f7766351917b9dc"
+
+[[package]]
+name = "crossbeam"
+version = "0.8.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "2801af0d36612ae591caa9568261fddce32ce6e08a7275ea334a06a4ad021a2c"
+dependencies = [
+ "cfg-if",
+ "crossbeam-channel",
+ "crossbeam-deque",
+ "crossbeam-epoch",
+ "crossbeam-queue",
+ "crossbeam-utils",
+]
+
+[[package]]
+name = "crossbeam-channel"
+version = "0.5.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c2dd04ddaf88237dc3b8d8f9a3c1004b506b54b3313403944054d23c0870c521"
+dependencies = [
+ "cfg-if",
+ "crossbeam-utils",
+]
+
+[[package]]
+name = "crossbeam-deque"
+version = "0.8.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "715e8152b692bba2d374b53d4875445368fdf21a94751410af607a5ac677d1fc"
+dependencies = [
+ "cfg-if",
+ "crossbeam-epoch",
+ "crossbeam-utils",
+]
+
+[[package]]
+name = "crossbeam-epoch"
+version = "0.9.13"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "01a9af1f4c2ef74bb8aa1f7e19706bc72d03598c8a570bb5de72243c7a9d9d5a"
+dependencies = [
+ "autocfg",
+ "cfg-if",
+ "crossbeam-utils",
+ "memoffset 0.7.1",
+ "scopeguard",
+]
+
+[[package]]
+name = "crossbeam-queue"
+version = "0.3.8"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d1cfb3ea8a53f37c40dea2c7bedcbd88bdfae54f5e2175d6ecaff1c988353add"
+dependencies = [
+ "cfg-if",
+ "crossbeam-utils",
+]
+
+[[package]]
+name = "crossbeam-utils"
+version = "0.8.14"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "4fb766fa798726286dbbb842f174001dab8abc7b627a1dd86e0b7222a95d929f"
+dependencies = [
+ "cfg-if",
+]
+
+[[package]]
+name = "crunchy"
+version = "0.2.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7a81dae078cea95a014a339291cec439d2f232ebe854a9d672b796c6afafa9b7"
+
+[[package]]
+name = "duct"
+version = "0.13.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "37ae3fc31835f74c2a7ceda3aeede378b0ae2e74c8f1c36559fcc9ae2a4e7d3e"
+dependencies = [
+ "libc",
+ "once_cell",
+ "os_pipe",
+ "shared_child",
+]
+
+[[package]]
+name = "either"
+version = "1.8.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "90e5c1c8368803113bf0c9584fc495a58b86dc8a29edbf8fe877d21d9507e797"
+
+[[package]]
+name = "futures"
+version = "0.1.31"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3a471a38ef8ed83cd6e40aa59c1ffe17db6855c18e3604d9c4ed8c08ebc28678"
+
+[[package]]
+name = "futures"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "38390104763dc37a5145a53c29c63c1290b5d316d6086ec32c293f6736051bb0"
+dependencies = [
+ "futures-channel",
+ "futures-core",
+ "futures-executor",
+ "futures-io",
+ "futures-sink",
+ "futures-task",
+ "futures-util",
+]
+
+[[package]]
+name = "futures-channel"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "52ba265a92256105f45b719605a571ffe2d1f0fea3807304b522c1d778f79eed"
+dependencies = [
+ "futures-core",
+ "futures-sink",
+]
+
+[[package]]
+name = "futures-core"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "04909a7a7e4633ae6c4a9ab280aeb86da1236243a77b694a49eacd659a4bd3ac"
+
+[[package]]
+name = "futures-executor"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7acc85df6714c176ab5edf386123fafe217be88c0840ec11f199441134a074e2"
+dependencies = [
+ "futures-core",
+ "futures-task",
+ "futures-util",
+]
+
+[[package]]
+name = "futures-io"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "00f5fb52a06bdcadeb54e8d3671f8888a39697dcb0b81b23b55174030427f4eb"
+
+[[package]]
+name = "futures-macro"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "bdfb8ce053d86b91919aad980c220b1fb8401a9394410e1c289ed7e66b61835d"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "futures-sink"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "39c15cf1a4aa79df40f1bb462fb39676d0ad9e366c2a33b590d7c66f4f81fcf9"
+
+[[package]]
+name = "futures-task"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "2ffb393ac5d9a6eaa9d3fdf37ae2776656b706e200c8e16b1bdb227f5198e6ea"
+
+[[package]]
+name = "futures-util"
+version = "0.3.25"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "197676987abd2f9cadff84926f410af1c183608d36641465df73ae8211dc65d6"
+dependencies = [
+ "futures 0.1.31",
+ "futures-channel",
+ "futures-core",
+ "futures-io",
+ "futures-macro",
+ "futures-sink",
+ "futures-task",
+ "memchr",
+ "pin-project-lite",
+ "pin-utils",
+ "slab",
+]
+
+[[package]]
+name = "getrandom"
+version = "0.2.8"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c05aeb6a22b8f62540c194aac980f2115af067bfe15a0734d7277a768d396b31"
+dependencies = [
+ "cfg-if",
+ "libc",
+ "wasi",
+]
+
+[[package]]
+name = "heck"
+version = "0.3.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "6d621efb26863f0e9924c6ac577e8275e5e6b77455db64ffa6c65c904e9e132c"
+dependencies = [
+ "unicode-segmentation",
+]
+
+[[package]]
+name = "hermit-abi"
+version = "0.1.19"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "62b467343b94ba476dcb2500d242dadbb39557df889310ac77c5d99100aaac33"
+dependencies = [
+ "libc",
+]
+
+[[package]]
+name = "hermit-abi"
+version = "0.2.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ee512640fe35acbfb4bb779db6f0d80704c2cacfa2e39b601ef3e3f47d1ae4c7"
+dependencies = [
+ "libc",
+]
+
+[[package]]
+name = "itoa"
+version = "1.0.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "fad582f4b9e86b6caa621cabeb0963332d92eea04729ab12892c2533951e6440"
+
+[[package]]
+name = "jwalk"
+version = "0.6.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5dbcda57db8b6dc067e589628b7348639014e793d9e8137d8cf215e8b133a0bd"
+dependencies = [
+ "crossbeam",
+ "rayon",
+]
+
+[[package]]
+name = "lazy_static"
+version = "1.4.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
+
+[[package]]
+name = "libc"
+version = "0.2.139"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "201de327520df007757c1f0adce6e827fe8562fbc28bfd9c15571c66ca1f5f79"
+
+[[package]]
+name = "lock_api"
+version = "0.4.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "435011366fe56583b16cf956f9df0095b405b82d76425bc8981c0e22e60ec4df"
+dependencies = [
+ "autocfg",
+ "scopeguard",
+]
+
+[[package]]
+name = "log"
+version = "0.4.17"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "abb12e687cfb44aa40f41fc3978ef76448f9b6038cad6aef4259d3c095a2382e"
+dependencies = [
+ "cfg-if",
+]
+
+[[package]]
+name = "maplit"
+version = "1.0.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3e2e65a1a2e43cfcb47a895c4c8b10d1f4a61097f9f254f183aee60cad9c651d"
+
+[[package]]
+name = "memchr"
+version = "2.5.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "2dffe52ecf27772e601905b7522cb4ef790d2cc203488bbd0e2fe85fcb74566d"
+
+[[package]]
+name = "memoffset"
+version = "0.6.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5aa361d4faea93603064a027415f07bd8e1d5c88c9fbf68bf56a285428fd79ce"
+dependencies = [
+ "autocfg",
+]
+
+[[package]]
+name = "memoffset"
+version = "0.7.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5de893c32cde5f383baa4c04c5d6dbdd735cfd4a794b0debdb2bb1b421da5ff4"
+dependencies = [
+ "autocfg",
+]
+
+[[package]]
+name = "mio"
+version = "0.8.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e5d732bc30207a6423068df043e3d02e0735b155ad7ce1a6f76fe2baa5b158de"
+dependencies = [
+ "libc",
+ "log",
+ "wasi",
+ "windows-sys",
+]
+
+[[package]]
+name = "nix"
+version = "0.23.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8f3790c00a0150112de0f4cd161e3d7fc4b2d8a5542ffc35f099a2562aecb35c"
+dependencies = [
+ "bitflags",
+ "cc",
+ "cfg-if",
+ "libc",
+ "memoffset 0.6.5",
+]
+
+[[package]]
+name = "ntapi"
+version = "0.4.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "bc51db7b362b205941f71232e56c625156eb9a929f8cf74a428fd5bc094a4afc"
+dependencies = [
+ "winapi",
+]
+
+[[package]]
+name = "num_cpus"
+version = "1.15.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0fac9e2da13b5eb447a6ce3d392f23a29d8694bff781bf03a16cd9ac8697593b"
+dependencies = [
+ "hermit-abi 0.2.6",
+ "libc",
+]
+
+[[package]]
+name = "once_cell"
+version = "1.17.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "6f61fba1741ea2b3d6a1e3178721804bb716a68a6aeba1149b5d52e3d464ea66"
+
+[[package]]
+name = "os_pipe"
+version = "1.1.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c6a252f1f8c11e84b3ab59d7a488e48e4478a93937e027076638c49536204639"
+dependencies = [
+ "libc",
+ "windows-sys",
+]
+
+[[package]]
+name = "parking_lot"
+version = "0.12.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "3742b2c103b9f06bc9fff0a37ff4912935851bee6d36f3c02bcc755bcfec228f"
+dependencies = [
+ "lock_api",
+ "parking_lot_core",
+]
+
+[[package]]
+name = "parking_lot_core"
+version = "0.9.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ba1ef8814b5c993410bb3adfad7a5ed269563e4a2f90c41f5d85be7fb47133bf"
+dependencies = [
+ "cfg-if",
+ "libc",
+ "redox_syscall",
+ "smallvec",
+ "windows-sys",
+]
+
+[[package]]
+name = "pin-project-lite"
+version = "0.2.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e0a7ae3ac2f1173085d398531c705756c94a4c56843785df85a60c1a0afac116"
+
+[[package]]
+name = "pin-utils"
+version = "0.1.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
+
+[[package]]
+name = "proc-macro-error"
+version = "1.0.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "da25490ff9892aab3fcf7c36f08cfb902dd3e71ca0f9f9517bea02a73a5ce38c"
+dependencies = [
+ "proc-macro-error-attr",
+ "proc-macro2",
+ "quote",
+ "syn",
+ "version_check",
+]
+
+[[package]]
+name = "proc-macro-error-attr"
+version = "1.0.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a1be40180e52ecc98ad80b184934baf3d0d29f979574e439af5a55274b35f869"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "version_check",
+]
+
+[[package]]
+name = "proc-macro-hack"
+version = "0.5.20+deprecated"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "dc375e1527247fe1a97d8b7156678dfe7c1af2fc075c9a4db3690ecd2a148068"
+
+[[package]]
+name = "proc-macro2"
+version = "1.0.50"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "6ef7d57beacfaf2d8aee5937dab7b7f28de3cb8b1828479bb5de2a7106f2bae2"
+dependencies = [
+ "unicode-ident",
+]
+
+[[package]]
+name = "quote"
+version = "1.0.23"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8856d8364d252a14d474036ea1358d63c9e6965c8e5c1885c18f73d70bff9c7b"
+dependencies = [
+ "proc-macro2",
+]
+
+[[package]]
+name = "rayon"
+version = "1.6.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "6db3a213adf02b3bcfd2d3846bb41cb22857d131789e01df434fb7e7bc0759b7"
+dependencies = [
+ "either",
+ "rayon-core",
+]
+
+[[package]]
+name = "rayon-core"
+version = "1.10.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "cac410af5d00ab6884528b4ab69d1e8e146e8d471201800fa1b4524126de6ad3"
+dependencies = [
+ "crossbeam-channel",
+ "crossbeam-deque",
+ "crossbeam-utils",
+ "num_cpus",
+]
+
+[[package]]
+name = "redox_syscall"
+version = "0.2.16"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "fb5a58c1855b4b6819d59012155603f0b22ad30cad752600aadfcb695265519a"
+dependencies = [
+ "bitflags",
+]
+
+[[package]]
+name = "ryu"
+version = "1.0.12"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "7b4b9743ed687d4b4bcedf9ff5eaa7398495ae14e61cba0a295704edbc7decde"
+
+[[package]]
+name = "scopeguard"
+version = "1.1.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
+
+[[package]]
+name = "serde"
+version = "1.0.152"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "bb7d1f0d3021d347a83e556fc4683dea2ea09d87bccdf88ff5c12545d89d5efb"
+dependencies = [
+ "serde_derive",
+]
+
+[[package]]
+name = "serde_bser"
+version = "0.3.1"
+dependencies = [
+ "anyhow",
+ "byteorder",
+ "bytes",
+ "serde",
+ "thiserror",
+]
+
+[[package]]
+name = "serde_derive"
+version = "1.0.152"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "af487d118eecd09402d70a5d72551860e788df87b464af30e5ea6a38c75c541e"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "serde_json"
+version = "1.0.91"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "877c235533714907a8c2464236f5c4b2a17262ef1bd71f38f35ea592c8da6883"
+dependencies = [
+ "itoa",
+ "ryu",
+ "serde",
+]
+
+[[package]]
+name = "shared_child"
+version = "1.0.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b0d94659ad3c2137fef23ae75b03d5241d633f8acded53d672decfa0e6e0caef"
+dependencies = [
+ "libc",
+ "winapi",
+]
+
+[[package]]
+name = "signal-hook-registry"
+version = "1.4.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e51e73328dc4ac0c7ccbda3a494dfa03df1de2f46018127f60c693f2648455b0"
+dependencies = [
+ "libc",
+]
+
+[[package]]
+name = "slab"
+version = "0.4.7"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "4614a76b2a8be0058caa9dbbaf66d988527d86d003c11a94fbd335d7661edcef"
+dependencies = [
+ "autocfg",
+]
+
+[[package]]
+name = "smallvec"
+version = "1.10.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a507befe795404456341dfab10cef66ead4c041f62b8b11bbb92bffe5d0953e0"
+
+[[package]]
+name = "socket2"
+version = "0.4.7"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "02e2d2db9033d13a1567121ddd7a095ee144db4e1ca1b1bda3419bc0da294ebd"
+dependencies = [
+ "libc",
+ "winapi",
+]
+
+[[package]]
+name = "strsim"
+version = "0.8.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
+
+[[package]]
+name = "structopt"
+version = "0.3.26"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0c6b5c64445ba8094a6ab0c3cd2ad323e07171012d9c98b0b15651daf1787a10"
+dependencies = [
+ "clap",
+ "lazy_static",
+ "structopt-derive",
+]
+
+[[package]]
+name = "structopt-derive"
+version = "0.4.18"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "dcb5ae327f9cc13b68763b5749770cb9e048a99bd9dfdfa58d0cf05d5f64afe0"
+dependencies = [
+ "heck",
+ "proc-macro-error",
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "syn"
+version = "1.0.107"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "1f4064b5b16e03ae50984a5a8ed5d4f8803e6bc1fd170a3cda91a1be4b18e3f5"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "unicode-ident",
+]
+
+[[package]]
+name = "sysinfo"
+version = "0.26.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5c18a6156d1f27a9592ee18c1a846ca8dd5c258b7179fc193ae87c74ebb666f5"
+dependencies = [
+ "cfg-if",
+ "core-foundation-sys",
+ "libc",
+ "ntapi",
+ "once_cell",
+ "rayon",
+ "winapi",
+]
+
+[[package]]
+name = "tabular"
+version = "0.2.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d9a2882c514780a1973df90de9d68adcd8871bacc9a6331c3f28e6d2ff91a3d1"
+dependencies = [
+ "unicode-width",
+]
+
+[[package]]
+name = "textwrap"
+version = "0.11.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
+dependencies = [
+ "unicode-width",
+]
+
+[[package]]
+name = "thiserror"
+version = "1.0.38"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "6a9cd18aa97d5c45c6603caea1da6628790b37f7a34b6ca89522331c5180fed0"
+dependencies = [
+ "thiserror-impl",
+]
+
+[[package]]
+name = "thiserror-impl"
+version = "1.0.38"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "1fb327af4685e4d03fa8cbcf1716380da910eeb2bb8be417e7f9fd3fb164f36f"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "tiny-keccak"
+version = "2.0.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "2c9d3793400a45f954c52e73d068316d76b6f4e36977e3fcebb13a2721e80237"
+dependencies = [
+ "crunchy",
+]
+
+[[package]]
+name = "tokio"
+version = "1.24.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "597a12a59981d9e3c38d216785b0c37399f6e415e8d0712047620f189371b0bb"
+dependencies = [
+ "autocfg",
+ "bytes",
+ "libc",
+ "memchr",
+ "mio",
+ "num_cpus",
+ "parking_lot",
+ "pin-project-lite",
+ "signal-hook-registry",
+ "socket2",
+ "tokio-macros",
+ "windows-sys",
+]
+
+[[package]]
+name = "tokio-macros"
+version = "1.8.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d266c00fde287f55d3f1c3e96c500c362a2b8c695076ec180f27918820bc6df8"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "syn",
+]
+
+[[package]]
+name = "tokio-util"
+version = "0.6.10"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "36943ee01a6d67977dd3f84a5a1d2efeb4ada3a1ae771cadfaa535d9d9fc6507"
+dependencies = [
+ "bytes",
+ "futures-core",
+ "futures-io",
+ "futures-sink",
+ "log",
+ "pin-project-lite",
+ "slab",
+ "tokio",
+]
+
+[[package]]
+name = "unicode-ident"
+version = "1.0.6"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "84a22b9f218b40614adcb3f4ff08b703773ad44fa9423e4e0d346d5db86e4ebc"
+
+[[package]]
+name = "unicode-segmentation"
+version = "1.10.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0fdbf052a0783de01e944a6ce7a8cb939e295b1e7be835a1112c3b9a7f047a5a"
+
+[[package]]
+name = "unicode-width"
+version = "0.1.10"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c0edd1e5b14653f783770bce4a4dabb4a5108a5370a5f5d8cfe8710c361f6c8b"
+
+[[package]]
+name = "vec_map"
+version = "0.8.2"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f1bddf1187be692e79c5ffeab891132dfb0f236ed36a43c7ed39f1165ee20191"
+
+[[package]]
+name = "version_check"
+version = "0.9.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
+
+[[package]]
+name = "wasi"
+version = "0.11.0+wasi-snapshot-preview1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
+
+[[package]]
+name = "watchman_client"
+version = "0.8.0"
+dependencies = [
+ "anyhow",
+ "bytes",
+ "futures 0.3.25",
+ "maplit",
+ "serde",
+ "serde_bser",
+ "thiserror",
+ "tokio",
+ "tokio-util",
+ "winapi",
+]
+
+[[package]]
+name = "watchmanctl"
+version = "0.1.0"
+dependencies = [
+ "ahash",
+ "anyhow",
+ "atty",
+ "duct",
+ "jwalk",
+ "nix",
+ "serde",
+ "serde_json",
+ "structopt",
+ "sysinfo",
+ "tabular",
+ "tokio",
+ "watchman_client",
+]
+
+[[package]]
+name = "winapi"
+version = "0.3.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
+dependencies = [
+ "winapi-i686-pc-windows-gnu",
+ "winapi-x86_64-pc-windows-gnu",
+]
+
+[[package]]
+name = "winapi-i686-pc-windows-gnu"
+version = "0.4.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
+
+[[package]]
+name = "winapi-x86_64-pc-windows-gnu"
+version = "0.4.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
+
+[[package]]
+name = "windows-sys"
+version = "0.42.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "5a3e1820f08b8513f676f7ab6c1f99ff312fb97b553d30ff4dd86f9f15728aa7"
+dependencies = [
+ "windows_aarch64_gnullvm",
+ "windows_aarch64_msvc",
+ "windows_i686_gnu",
+ "windows_i686_msvc",
+ "windows_x86_64_gnu",
+ "windows_x86_64_gnullvm",
+ "windows_x86_64_msvc",
+]
+
+[[package]]
+name = "windows_aarch64_gnullvm"
+version = "0.42.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "8c9864e83243fdec7fc9c5444389dcbbfd258f745e7853198f365e3c4968a608"
+
+[[package]]
+name = "windows_aarch64_msvc"
+version = "0.42.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "4c8b1b673ffc16c47a9ff48570a9d85e25d265735c503681332589af6253c6c7"
+
+[[package]]
+name = "windows_i686_gnu"
+version = "0.42.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "de3887528ad530ba7bdbb1faa8275ec7a1155a45ffa57c37993960277145d640"
+
+[[package]]
+name = "windows_i686_msvc"
+version = "0.42.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "bf4d1122317eddd6ff351aa852118a2418ad4214e6613a50e0191f7004372605"
+
+[[package]]
+name = "windows_x86_64_gnu"
+version = "0.42.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "c1040f221285e17ebccbc2591ffdc2d44ee1f9186324dd3e84e99ac68d699c45"
+
+[[package]]
+name = "windows_x86_64_gnullvm"
+version = "0.42.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "628bfdf232daa22b0d64fdb62b09fcc36bb01f05a3939e20ab73aaf9470d0463"
+
+[[package]]
+name = "windows_x86_64_msvc"
+version = "0.42.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "447660ad36a13288b1db4d4248e857b510e8c3a225c822ba4fb748c0aafecffd"
diff --git a/pkgs/development/tools/watchman/default.nix b/pkgs/development/tools/watchman/default.nix
index 2acbf13e2789..7a042ac8bc73 100644
--- a/pkgs/development/tools/watchman/default.nix
+++ b/pkgs/development/tools/watchman/default.nix
@@ -1,47 +1,107 @@
-{ stdenv, lib, config, fetchFromGitHub, autoconf, automake, pcre
-, libtool, pkg-config, openssl
-, confFile ? config.watchman.confFile or null
-, withApple ? stdenv.isDarwin, CoreServices
+{ boost
+, cmake
+, config
+, CoreServices
+, cpptoml
+, double-conversion
+, edencommon
+, ensureNewerSourcesForZipFilesHook
+, fb303
+, fbthrift
+, fetchFromGitHub
+, fizz
+, fmt_8
+, folly
+, glog
+, gtest
+, lib
+, libevent
+, libiconv
+, libsodium
+, libunwind
+, lz4
+, openssl
+, pcre
+, pkg-config
+, python3
+, rustPlatform
+, stateDir ? "/tmp"
+, stdenv
+, wangle
+, zlib
+, zstd
}:
stdenv.mkDerivation rec {
pname = "watchman";
- version = "4.9.0";
+ version = "2023.01.30.00";
src = fetchFromGitHub {
owner = "facebook";
repo = "watchman";
rev = "v${version}";
- sha256 = "0fdaj5pmicm6j17d5q7px800m5rmam1a400x3hv1iiifnmhgnkal";
+ sha256 = "sha256-ZtCUlxx3YgfwKa9J8o9GkdkHquJbh+EytLiGNRlABls=";
};
- nativeBuildInputs = [ autoconf automake pkg-config libtool ];
- buildInputs = [ pcre openssl ]
- ++ lib.optionals withApple [ CoreServices ];
-
- configureFlags = [
- "--enable-lenient"
- "--enable-conffile=${if confFile == null then "no" else confFile}"
- "--with-pcre=yes"
-
- # For security considerations re: --disable-statedir, see:
- # https://github.com/facebook/watchman/issues/178
- "--disable-statedir"
+ cmakeFlags = [
+ "-DBUILD_SHARED_LIBS=ON"
+ "-DENABLE_EDEN_SUPPORT=NO" # requires sapling (formerly known as eden), which is not packaged in nixpkgs
+ "-DWATCHMAN_STATE_DIR=${stateDir}"
+ ] ++ lib.optionals stdenv.isDarwin [
+ "-DCMAKE_OSX_DEPLOYMENT_TARGET=10.14" # For aligned allocation
];
- prePatch = ''
- patchShebangs .
- '';
+ nativeBuildInputs = [
+ cmake
+ pkg-config
+ ensureNewerSourcesForZipFilesHook
+ ] ++ (with rustPlatform; [
+ cargoSetupHook
+ rust.cargo
+ rust.rustc
+ ]);
- preConfigure = ''
- ./autogen.sh
+ buildInputs = [
+ pcre
+ openssl
+ python3
+ gtest
+ glog
+ boost
+ libevent
+ fmt_8
+ libsodium
+ zlib
+ folly
+ fizz
+ wangle
+ fbthrift
+ fb303
+ cpptoml
+ edencommon
+ libunwind
+ double-conversion
+ lz4
+ zstd
+ libiconv
+ ] ++ lib.optionals stdenv.isDarwin [ CoreServices ];
+
+ cargoRoot = "watchman/cli";
+
+ cargoDeps = rustPlatform.importCargoLock {
+ lockFile = ./Cargo.lock;
+ };
+
+ postPatch = ''
+ patchShebangs .
+ cp ${./Cargo.lock} ${cargoRoot}/Cargo.lock
'';
meta = with lib; {
description = "Watches files and takes action when they change";
- homepage = "https://facebook.github.io/watchman";
- maintainers = with maintainers; [ cstrahan ];
- platforms = with platforms; linux ++ darwin;
- license = licenses.asl20;
+ homepage = "https://facebook.github.io/watchman";
+ maintainers = with maintainers; [ cstrahan kylesferrazza ];
+ platforms = platforms.unix;
+ license = licenses.mit;
};
}
diff --git a/pkgs/games/fheroes2/default.nix b/pkgs/games/fheroes2/default.nix
index e1b15b6248f4..30ba8eaabe5a 100644
--- a/pkgs/games/fheroes2/default.nix
+++ b/pkgs/games/fheroes2/default.nix
@@ -6,13 +6,13 @@
stdenv.mkDerivation rec {
pname = "fheroes2";
- version = "1.0.0";
+ version = "1.0.1";
src = fetchFromGitHub {
owner = "ihhub";
repo = "fheroes2";
rev = version;
- sha256 = "sha256-86+4rFSvJ3xIVx+qDXZ65TSqIrPkbyoLNo1A+mFPdy8=";
+ sha256 = "sha256-l7MFvcUOv1jA7moA8VYcaQO15eyK/06x6Jznz5jsNNg=";
};
buildInputs = [ gettext glibcLocalesUtf8 libpng SDL2 SDL2_image SDL2_mixer SDL2_ttf zlib ];
diff --git a/pkgs/servers/matrix-synapse/default.nix b/pkgs/servers/matrix-synapse/default.nix
index 0c42373dd288..55d6bd68135f 100644
--- a/pkgs/servers/matrix-synapse/default.nix
+++ b/pkgs/servers/matrix-synapse/default.nix
@@ -67,7 +67,6 @@ buildPythonApplication rec {
pyasn1
pydantic
pyicu
- pyjwt
pymacaroons
pynacl
pyopenssl
diff --git a/pkgs/servers/sql/postgresql/default.nix b/pkgs/servers/sql/postgresql/default.nix
index 93df798c8bcb..c5e08b8279a3 100644
--- a/pkgs/servers/sql/postgresql/default.nix
+++ b/pkgs/servers/sql/postgresql/default.nix
@@ -207,45 +207,45 @@ let
in self: {
postgresql_11 = self.callPackage generic {
- version = "11.18";
+ version = "11.19";
psqlSchema = "11.1"; # should be 11, but changing it is invasive
- hash = "sha256-0k8g78UukYrPvMoh6c6ijg4mO4RqDECPz6w7PEoPdQQ=";
+ hash = "sha256-ExCeK3HxE5QFwnIB2jczphrOcu4cIo2cnwMg4GruFMI=";
this = self.postgresql_11;
thisAttr = "postgresql_11";
inherit self;
};
postgresql_12 = self.callPackage generic {
- version = "12.13";
+ version = "12.14";
psqlSchema = "12";
- hash = "sha256-tsYjBGr0VI8RqEtAeTTWddEe0HDHk9FbBGg79fMi4C0=";
+ hash = "sha256-eFYQI304LIQtNW40cTjljAb/6uJA5swLUqxevMMNBD4=";
this = self.postgresql_12;
thisAttr = "postgresql_12";
inherit self;
};
postgresql_13 = self.callPackage generic {
- version = "13.9";
+ version = "13.10";
psqlSchema = "13";
- hash = "sha256-7xlmwKXkn77TNwrSgkkoy2sRZGF67q4WBtooP38zpBU=";
+ hash = "sha256-W7z1pW2FxE86iwWPtGhi/0nLyRg00H4pXQLm3jwhbfI=";
this = self.postgresql_13;
thisAttr = "postgresql_13";
inherit self;
};
postgresql_14 = self.callPackage generic {
- version = "14.6";
+ version = "14.7";
psqlSchema = "14";
- hash = "sha256-UIhA/BgJ05q3InTV8Tfau5/X+0+TPaQWiu67IAae3yI=";
+ hash = "sha256-zvYPAJj6gQHBVG9CVORbcir1QxM3lFs3ryBwB2MNszE=";
this = self.postgresql_14;
thisAttr = "postgresql_14";
inherit self;
};
postgresql_15 = self.callPackage generic {
- version = "15.1";
+ version = "15.2";
psqlSchema = "15";
- hash = "sha256-ZP3yPXNK+tDf5Ad9rKlqxR3NaX5ori09TKbEXLFOIa4=";
+ hash = "sha256-maIXH8PWtbX1a3V6ejy4XVCaOOQnOAXe8jlB7SuEaMc=";
this = self.postgresql_15;
thisAttr = "postgresql_15";
inherit self;
diff --git a/pkgs/tools/misc/pre-commit/default.nix b/pkgs/tools/misc/pre-commit/default.nix
index 593ff2c68bd0..f51fcf254f98 100644
--- a/pkgs/tools/misc/pre-commit/default.nix
+++ b/pkgs/tools/misc/pre-commit/default.nix
@@ -159,6 +159,9 @@ buildPythonPackage rec {
"test_sub_staged"
"test_submodule_does_not_discard_changes"
"test_submodule_does_not_discard_changes_recurse"
+ ] ++ lib.optionals (stdenv.isLinux && stdenv.isAarch64) [
+ # requires gcc bump
+ "test_rust_hook"
];
pythonImportsCheck = [
diff --git a/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/docbook.py b/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/docbook.py
index 28c4425d8c08..b3728645f75f 100644
--- a/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/docbook.py
+++ b/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/docbook.py
@@ -34,12 +34,14 @@ class DocBookRenderer(Renderer):
_link_tags: list[str]
_deflists: list[Deflist]
_headings: list[Heading]
+ _attrspans: list[str]
def __init__(self, manpage_urls: Mapping[str, str], parser: Optional[markdown_it.MarkdownIt] = None):
super().__init__(manpage_urls, parser)
self._link_tags = []
self._deflists = []
self._headings = []
+ self._attrspans = []
def render(self, tokens: Sequence[Token], options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
@@ -212,9 +214,25 @@ class DocBookRenderer(Renderer):
else:
return ref
raise NotImplementedError("md node not supported yet", token)
- def inline_anchor(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
- env: MutableMapping[str, Any]) -> str:
- return f''
+ def attr_span_begin(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> str:
+ # we currently support *only* inline anchors and the special .keycap class to produce
+ # docbook elements.
+ (id_part, class_part) = ("", "")
+ if s := token.attrs.get('id'):
+ id_part = f''
+ if s := token.attrs.get('class'):
+ if s == 'keycap':
+ class_part = ""
+ self._attrspans.append("")
+ else:
+ return super().attr_span_begin(token, tokens, i, options, env)
+ else:
+ self._attrspans.append("")
+ return id_part + class_part
+ def attr_span_end(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> str:
+ return self._attrspans.pop()
def ordered_list_open(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
start = f' startingnumber="{token.attrs["start"]}"' if 'start' in token.attrs else ""
@@ -234,6 +252,14 @@ class DocBookRenderer(Renderer):
def heading_close(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
return ''
+ def example_open(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> str:
+ if id := token.attrs.get('id'):
+ return f""
+ return ""
+ def example_close(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> str:
+ return ""
def _close_headings(self, level: Optional[int], env: MutableMapping[str, Any]) -> str:
# we rely on markdown-it producing h{1..6} tags in token.tag for this to work
diff --git a/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/manpage.py b/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/manpage.py
index 24d0e8f3d699..1b796d9f0486 100644
--- a/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/manpage.py
+++ b/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/manpage.py
@@ -306,9 +306,15 @@ class ManpageRenderer(Renderer):
return f'\\fB{man_escape(page)}\\fP\\fR({man_escape(section)})\\fP'
else:
raise NotImplementedError("md node not supported yet", token)
- def inline_anchor(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ def attr_span_begin(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> str:
+ # mdoc knows no anchors so we can drop those, but classes must be rejected.
+ if 'class' in token.attrs:
+ return super().attr_span_begin(token, tokens, i, options, env)
+ return ""
+ def attr_span_end(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
- return "" # mdoc knows no anchors
+ return ""
def heading_open(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
raise RuntimeError("md token not supported in manpages", token)
diff --git a/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/manual.py b/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/manual.py
index 8c2d41457539..ab61d699d7f5 100644
--- a/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/manual.py
+++ b/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/manual.py
@@ -76,10 +76,14 @@ class ManualDocBookRenderer(DocBookRenderer):
return f"\n{escape(token.content)}"
def fence(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
+ # HACK for temporarily being able to replace md-to-db.sh. pandoc used this syntax to
+ # allow md files to inject arbitrary docbook, and manual chapters use it.
+ if token.info == '{=docbook}':
+ return token.content
info = f" language={quoteattr(token.info)}" if token.info != "" else ""
return f"\n{escape(token.content)}"
-class DocBookConverter(BaseConverter):
+class DocBookSectionConverter(BaseConverter):
__renderer__ = ManualDocBookRenderer
def finalize(self) -> str:
@@ -93,6 +97,29 @@ class DocBookConverter(BaseConverter):
return "\n".join(result)
+class ManualFragmentDocBookRenderer(ManualDocBookRenderer):
+ _tag: str = "chapter"
+
+ def _heading_tag(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> tuple[str, dict[str, str]]:
+ (tag, attrs) = super()._heading_tag(token, tokens, i, options, env)
+ if token.tag == 'h1':
+ return (self._tag, attrs | { 'xmlns:xi': "http://www.w3.org/2001/XInclude" })
+ return (tag, attrs)
+
+class DocBookFragmentConverter(Converter):
+ __renderer__ = ManualFragmentDocBookRenderer
+
+ def convert(self, file: Path, tag: str) -> str:
+ assert isinstance(self._md.renderer, ManualFragmentDocBookRenderer)
+ try:
+ with open(file, 'r') as f:
+ self._md.renderer._title_seen = False
+ self._md.renderer._tag = tag
+ return self._render(f.read())
+ except Exception as e:
+ raise RuntimeError(f"failed to render manual {tag} {file}") from e
+
class Section:
@@ -124,27 +151,52 @@ class ChaptersAction(argparse.Action):
if sections is None: raise argparse.ArgumentError(self, "no active section")
sections[-1].chapters.extend(map(Path, cast(Sequence[str], values)))
-def _build_cli_db(p: argparse.ArgumentParser) -> None:
+class SingleFileAction(argparse.Action):
+ def __call__(self, parser: argparse.ArgumentParser, ns: argparse.Namespace,
+ values: Union[str, Sequence[Any], None], opt_str: Optional[str] = None) -> None:
+ assert isinstance(values, Sequence)
+ chapters = getattr(ns, self.dest) or []
+ chapters.append((Path(values[0]), Path(values[1])))
+ setattr(ns, self.dest, chapters)
+
+def _build_cli_db_section(p: argparse.ArgumentParser) -> None:
p.add_argument('--manpage-urls', required=True)
p.add_argument("outfile")
p.add_argument("--section", dest="contents", action=SectionAction, nargs=0)
p.add_argument("--section-id", dest="contents", action=SectionIDAction)
p.add_argument("--chapters", dest="contents", action=ChaptersAction, nargs='+')
-def _run_cli_db(args: argparse.Namespace) -> None:
+def _build_cli_db_fragment(p: argparse.ArgumentParser) -> None:
+ p.add_argument('--manpage-urls', required=True)
+ p.add_argument("--chapter", action=SingleFileAction, required=True, nargs=2)
+ p.add_argument("--section", action=SingleFileAction, required=True, nargs=2)
+
+def _run_cli_db_section(args: argparse.Namespace) -> None:
with open(args.manpage_urls, 'r') as manpage_urls:
- md = DocBookConverter(json.load(manpage_urls))
+ md = DocBookSectionConverter(json.load(manpage_urls))
for section in args.contents:
md.add_section(section.id, section.chapters)
with open(args.outfile, 'w') as f:
f.write(md.finalize())
+def _run_cli_db_fragment(args: argparse.Namespace) -> None:
+ with open(args.manpage_urls, 'r') as manpage_urls:
+ md = DocBookFragmentConverter(json.load(manpage_urls))
+ for kind in [ 'chapter', 'section' ]:
+ for (target, file) in getattr(args, kind):
+ converted = md.convert(file, kind)
+ target.parent.mkdir(parents=True, exist_ok=True)
+ target.write_text(converted)
+
def build_cli(p: argparse.ArgumentParser) -> None:
formats = p.add_subparsers(dest='format', required=True)
- _build_cli_db(formats.add_parser('docbook'))
+ _build_cli_db_section(formats.add_parser('docbook-section'))
+ _build_cli_db_fragment(formats.add_parser('docbook-fragment'))
def run_cli(args: argparse.Namespace) -> None:
- if args.format == 'docbook':
- _run_cli_db(args)
+ if args.format == 'docbook-section':
+ _run_cli_db_section(args)
+ elif args.format == 'docbook-fragment':
+ _run_cli_db_fragment(args)
else:
raise RuntimeError('format not hooked up', args)
diff --git a/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/md.py b/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/md.py
index 5bc16e65933c..599ee7e91c14 100644
--- a/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/md.py
+++ b/pkgs/tools/nix/nixos-render-docs/src/nixos_render_docs/md.py
@@ -1,8 +1,9 @@
from abc import ABC
from collections.abc import Mapping, MutableMapping, Sequence
from frozendict import frozendict # type: ignore[attr-defined]
-from typing import Any, Callable, cast, Iterable, Optional
+from typing import Any, Callable, cast, get_args, Iterable, Literal, NoReturn, Optional
+import dataclasses
import re
from .types import RenderFn
@@ -27,9 +28,13 @@ _md_escape_table = {
def md_escape(s: str) -> str:
return s.translate(_md_escape_table)
+AttrBlockKind = Literal['admonition', 'example']
+
+AdmonitionKind = Literal["note", "caution", "tip", "important", "warning"]
+
class Renderer(markdown_it.renderer.RendererProtocol):
- _admonitions: dict[str, tuple[RenderFn, RenderFn]]
- _admonition_stack: list[str]
+ _admonitions: dict[AdmonitionKind, tuple[RenderFn, RenderFn]]
+ _admonition_stack: list[AdmonitionKind]
def __init__(self, manpage_urls: Mapping[str, str], parser: Optional[markdown_it.MarkdownIt] = None):
self._manpage_urls = manpage_urls
@@ -61,21 +66,24 @@ class Renderer(markdown_it.renderer.RendererProtocol):
'dd_open': self.dd_open,
'dd_close': self.dd_close,
'myst_role': self.myst_role,
- "container_admonition_open": self.admonition_open,
- "container_admonition_close": self.admonition_close,
- "inline_anchor": self.inline_anchor,
+ "admonition_open": self.admonition_open,
+ "admonition_close": self.admonition_close,
+ "attr_span_begin": self.attr_span_begin,
+ "attr_span_end": self.attr_span_end,
"heading_open": self.heading_open,
"heading_close": self.heading_close,
"ordered_list_open": self.ordered_list_open,
"ordered_list_close": self.ordered_list_close,
+ "example_open": self.example_open,
+ "example_close": self.example_close,
}
self._admonitions = {
- "{.note}": (self.note_open, self.note_close),
- "{.caution}": (self.caution_open,self.caution_close),
- "{.tip}": (self.tip_open, self.tip_close),
- "{.important}": (self.important_open, self.important_close),
- "{.warning}": (self.warning_open, self.warning_close),
+ "note": (self.note_open, self.note_close),
+ "caution": (self.caution_open,self.caution_close),
+ "tip": (self.tip_open, self.tip_close),
+ "important": (self.important_open, self.important_close),
+ "warning": (self.warning_open, self.warning_close),
}
self._admonition_stack = []
@@ -86,7 +94,7 @@ class Renderer(markdown_it.renderer.RendererProtocol):
def admonition_open(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
- tag = token.info.strip()
+ tag = token.meta['kind']
self._admonition_stack.append(tag)
return self._admonitions[tag][0](token, tokens, i, options, env)
def admonition_close(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
@@ -224,7 +232,10 @@ class Renderer(markdown_it.renderer.RendererProtocol):
def myst_role(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
raise RuntimeError("md token not supported", token)
- def inline_anchor(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ def attr_span_begin(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> str:
+ raise RuntimeError("md token not supported", token)
+ def attr_span_end(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
raise RuntimeError("md token not supported", token)
def heading_open(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
@@ -239,6 +250,12 @@ class Renderer(markdown_it.renderer.RendererProtocol):
def ordered_list_close(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
env: MutableMapping[str, Any]) -> str:
raise RuntimeError("md token not supported", token)
+ def example_open(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> str:
+ raise RuntimeError("md token not supported", token)
+ def example_close(self, token: Token, tokens: Sequence[Token], i: int, options: OptionsDict,
+ env: MutableMapping[str, Any]) -> str:
+ raise RuntimeError("md token not supported", token)
def _is_escaped(src: str, pos: int) -> bool:
found = 0
@@ -247,10 +264,44 @@ def _is_escaped(src: str, pos: int) -> bool:
pos -= 1
return found % 2 == 1
-_INLINE_ANCHOR_PATTERN = re.compile(r"\{\s*#([\w-]+)\s*\}")
+# the contents won't be split apart in the regex because spacing rules get messy here
+_ATTR_SPAN_PATTERN = re.compile(r"\{([^}]*)\}")
+# this one is for blocks with attrs. we want to use it with fullmatch() to deconstruct an info.
+_ATTR_BLOCK_PATTERN = re.compile(r"\s*\{([^}]*)\}\s*")
-def _inline_anchor_plugin(md: markdown_it.MarkdownIt) -> None:
- def inline_anchor(state: markdown_it.rules_inline.StateInline, silent: bool) -> bool:
+def _parse_attrs(s: str) -> Optional[tuple[Optional[str], list[str]]]:
+ (id, classes) = (None, [])
+ for part in s.split():
+ if part.startswith('#'):
+ if id is not None:
+ return None # just bail on multiple ids instead of trying to recover
+ id = part[1:]
+ elif part.startswith('.'):
+ classes.append(part[1:])
+ else:
+ return None # no support for key=value attrs like in pandoc
+
+ return (id, classes)
+
+def _parse_blockattrs(info: str) -> Optional[tuple[AttrBlockKind, Optional[str], list[str]]]:
+ if (m := _ATTR_BLOCK_PATTERN.fullmatch(info)) is None:
+ return None
+ if (parsed_attrs := _parse_attrs(m[1])) is None:
+ return None
+ id, classes = parsed_attrs
+ # check that we actually support this kind of block, and that is adheres to
+ # whetever restrictions we want to enforce for that kind of block.
+ if len(classes) == 1 and classes[0] in get_args(AdmonitionKind):
+ # don't want to support ids for admonitions just yet
+ if id is not None:
+ return None
+ return ('admonition', id, classes)
+ if classes == ['example']:
+ return ('example', id, classes)
+ return None
+
+def _attr_span_plugin(md: markdown_it.MarkdownIt) -> None:
+ def attr_span(state: markdown_it.rules_inline.StateInline, silent: bool) -> bool:
if state.src[state.pos] != '[':
return False
if _is_escaped(state.src, state.pos - 1):
@@ -263,24 +314,33 @@ def _inline_anchor_plugin(md: markdown_it.MarkdownIt) -> None:
if label_end < 0:
return False
- # match id
- match = _INLINE_ANCHOR_PATTERN.match(state.src[label_end + 1 : ])
+ # match id and classes in any combination
+ match = _ATTR_SPAN_PATTERN.match(state.src[label_end + 1 : ])
if not match:
return False
if not silent:
- token = state.push("inline_anchor", "", 0) # type: ignore[no-untyped-call]
- token.attrs['id'] = match[1]
+ if (parsed_attrs := _parse_attrs(match[1])) is None:
+ return False
+ id, classes = parsed_attrs
+
+ token = state.push("attr_span_begin", "span", 1) # type: ignore[no-untyped-call]
+ if id:
+ token.attrs['id'] = id
+ if classes:
+ token.attrs['class'] = " ".join(classes)
state.pos = label_begin
state.posMax = label_end
state.md.inline.tokenize(state)
+ state.push("attr_span_end", "span", -1) # type: ignore[no-untyped-call]
+
state.pos = label_end + match.end() + 1
state.posMax = input_end
return True
- md.inline.ruler.before("link", "inline_anchor", inline_anchor)
+ md.inline.ruler.before("link", "attr_span", attr_span)
def _inline_comment_plugin(md: markdown_it.MarkdownIt) -> None:
def inline_comment(state: markdown_it.rules_inline.StateInline, silent: bool) -> bool:
@@ -321,7 +381,78 @@ def _block_comment_plugin(md: markdown_it.MarkdownIt) -> None:
md.block.ruler.after("code", "block_comment", block_comment)
-_HEADER_ID_RE = re.compile(r"\s*\{\s*\#([\w-]+)\s*\}\s*$")
+_HEADER_ID_RE = re.compile(r"\s*\{\s*\#([\w.-]+)\s*\}\s*$")
+
+def _heading_ids(md: markdown_it.MarkdownIt) -> None:
+ def heading_ids(state: markdown_it.rules_core.StateCore) -> None:
+ tokens = state.tokens
+ # this is purposely simple and doesn't support classes or other kinds of attributes.
+ for (i, token) in enumerate(tokens):
+ if token.type == 'heading_open':
+ children = tokens[i + 1].children
+ assert children is not None
+ if len(children) == 0 or children[-1].type != 'text':
+ continue
+ if m := _HEADER_ID_RE.search(children[-1].content):
+ tokens[i].attrs['id'] = m[1]
+ children[-1].content = children[-1].content[:-len(m[0])].rstrip()
+
+ md.core.ruler.before("replacements", "heading_ids", heading_ids)
+
+def _compact_list_attr(md: markdown_it.MarkdownIt) -> None:
+ @dataclasses.dataclass
+ class Entry:
+ head: Token
+ end: int
+ compact: bool = True
+
+ def compact_list_attr(state: markdown_it.rules_core.StateCore) -> None:
+ # markdown-it signifies wide lists by setting the wrapper paragraphs
+ # of each item to hidden. this is not useful for our stylesheets, which
+ # signify this with a special css class on list elements instead.
+ stack = []
+ for token in state.tokens:
+ if token.type in [ 'bullet_list_open', 'ordered_list_open' ]:
+ stack.append(Entry(token, cast(int, token.attrs.get('start', 1))))
+ elif token.type in [ 'bullet_list_close', 'ordered_list_close' ]:
+ lst = stack.pop()
+ lst.head.meta['compact'] = lst.compact
+ if token.type == 'ordered_list_close':
+ lst.head.meta['end'] = lst.end - 1
+ elif len(stack) > 0 and token.type == 'paragraph_open' and not token.hidden:
+ stack[-1].compact = False
+ elif token.type == 'list_item_open':
+ stack[-1].end += 1
+
+ md.core.ruler.push("compact_list_attr", compact_list_attr)
+
+def _block_attr(md: markdown_it.MarkdownIt) -> None:
+ def assert_never(value: NoReturn) -> NoReturn:
+ assert False
+
+ def block_attr(state: markdown_it.rules_core.StateCore) -> None:
+ stack = []
+ for token in state.tokens:
+ if token.type == 'container_blockattr_open':
+ if (parsed_attrs := _parse_blockattrs(token.info)) is None:
+ # if we get here we've missed a possible case in the plugin validate function
+ raise RuntimeError("this should be unreachable")
+ kind, id, classes = parsed_attrs
+ if kind == 'admonition':
+ token.type = 'admonition_open'
+ token.meta['kind'] = classes[0]
+ stack.append('admonition_close')
+ elif kind == 'example':
+ token.type = 'example_open'
+ if id is not None:
+ token.attrs['id'] = id
+ stack.append('example_close')
+ else:
+ assert_never(kind)
+ elif token.type == 'container_blockattr_close':
+ token.type = stack.pop()
+
+ md.core.ruler.push("block_attr", block_attr)
class Converter(ABC):
__renderer__: Callable[[Mapping[str, str], markdown_it.MarkdownIt], Renderer]
@@ -340,56 +471,21 @@ class Converter(ABC):
)
self._md.use(
container_plugin,
- name="admonition",
- validate=lambda name, *args: (
- name.strip() in self._md.renderer._admonitions # type: ignore[attr-defined]
- )
+ name="blockattr",
+ validate=lambda name, *args: _parse_blockattrs(name),
)
self._md.use(deflist_plugin)
self._md.use(myst_role_plugin)
- self._md.use(_inline_anchor_plugin)
+ self._md.use(_attr_span_plugin)
self._md.use(_inline_comment_plugin)
self._md.use(_block_comment_plugin)
+ self._md.use(_heading_ids)
+ self._md.use(_compact_list_attr)
+ self._md.use(_block_attr)
self._md.enable(["smartquotes", "replacements"])
- def _post_parse(self, tokens: list[Token]) -> list[Token]:
- for i in range(0, len(tokens)):
- # parse header IDs. this is purposely simple and doesn't support
- # classes or other inds of attributes.
- if tokens[i].type == 'heading_open':
- children = tokens[i + 1].children
- assert children is not None
- if len(children) == 0 or children[-1].type != 'text':
- continue
- if m := _HEADER_ID_RE.search(children[-1].content):
- tokens[i].attrs['id'] = m[1]
- children[-1].content = children[-1].content[:-len(m[0])].rstrip()
-
- # markdown-it signifies wide lists by setting the wrapper paragraphs
- # of each item to hidden. this is not useful for our stylesheets, which
- # signify this with a special css class on list elements instead.
- wide_stack = []
- end_stack = []
- for i in range(0, len(tokens)):
- if tokens[i].type in [ 'bullet_list_open', 'ordered_list_open' ]:
- wide_stack.append([i, True])
- end_stack.append([i, cast(int, tokens[i].attrs.get('start', 1))])
- elif tokens[i].type in [ 'bullet_list_close', 'ordered_list_close' ]:
- (idx, compact) = wide_stack.pop()
- tokens[idx].meta['compact'] = compact
- (idx, end) = end_stack.pop()
- if tokens[i].type == 'ordered_list_close':
- tokens[idx].meta['end'] = end - 1
- elif len(wide_stack) > 0 and tokens[i].type == 'paragraph_open' and not tokens[i].hidden:
- wide_stack[-1][1] = False
- elif tokens[i].type == 'list_item_open':
- end_stack[-1][1] += 1
-
- return tokens
-
def _parse(self, src: str, env: Optional[MutableMapping[str, Any]] = None) -> list[Token]:
- tokens = self._md.parse(src, env if env is not None else {})
- return self._post_parse(tokens)
+ return self._md.parse(src, env if env is not None else {})
def _render(self, src: str, env: Optional[MutableMapping[str, Any]] = None) -> str:
env = {} if env is None else env
diff --git a/pkgs/tools/nix/nixos-render-docs/src/tests/test_plugins.py b/pkgs/tools/nix/nixos-render-docs/src/tests/test_plugins.py
index 4efcb9bdfc73..1d836a916d96 100644
--- a/pkgs/tools/nix/nixos-render-docs/src/tests/test_plugins.py
+++ b/pkgs/tools/nix/nixos-render-docs/src/tests/test_plugins.py
@@ -6,7 +6,7 @@ class Converter(nixos_render_docs.md.Converter):
# actual renderer doesn't matter, we're just parsing.
__renderer__ = nixos_render_docs.docbook.DocBookRenderer
-def test_inline_anchor_simple() -> None:
+def test_attr_span_parsing() -> None:
c = Converter({})
assert c._parse("[]{#test}") == [
Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
@@ -14,14 +14,71 @@ def test_inline_anchor_simple() -> None:
Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1, content='[]{#test}',
markup='', info='', meta={}, block=True, hidden=False,
children=[
- Token(type='inline_anchor', tag='', nesting=0, attrs={'id': 'test'}, map=None, level=0,
+ Token(type='attr_span_begin', tag='span', nesting=1, attrs={'id': 'test'}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=0,
children=None, content='', markup='', info='', meta={}, block=False, hidden=False)
]),
Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0,
children=None, content='', markup='', info='', meta={}, block=True, hidden=False)
]
+ assert c._parse("[]{.test}") == [
+ Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
+ content='', markup='', info='', meta={}, block=True, hidden=False),
+ Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1, content='[]{.test}',
+ markup='', info='', meta={}, block=True, hidden=False,
+ children=[
+ Token(type='attr_span_begin', tag='span', nesting=1, attrs={'class': 'test'}, map=None,
+ level=0, children=None, content='', markup='', info='', meta={}, block=False,
+ hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False)
+ ]),
+ Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("[]{.test1 .test2 #foo .test3 .test4}") == [
+ Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
+ content='', markup='', info='', meta={}, block=True, hidden=False),
+ Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1,
+ content='[]{.test1 .test2 #foo .test3 .test4}',
+ markup='', info='', meta={}, block=True, hidden=False,
+ children=[
+ Token(type='attr_span_begin', tag='span', nesting=1,
+ attrs={'class': 'test1 test2 test3 test4', 'id': 'foo'}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False)
+ ]),
+ Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("[]{#a #a}") == [
+ Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
+ content='', markup='', info='', meta={}, block=True, hidden=False),
+ Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1,
+ content='[]{#a #a}', markup='', info='', meta={}, block=True, hidden=False,
+ children=[
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
+ content='[]{#a #a}', markup='', info='', meta={}, block=False, hidden=False)
+ ]),
+ Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0, children=None,
+ content='', markup='', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("[]{foo}") == [
+ Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
+ content='', markup='', info='', meta={}, block=True, hidden=False),
+ Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1,
+ content='[]{foo}', markup='', info='', meta={}, block=True, hidden=False,
+ children=[
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
+ content='[]{foo}', markup='', info='', meta={}, block=False, hidden=False)
+ ]),
+ Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0, children=None,
+ content='', markup='', info='', meta={}, block=True, hidden=False)
+ ]
-def test_inline_anchor_formatted() -> None:
+def test_attr_span_formatted() -> None:
c = Converter({})
assert c._parse("a[b c `d` ***e***]{#test}f") == [
Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0,
@@ -31,28 +88,30 @@ def test_inline_anchor_formatted() -> None:
children=[
Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0,
children=None, content='a', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='inline_anchor', tag='', nesting=0, attrs={'id': 'test'}, map=None, level=0,
+ Token(type='attr_span_begin', tag='span', nesting=1, attrs={'id': 'test'}, map=None, level=0,
children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
- content='b c ', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='code_inline', tag='code', nesting=0, attrs={}, map=None, level=0,
- children=None, content='d', markup='`', info='', meta={}, block=False, hidden=False),
- Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
- content=' ', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='em_open', tag='em', nesting=1, attrs={}, map=None, level=0, children=None,
- content='', markup='*', info='', meta={}, block=False, hidden=False),
Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
+ content='b c ', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='code_inline', tag='code', nesting=0, attrs={}, map=None, level=1,
+ children=None, content='d', markup='`', info='', meta={}, block=False, hidden=False),
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
+ content=' ', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='em_open', tag='em', nesting=1, attrs={}, map=None, level=1, children=None,
+ content='', markup='*', info='', meta={}, block=False, hidden=False),
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=2, children=None,
content='', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='strong_open', tag='strong', nesting=1, attrs={}, map=None, level=1,
+ Token(type='strong_open', tag='strong', nesting=1, attrs={}, map=None, level=2,
+ children=None, content='', markup='**', info='', meta={}, block=False, hidden=False),
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=3, children=None,
+ content='e', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='strong_close', tag='strong', nesting=-1, attrs={}, map=None, level=2,
children=None, content='', markup='**', info='', meta={}, block=False, hidden=False),
Token(type='text', tag='', nesting=0, attrs={}, map=None, level=2, children=None,
- content='e', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='strong_close', tag='strong', nesting=-1, attrs={}, map=None, level=1,
- children=None, content='', markup='**', info='', meta={}, block=False, hidden=False),
- Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
content='', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='em_close', tag='em', nesting=-1, attrs={}, map=None, level=0, children=None,
+ Token(type='em_close', tag='em', nesting=-1, attrs={}, map=None, level=1, children=None,
content='', markup='*', info='', meta={}, block=False, hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
content='f', markup='', info='', meta={}, block=False, hidden=False)
]),
@@ -60,7 +119,7 @@ def test_inline_anchor_formatted() -> None:
content='', markup='', info='', meta={}, block=True, hidden=False)
]
-def test_inline_anchor_in_heading() -> None:
+def test_attr_span_in_heading() -> None:
c = Converter({})
# inline anchors in headers are allowed, but header attributes should be preferred
assert c._parse("# foo []{#bar} baz") == [
@@ -71,8 +130,10 @@ def test_inline_anchor_in_heading() -> None:
children=[
Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
content='foo ', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='inline_anchor', tag='', nesting=0, attrs={'id': 'bar'}, map=None, level=0,
+ Token(type='attr_span_begin', tag='span', nesting=1, attrs={'id': 'bar'}, map=None, level=0,
children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
content=' baz', markup='', info='', meta={}, block=False, hidden=False)
]),
@@ -80,7 +141,7 @@ def test_inline_anchor_in_heading() -> None:
content='', markup='#', info='', meta={}, block=True, hidden=False)
]
-def test_inline_anchor_on_links() -> None:
+def test_attr_span_on_links() -> None:
c = Converter({})
assert c._parse("[ [a](#bar) ]{#foo}") == [
Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
@@ -88,24 +149,26 @@ def test_inline_anchor_on_links() -> None:
Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1, content='[ [a](#bar) ]{#foo}',
markup='', info='', meta={}, block=True, hidden=False,
children=[
- Token(type='inline_anchor', tag='', nesting=0, attrs={'id': 'foo'}, map=None, level=0,
- children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
- content=' ', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='link_open', tag='a', nesting=1, attrs={'href': '#bar'}, map=None, level=0,
+ Token(type='attr_span_begin', tag='span', nesting=1, attrs={'id': 'foo'}, map=None, level=0,
children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
+ content=' ', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='link_open', tag='a', nesting=1, attrs={'href': '#bar'}, map=None, level=1,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=2, children=None,
content='a', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='link_close', tag='a', nesting=-1, attrs={}, map=None, level=0, children=None,
+ Token(type='link_close', tag='a', nesting=-1, attrs={}, map=None, level=1, children=None,
content='', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
- content=' ', markup='', info='', meta={}, block=False, hidden=False)
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
+ content=' ', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False)
]),
Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0, children=None,
content='', markup='', info='', meta={}, block=True, hidden=False)
]
-def test_inline_anchor_nested() -> None:
+def test_attr_span_nested() -> None:
# inline anchors may contain more anchors (even though this is a bit pointless)
c = Converter({})
assert c._parse("[ [a]{#bar} ]{#foo}") == [
@@ -114,20 +177,26 @@ def test_inline_anchor_nested() -> None:
Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1,
content='[ [a]{#bar} ]{#foo}', markup='', info='', meta={}, block=True, hidden=False,
children=[
- Token(type='inline_anchor', tag='', nesting=0, attrs={'id': 'foo'}, map=None, level=0,
+ Token(type='attr_span_begin', tag='span', nesting=1, attrs={'id': 'foo'}, map=None, level=0,
children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
content=' ', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='inline_anchor', tag='', nesting=0, attrs={'id': 'bar'}, map=None, level=0,
+ Token(type='attr_span_begin', tag='span', nesting=1, attrs={'id': 'bar'}, map=None, level=1,
children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
- content='a ', markup='', info='', meta={}, block=False, hidden=False)
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=2, children=None,
+ content='a', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=1,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
+ content=' ', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False)
]),
Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0, children=None,
content='', markup='', info='', meta={}, block=True, hidden=False)
]
-def test_inline_anchor_escaping() -> None:
+def test_attr_span_escaping() -> None:
c = Converter({})
assert c._parse("\\[a]{#bar}") == [
Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
@@ -149,10 +218,12 @@ def test_inline_anchor_escaping() -> None:
children=[
Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
content='\\', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='inline_anchor', tag='', nesting=0, attrs={'id': 'bar'}, map=None, level=0,
+ Token(type='attr_span_begin', tag='span', nesting=1, attrs={'id': 'bar'}, map=None, level=0,
children=None, content='', markup='', info='', meta={}, block=False, hidden=False),
- Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
- content='a', markup='', info='', meta={}, block=False, hidden=False)
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
+ content='a', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='attr_span_end', tag='span', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup='', info='', meta={}, block=False, hidden=False)
]),
Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0, children=None,
content='', markup='', info='', meta={}, block=True, hidden=False)
@@ -277,3 +348,105 @@ def test_block_comment() -> None:
assert c._parse("") == []
assert c._parse("") == []
assert c._parse("") == []
+
+def test_heading_attributes() -> None:
+ c = Converter({})
+ assert c._parse("# foo *bar* {#hid}") == [
+ Token(type='heading_open', tag='h1', nesting=1, attrs={'id': 'hid'}, map=[0, 1], level=0,
+ children=None, content='', markup='#', info='', meta={}, block=True, hidden=False),
+ Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1,
+ content='foo *bar* {#hid}', markup='', info='', meta={}, block=True, hidden=False,
+ children=[
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
+ content='foo ', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='em_open', tag='em', nesting=1, attrs={}, map=None, level=0, children=None,
+ content='', markup='*', info='', meta={}, block=False, hidden=False),
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=1, children=None,
+ content='bar', markup='', info='', meta={}, block=False, hidden=False),
+ Token(type='em_close', tag='em', nesting=-1, attrs={}, map=None, level=0, children=None,
+ content='', markup='*', info='', meta={}, block=False, hidden=False),
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
+ content='', markup='', info='', meta={}, block=False, hidden=False)
+ ]),
+ Token(type='heading_close', tag='h1', nesting=-1, attrs={}, map=None, level=0, children=None,
+ content='', markup='#', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("# foo--bar {#id-with--double-dashes}") == [
+ Token(type='heading_open', tag='h1', nesting=1, attrs={'id': 'id-with--double-dashes'}, map=[0, 1],
+ level=0, children=None, content='', markup='#', info='', meta={}, block=True, hidden=False),
+ Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1,
+ content='foo--bar {#id-with--double-dashes}', markup='', info='', meta={}, block=True,
+ hidden=False,
+ children=[
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
+ content='foo–bar', markup='', info='', meta={}, block=False, hidden=False)
+ ]),
+ Token(type='heading_close', tag='h1', nesting=-1, attrs={}, map=None, level=0, children=None,
+ content='', markup='#', info='', meta={}, block=True, hidden=False)
+ ]
+
+def test_admonitions() -> None:
+ c = Converter({})
+ assert c._parse("::: {.note}") == [
+ Token(type='admonition_open', tag='div', nesting=1, attrs={}, map=[0, 1], level=0,
+ children=None, content='', markup=':::', info=' {.note}', meta={'kind': 'note'}, block=True,
+ hidden=False),
+ Token(type='admonition_close', tag='div', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup=':::', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("::: {.caution}") == [
+ Token(type='admonition_open', tag='div', nesting=1, attrs={}, map=[0, 1], level=0,
+ children=None, content='', markup=':::', info=' {.caution}', meta={'kind': 'caution'},
+ block=True, hidden=False),
+ Token(type='admonition_close', tag='div', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup=':::', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("::: {.tip}") == [
+ Token(type='admonition_open', tag='div', nesting=1, attrs={}, map=[0, 1], level=0,
+ children=None, content='', markup=':::', info=' {.tip}', meta={'kind': 'tip'}, block=True,
+ hidden=False),
+ Token(type='admonition_close', tag='div', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup=':::', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("::: {.important}") == [
+ Token(type='admonition_open', tag='div', nesting=1, attrs={}, map=[0, 1], level=0,
+ children=None, content='', markup=':::', info=' {.important}', meta={'kind': 'important'},
+ block=True, hidden=False),
+ Token(type='admonition_close', tag='div', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup=':::', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("::: {.warning}") == [
+ Token(type='admonition_open', tag='div', nesting=1, attrs={}, map=[0, 1], level=0,
+ children=None, content='', markup=':::', info=' {.warning}', meta={'kind': 'warning'},
+ block=True, hidden=False),
+ Token(type='admonition_close', tag='div', nesting=-1, attrs={}, map=None, level=0,
+ children=None, content='', markup=':::', info='', meta={}, block=True, hidden=False)
+ ]
+
+def test_example() -> None:
+ c = Converter({})
+ assert c._parse("::: {.example}") == [
+ Token(type='example_open', tag='div', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
+ content='', markup=':::', info=' {.example}', meta={}, block=True, hidden=False),
+ Token(type='example_close', tag='div', nesting=-1, attrs={}, map=None, level=0, children=None,
+ content='', markup=':::', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("::: {#eid .example}") == [
+ Token(type='example_open', tag='div', nesting=1, attrs={'id': 'eid'}, map=[0, 1], level=0,
+ children=None, content='', markup=':::', info=' {#eid .example}', meta={}, block=True,
+ hidden=False),
+ Token(type='example_close', tag='div', nesting=-1, attrs={}, map=None, level=0, children=None,
+ content='', markup=':::', info='', meta={}, block=True, hidden=False)
+ ]
+ assert c._parse("::: {.example .note}") == [
+ Token(type='paragraph_open', tag='p', nesting=1, attrs={}, map=[0, 1], level=0, children=None,
+ content='', markup='', info='', meta={}, block=True, hidden=False),
+ Token(type='inline', tag='', nesting=0, attrs={}, map=[0, 1], level=1,
+ content='::: {.example .note}', markup='', info='', meta={}, block=True, hidden=False,
+ children=[
+ Token(type='text', tag='', nesting=0, attrs={}, map=None, level=0, children=None,
+ content='::: {.example .note}', markup='', info='', meta={}, block=False, hidden=False)
+ ]),
+ Token(type='paragraph_close', tag='p', nesting=-1, attrs={}, map=None, level=0, children=None,
+ content='', markup='', info='', meta={}, block=True, hidden=False)
+ ]
diff --git a/pkgs/tools/security/gotrue/supabase.nix b/pkgs/tools/security/gotrue/supabase.nix
index 46d296453f7d..0f1b461b9289 100644
--- a/pkgs/tools/security/gotrue/supabase.nix
+++ b/pkgs/tools/security/gotrue/supabase.nix
@@ -1,14 +1,19 @@
-{ lib, buildGoModule, fetchFromGitHub }:
+{ lib
+, buildGoModule
+, fetchFromGitHub
+, testers
+, gotrue-supabase
+}:
buildGoModule rec {
pname = "gotrue";
- version = "2.44.0";
+ version = "2.47.0";
src = fetchFromGitHub {
owner = "supabase";
repo = pname;
rev = "v${version}";
- hash = "sha256-LSA6h6hs5M80urBasVDWZSCNA3fWxjYjvbPRbHLOX0Y=";
+ hash = "sha256-ww3tiIIn2Vwhwa5IgkrybnWQQ3beihQhZzB1ysz4y1k=";
};
vendorHash = "sha256-FIl30sKmdcXayK8KWGFl+N+lYExl4ibKZ2tcvelw8zo=";
@@ -16,12 +21,18 @@ buildGoModule rec {
ldflags = [
"-s"
"-w"
- "-X=github.com/netlify/gotrue/utilities.Version=${version}"
+ "-X=github.com/netlify/gotrue/internal/utilities.Version=${version}"
];
# integration tests require network to connect to postgres database
doCheck = false;
+ passthru.tests.version = testers.testVersion {
+ package = gotrue-supabase;
+ command = "gotrue version";
+ inherit version;
+ };
+
meta = with lib; {
homepage = "https://github.com/supabase/gotrue";
description = "A JWT based API for managing users and issuing JWT tokens";
diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index a09a24453d8b..9bd7c40e5ac6 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -13089,8 +13089,7 @@ with pkgs;
watchlog = callPackage ../tools/misc/watchlog { };
watchman = callPackage ../development/tools/watchman {
- inherit (darwin.apple_sdk.frameworks) CoreServices;
- autoconf = buildPackages.autoconf269;
+ inherit (darwin.apple_sdk_11_0.frameworks) CoreServices;
};
wavefunctioncollapse = callPackage ../tools/graphics/wavefunctioncollapse {};
@@ -19455,6 +19454,8 @@ with pkgs;
editline = callPackage ../development/libraries/editline { };
+ edencommon = callPackage ../development/libraries/edencommon { };
+
eigen = callPackage ../development/libraries/eigen {};
eigen2 = callPackage ../development/libraries/eigen/2.0.nix {};
@@ -19529,6 +19530,10 @@ with pkgs;
autoreconfHook = buildPackages.autoreconfHook269;
};
+ fbthrift = callPackage ../development/libraries/fbthrift { };
+
+ fb303 = callPackage ../development/libraries/fb303 { };
+
fcgi = callPackage ../development/libraries/fcgi { };
fcl = callPackage ../development/libraries/fcl { };
@@ -19595,6 +19600,8 @@ with pkgs;
filtron = callPackage ../servers/filtron { };
+ fizz = callPackage ../development/libraries/fizz { };
+
flann = callPackage ../development/libraries/flann { };
flatcc = callPackage ../development/libraries/flatcc { };
@@ -23652,6 +23659,8 @@ with pkgs;
wally-cli = callPackage ../development/tools/wally-cli { };
zsa-udev-rules = callPackage ../os-specific/linux/zsa-udev-rules { };
+ wangle = callPackage ../development/libraries/wangle { };
+
wavpack = callPackage ../development/libraries/wavpack { };
wayland = callPackage ../development/libraries/wayland { };
diff --git a/pkgs/top-level/php-packages.nix b/pkgs/top-level/php-packages.nix
index 827985cab7e5..3f1aa277de99 100644
--- a/pkgs/top-level/php-packages.nix
+++ b/pkgs/top-level/php-packages.nix
@@ -57,15 +57,22 @@ lib.makeScope pkgs.newScope (self: with self; {
# Wrap mkDerivation to prepend pname with "php-" to make names consistent
# with how buildPecl does it and make the file easier to overview.
- mkDerivation = { pname, ... }@args: pkgs.stdenv.mkDerivation (args // {
- pname = "php-${pname}";
- passthru = {
- updateScript = nix-update-script {};
- };
- meta = args.meta // {
- mainProgram = args.meta.mainProgram or pname;
- };
- });
+ mkDerivation = origArgs:
+ let
+ args = lib.fix (lib.extends
+ (_: previousAttrs: {
+ pname = "php-${previousAttrs.pname}";
+ passthru = (previousAttrs.passthru or { }) // {
+ updateScript = nix-update-script { };
+ };
+ meta = (previousAttrs.meta or { }) // {
+ mainProgram = previousAttrs.meta.mainProgram or previousAttrs.pname;
+ };
+ })
+ (if lib.isFunction origArgs then origArgs else (_: origArgs))
+ );
+ in
+ pkgs.stdenv.mkDerivation args;
# Function to build an extension which is shipped as part of the php
# source, based on the php version.
@@ -84,7 +91,6 @@ lib.makeScope pkgs.newScope (self: with self; {
, zendExtension ? false
, doCheck ? true
, extName ? name
- , allowLocalNetworking ? false
, ...
}@args: stdenv.mkDerivation ((builtins.removeAttrs args [ "name" ]) // {
pname = "php-${name}";
@@ -104,7 +110,6 @@ lib.makeScope pkgs.newScope (self: with self; {
];
inherit configureFlags internalDeps buildInputs zendExtension doCheck;
- __darwinAllowLocalNetworking = allowLocalNetworking;
preConfigurePhases = [
"cdToExtensionRootPhase"
@@ -413,8 +418,17 @@ lib.makeScope pkgs.newScope (self: with self; {
valgrind.dev
];
zendExtension = true;
+ postPatch = lib.optionalString stdenv.isDarwin ''
+ # Tests are flaky on darwin
+ rm ext/opcache/tests/blacklist.phpt
+ rm ext/opcache/tests/bug66338.phpt
+ rm ext/opcache/tests/bug78106.phpt
+ rm ext/opcache/tests/issue0115.phpt
+ rm ext/opcache/tests/issue0149.phpt
+ rm ext/opcache/tests/revalidate_path_01.phpt
+ '';
# Tests launch the builtin webserver.
- allowLocalNetworking = true;
+ __darwinAllowLocalNetworking = true;
}
{
name = "openssl";