alioth/nixpkgs
3
0
Fork 0
forked from mirrors/nixpkgs
Code Releases Activity
nixpkgs/nixos/doc/manual/release-notes/rl-2111.section.md
github-actions[bot] 79a728d821
Merge staging-next into staging
2021-09-14 00:01:57 +00:00

22 KiB
Raw Blame History

Release 21.11 (“?”, 2021.11/??)

In addition to numerous new and upgraded packages, this release has the following highlights:

  • Support is planned until the end of June 2022, handing over to 22.05.

Highlights

  • 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.

  • Activation scripts can now opt int to be run when running nixos-rebuild dry-activate and 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.

  • bash now defaults to major version 5.

  • Systemd was updated to version 249 (from 247).

New Services

  • navidrome, a personal music streaming server with subsonic-compatible api. Available as navidrome.

Backward Incompatibilities

  • 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-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.0

  • 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 it's 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.

  • 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 6.5.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.

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.

  • 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.

  • 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 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 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.iwd module has a new networking.wireless.iwd.settings option.

  • 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.