···11+<section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-release-21.05">
22+ <title>Release 21.05 (<quote>Okapi</quote>, 2021.05/31)</title>
33+ <para>
44+ Support is planned until the end of December 2021, handing over to
55+ 21.11.
66+ </para>
77+ <section xml:id="sec-release-21.05-highlights">
88+ <title>Highlights</title>
99+ <para>
1010+ In addition to numerous new and upgraded packages, this release
1111+ has the following highlights:
1212+ </para>
1313+ <itemizedlist>
1414+ <listitem>
1515+ <para>
1616+ Core version changes:
1717+ </para>
1818+ <itemizedlist>
1919+ <listitem>
2020+ <para>
2121+ gcc: 9.3.0 -> 10.3.0
2222+ </para>
2323+ </listitem>
2424+ <listitem>
2525+ <para>
2626+ glibc: 2.30 -> 2.32
2727+ </para>
2828+ </listitem>
2929+ <listitem>
3030+ <para>
3131+ default linux: 5.4 -> 5.10, all supported kernels
3232+ available
3333+ </para>
3434+ </listitem>
3535+ <listitem>
3636+ <para>
3737+ mesa: 20.1.7 -> 21.0.1
3838+ </para>
3939+ </listitem>
4040+ </itemizedlist>
4141+ </listitem>
4242+ <listitem>
4343+ <para>
4444+ Desktop Environments:
4545+ </para>
4646+ <itemizedlist>
4747+ <listitem>
4848+ <para>
4949+ GNOME: 3.36 -> 40, see its
5050+ <link xlink:href="https://help.gnome.org/misc/release-notes/40.0/">release
5151+ notes</link>
5252+ </para>
5353+ </listitem>
5454+ <listitem>
5555+ <para>
5656+ Plasma5: 5.18.5 -> 5.21.3
5757+ </para>
5858+ </listitem>
5959+ <listitem>
6060+ <para>
6161+ kdeApplications: 20.08.1 -> 20.12.3
6262+ </para>
6363+ </listitem>
6464+ <listitem>
6565+ <para>
6666+ cinnamon: 4.6 -> 4.8.1
6767+ </para>
6868+ </listitem>
6969+ </itemizedlist>
7070+ </listitem>
7171+ <listitem>
7272+ <para>
7373+ Programming Languages and Frameworks:
7474+ </para>
7575+ <itemizedlist spacing="compact">
7676+ <listitem>
7777+ <para>
7878+ Python optimizations were disabled again. Builds with
7979+ optimizations enabled are not reproducible. Optimizations
8080+ can now be enabled with an option.
8181+ </para>
8282+ </listitem>
8383+ </itemizedlist>
8484+ </listitem>
8585+ <listitem>
8686+ <para>
8787+ The linux_latest kernel was updated to the 5.12 series. It
8888+ currently is not officially supported for use with the zfs
8989+ filesystem. If you use zfs, you should use a different kernel
9090+ version (either the LTS kernel, or track a specific one).
9191+ </para>
9292+ </listitem>
9393+ </itemizedlist>
9494+ </section>
9595+ <section xml:id="sec-release-21.05-new-services">
9696+ <title>New Services</title>
9797+ <para>
9898+ The following new services were added since the last release:
9999+ </para>
100100+ <itemizedlist>
101101+ <listitem>
102102+ <para>
103103+ <link xlink:href="https://www.gnuradio.org/">GNURadio</link>
104104+ 3.8 was
105105+ <link xlink:href="https://github.com/NixOS/nixpkgs/issues/82263">finally</link>
106106+ packaged, along with a rewrite to the Nix expressions,
107107+ allowing users to override the features upstream supports
108108+ selecting to compile or not to. Additionally, the attribute
109109+ <literal>gnuradio</literal> and <literal>gnuradio3_7</literal>
110110+ now point to an externally wrapped by default derivations,
111111+ that allow you to also add `extraPythonPackages` to the Python
112112+ interpreter used by GNURadio. Missing environmental variables
113113+ needed for operational GUI were also added
114114+ (<link xlink:href="https://github.com/NixOS/nixpkgs/issues/75478">#75478</link>).
115115+ </para>
116116+ </listitem>
117117+ <listitem>
118118+ <para>
119119+ <link xlink:href="https://www.keycloak.org/">Keycloak</link>,
120120+ an open source identity and access management server with
121121+ support for
122122+ <link xlink:href="https://openid.net/connect/">OpenID
123123+ Connect</link>, <link xlink:href="https://oauth.net/2/">OAUTH
124124+ 2.0</link> and
125125+ <link xlink:href="https://en.wikipedia.org/wiki/SAML_2.0">SAML
126126+ 2.0</link>.
127127+ </para>
128128+ <para>
129129+ See the <link linkend="module-services-keycloak">Keycloak
130130+ section of the NixOS manual</link> for more information.
131131+ </para>
132132+ </listitem>
133133+ <listitem>
134134+ <para>
135135+ <link xlink:href="options.html#opt-services.samba-wsdd.enable">services.samba-wsdd.enable</link>
136136+ Web Services Dynamic Discovery host daemon
137137+ </para>
138138+ </listitem>
139139+ <listitem>
140140+ <para>
141141+ <link xlink:href="https://www.discourse.org/">Discourse</link>,
142142+ a modern and open source discussion platform.
143143+ </para>
144144+ <para>
145145+ See the <link linkend="module-services-discourse">Discourse
146146+ section of the NixOS manual</link> for more information.
147147+ </para>
148148+ </listitem>
149149+ <listitem>
150150+ <para>
151151+ <link xlink:href="options.html#opt-services.nebula.networks">services.nebula.networks</link>
152152+ <link xlink:href="https://github.com/slackhq/nebula">Nebula
153153+ VPN</link>
154154+ </para>
155155+ </listitem>
156156+ </itemizedlist>
157157+ </section>
158158+ <section xml:id="sec-release-21.05-incompatibilities">
159159+ <title>Backward Incompatibilities</title>
160160+ <para>
161161+ When upgrading from a previous release, please be aware of the
162162+ following incompatible changes:
163163+ </para>
164164+ <itemizedlist>
165165+ <listitem>
166166+ <para>
167167+ GNOME desktop environment was upgraded to 40, see the release
168168+ notes for
169169+ <link xlink:href="https://help.gnome.org/misc/release-notes/40.0/">40.0</link>
170170+ and
171171+ <link xlink:href="https://help.gnome.org/misc/release-notes/3.38/">3.38</link>.
172172+ The <literal>gnome3</literal> attribute set has been renamed
173173+ to <literal>gnome</literal> and so have been the NixOS
174174+ options.
175175+ </para>
176176+ </listitem>
177177+ <listitem>
178178+ <para>
179179+ If you are using <literal>services.udev.extraRules</literal>
180180+ to assign custom names to network interfaces, this may stop
181181+ working due to a change in the initialisation of dhcpcd and
182182+ systemd networkd. To avoid this, either move them to
183183+ <literal>services.udev.initrdRules</literal> or see the new
184184+ <link linkend="sec-custom-ifnames">Assigning custom
185185+ names</link> section of the NixOS manual for an example using
186186+ networkd links.
187187+ </para>
188188+ </listitem>
189189+ <listitem>
190190+ <para>
191191+ The <literal>security.hideProcessInformation</literal> module
192192+ has been removed. It was broken since the switch to
193193+ cgroups-v2.
194194+ </para>
195195+ </listitem>
196196+ <listitem>
197197+ <para>
198198+ The <literal>linuxPackages.ati_drivers_x11</literal> kernel
199199+ modules have been removed. The drivers only supported kernels
200200+ prior to 4.2, and thus have become obsolete.
201201+ </para>
202202+ </listitem>
203203+ <listitem>
204204+ <para>
205205+ The <literal>systemConfig</literal> kernel parameter is no
206206+ longer added to boot loader entries. It has been unused since
207207+ September 2010, but if do have a system generation from that
208208+ era, you will now be unable to boot into them.
209209+ </para>
210210+ </listitem>
211211+ <listitem>
212212+ <para>
213213+ <literal>systemd-journal2gelf</literal> no longer parses json
214214+ and expects the receiving system to handle it. How to achieve
215215+ this with Graylog is described in this
216216+ <link xlink:href="https://github.com/parse-nl/SystemdJournal2Gelf/issues/10">GitHub
217217+ issue</link>.
218218+ </para>
219219+ </listitem>
220220+ <listitem>
221221+ <para>
222222+ If the <literal>services.dbus</literal> module is enabled,
223223+ then the user D-Bus session is now always socket activated.
224224+ The associated options
225225+ <literal>services.dbus.socketActivated</literal> and
226226+ <literal>services.xserver.startDbusSession</literal> have
227227+ therefore been removed and you will receive a warning if they
228228+ are present in your configuration. This change makes the user
229229+ D-Bus session available also for non-graphical logins.
230230+ </para>
231231+ </listitem>
232232+ <listitem>
233233+ <para>
234234+ The <literal>networking.wireless.iwd</literal> module now
235235+ installs the upstream-provided 80-iwd.link file, which sets
236236+ the NamePolicy= for all wlan devices to "keep
237237+ kernel", to avoid race conditions between iwd and
238238+ networkd. If you don't want this, you can set
239239+ <literal>systemd.network.links."80-iwd" = lib.mkForce {}</literal>.
240240+ </para>
241241+ </listitem>
242242+ <listitem>
243243+ <para>
244244+ <literal>rubyMinimal</literal> was removed due to being unused
245245+ and unusable. The default ruby interpreter includes JIT
246246+ support, which makes it reference it's compiler. Since JIT
247247+ support is probably needed by some Gems, it was decided to
248248+ enable this feature with all cc references by default, and
249249+ allow to build a Ruby derivation without references to cc, by
250250+ setting <literal>jitSupport = false;</literal> in an overlay.
251251+ See
252252+ <link xlink:href="https://github.com/NixOS/nixpkgs/pull/90151">#90151</link>
253253+ for more info.
254254+ </para>
255255+ </listitem>
256256+ <listitem>
257257+ <para>
258258+ Setting
259259+ <literal>services.openssh.authorizedKeysFiles</literal> now
260260+ also affects which keys
261261+ <literal>security.pam.enableSSHAgentAuth</literal> will use.
262262+ WARNING: If you are using these options in combination do make
263263+ sure that any key paths you use are present in
264264+ <literal>services.openssh.authorizedKeysFiles</literal>!
265265+ </para>
266266+ </listitem>
267267+ <listitem>
268268+ <para>
269269+ The option <literal>fonts.enableFontDir</literal> has been
270270+ renamed to
271271+ <link xlink:href="options.html#opt-fonts.fontDir.enable">fonts.fontDir.enable</link>.
272272+ The path of font directory has also been changed to
273273+ <literal>/run/current-system/sw/share/X11/fonts</literal>, for
274274+ consistency with other X11 resources.
275275+ </para>
276276+ </listitem>
277277+ <listitem>
278278+ <para>
279279+ A number of options have been renamed in the kicad interface.
280280+ <literal>oceSupport</literal> has been renamed to
281281+ <literal>withOCE</literal>, <literal>withOCCT</literal> has
282282+ been renamed to <literal>withOCC</literal>,
283283+ <literal>ngspiceSupport</literal> has been renamed to
284284+ <literal>withNgspice</literal>, and
285285+ <literal>scriptingSupport</literal> has been renamed to
286286+ <literal>withScripting</literal>. Additionally,
287287+ <literal>kicad/base.nix</literal> no longer provides default
288288+ argument values since these are provided by
289289+ <literal>kicad/default.nix</literal>.
290290+ </para>
291291+ </listitem>
292292+ <listitem>
293293+ <para>
294294+ The socket for the <literal>pdns-recursor</literal> module was
295295+ moved from <literal>/var/lib/pdns-recursor</literal> to
296296+ <literal>/run/pdns-recursor</literal> to match upstream.
297297+ </para>
298298+ </listitem>
299299+ <listitem>
300300+ <para>
301301+ Paperwork was updated to version 2. The on-disk format
302302+ slightly changed, and it is not possible to downgrade from
303303+ Paperwork 2 back to Paperwork 1.3. Back your documents up
304304+ before upgrading. See
305305+ <link xlink:href="https://forum.openpaper.work/t/paperwork-2-0/112/5">this
306306+ thread</link> for more details.
307307+ </para>
308308+ </listitem>
309309+ <listitem>
310310+ <para>
311311+ PowerDNS has been updated from <literal>4.2.x</literal> to
312312+ <literal>4.3.x</literal>. Please be sure to review the
313313+ <link xlink:href="https://doc.powerdns.com/authoritative/upgrading.html#x-to-4-3-0">Upgrade
314314+ Notes</link> provided by upstream before upgrading. Worth
315315+ specifically noting is that the service now runs entirely as a
316316+ dedicated <literal>pdns</literal> user, instead of starting as
317317+ <literal>root</literal> and dropping privileges, as well as
318318+ the default <literal>socket-dir</literal> location changing
319319+ from <literal>/var/lib/powerdns</literal> to
320320+ <literal>/run/pdns</literal>.
321321+ </para>
322322+ </listitem>
323323+ <listitem>
324324+ <para>
325325+ The <literal>mediatomb</literal> service is now using by
326326+ default the new and maintained fork <literal>gerbera</literal>
327327+ package instead of the unmaintained
328328+ <literal>mediatomb</literal> package. If you want to keep the
329329+ old behavior, you must declare it with:
330330+ </para>
331331+ <programlisting language="bash">
332332+{
333333+ services.mediatomb.package = pkgs.mediatomb;
334334+}
335335+</programlisting>
336336+ <para>
337337+ One new option <literal>openFirewall</literal> has been
338338+ introduced which defaults to false. If you relied on the
339339+ service declaration to add the firewall rules itself before,
340340+ you should now declare it with:
341341+ </para>
342342+ <programlisting language="bash">
343343+{
344344+ services.mediatomb.openFirewall = true;
345345+}
346346+</programlisting>
347347+ </listitem>
348348+ <listitem>
349349+ <para>
350350+ xfsprogs was update from 4.19 to 5.11. It now enables reflink
351351+ support by default on filesystem creation. Support for
352352+ reflinks was added with an experimental status to kernel 4.9
353353+ and deemed stable in kernel 4.16. If you want to be able to
354354+ mount XFS filesystems created with this release of xfsprogs on
355355+ kernel releases older than those, you need to format them with
356356+ <literal>mkfs.xfs -m reflink=0</literal>.
357357+ </para>
358358+ </listitem>
359359+ <listitem>
360360+ <para>
361361+ The uWSGI server is now built with POSIX capabilities. As a
362362+ consequence, root is no longer required in emperor mode and
363363+ the service defaults to running as the unprivileged
364364+ <literal>uwsgi</literal> user. Any additional capability can
365365+ be added via the new option
366366+ <link xlink:href="options.html#opt-services.uwsgi.capabilities">services.uwsgi.capabilities</link>.
367367+ The previous behaviour can be restored by setting:
368368+ </para>
369369+ <programlisting language="bash">
370370+{
371371+ services.uwsgi.user = "root";
372372+ services.uwsgi.group = "root";
373373+ services.uwsgi.instance =
374374+ {
375375+ uid = "uwsgi";
376376+ gid = "uwsgi";
377377+ };
378378+}
379379+</programlisting>
380380+ <para>
381381+ Another incompatibility from the previous release is that
382382+ vassals running under a different user or group need to use
383383+ <literal>immediate-{uid,gid}</literal> instead of the usual
384384+ <literal>uid,gid</literal> options.
385385+ </para>
386386+ </listitem>
387387+ <listitem>
388388+ <para>
389389+ btc1 has been abandoned upstream, and removed.
390390+ </para>
391391+ </listitem>
392392+ <listitem>
393393+ <para>
394394+ cpp_ethereum (aleth) has been abandoned upstream, and removed.
395395+ </para>
396396+ </listitem>
397397+ <listitem>
398398+ <para>
399399+ riak-cs package removed along with
400400+ <literal>services.riak-cs</literal> module.
401401+ </para>
402402+ </listitem>
403403+ <listitem>
404404+ <para>
405405+ stanchion package removed along with
406406+ <literal>services.stanchion</literal> module.
407407+ </para>
408408+ </listitem>
409409+ <listitem>
410410+ <para>
411411+ mutt has been updated to a new major version (2.x), which
412412+ comes with some backward incompatible changes that are
413413+ described in the
414414+ <link xlink:href="http://www.mutt.org/relnotes/2.0/">release
415415+ notes for Mutt 2.0</link>.
416416+ </para>
417417+ </listitem>
418418+ <listitem>
419419+ <para>
420420+ <literal>vim</literal> and <literal>neovim</literal> switched
421421+ to Python 3, dropping all Python 2 support.
422422+ </para>
423423+ </listitem>
424424+ <listitem>
425425+ <para>
426426+ <link xlink:href="options.html#opt-networking.wireguard.interfaces">networking.wireguard.interfaces.<name>.generatePrivateKeyFile</link>,
427427+ which is off by default, had a <literal>chmod</literal> race
428428+ condition fixed. As an aside, the parent directory's
429429+ permissions were widened, and the key files were made
430430+ owner-writable. This only affects newly created keys. However,
431431+ if the exact permissions are important for your setup, read
432432+ <link xlink:href="https://github.com/NixOS/nixpkgs/pull/121294">#121294</link>.
433433+ </para>
434434+ </listitem>
435435+ <listitem>
436436+ <para>
437437+ <link xlink:href="options.html#opt-boot.zfs.forceImportAll">boot.zfs.forceImportAll</link>
438438+ previously did nothing, but has been fixed. However its
439439+ default has been changed to <literal>false</literal> to
440440+ preserve the existing default behaviour. If you have this
441441+ explicitly set to <literal>true</literal>, please note that
442442+ your non-root pools will now be forcibly imported.
443443+ </para>
444444+ </listitem>
445445+ <listitem>
446446+ <para>
447447+ openafs now points to openafs_1_8, which is the new stable
448448+ release. OpenAFS 1.6 was removed.
449449+ </para>
450450+ </listitem>
451451+ <listitem>
452452+ <para>
453453+ The WireGuard module gained a new option
454454+ <literal>networking.wireguard.interfaces.<name>.peers.*.dynamicEndpointRefreshSeconds</literal>
455455+ that implements refreshing the IP of DNS-based endpoints
456456+ periodically (which WireGuard itself
457457+ <link xlink:href="https://lists.zx2c4.com/pipermail/wireguard/2017-November/002028.html">cannot
458458+ do</link>).
459459+ </para>
460460+ </listitem>
461461+ <listitem>
462462+ <para>
463463+ MariaDB has been updated to 10.5. Before you upgrade, it would
464464+ be best to take a backup of your database and read
465465+ <link xlink:href="https://mariadb.com/kb/en/upgrading-from-mariadb-104-to-mariadb-105/#incompatible-changes-between-104-and-105">
466466+ Incompatible Changes Between 10.4 and 10.5</link>. After the
467467+ upgrade you will need to run <literal>mysql_upgrade</literal>.
468468+ </para>
469469+ </listitem>
470470+ <listitem>
471471+ <para>
472472+ The TokuDB storage engine dropped in mariadb 10.5 and removed
473473+ in mariadb 10.6. It is recommended to switch to RocksDB. See
474474+ also
475475+ <link xlink:href="https://mariadb.com/kb/en/tokudb/">TokuDB</link>
476476+ and
477477+ <link xlink:href="https://jira.mariadb.org/browse/MDEV-19780">MDEV-19780:
478478+ Remove the TokuDB storage engine</link>.
479479+ </para>
480480+ </listitem>
481481+ <listitem>
482482+ <para>
483483+ The <literal>openldap</literal> module now has support for
484484+ OLC-style configuration, users of the
485485+ <literal>configDir</literal> option may wish to migrate. If
486486+ you continue to use <literal>configDir</literal>, ensure that
487487+ <literal>olcPidFile</literal> is set to
488488+ <literal>/run/slapd/slapd.pid</literal>.
489489+ </para>
490490+ <para>
491491+ As a result, <literal>extraConfig</literal> and
492492+ <literal>extraDatabaseConfig</literal> are removed. To help
493493+ with migration, you can convert your
494494+ <literal>slapd.conf</literal> file to OLC configuration with
495495+ the following script (find the location of this configuration
496496+ file by running <literal>systemctl status openldap</literal>,
497497+ it is the <literal>-f</literal> option.
498498+ </para>
499499+ <programlisting>
500500+$ TMPDIR=$(mktemp -d)
501501+$ slaptest -f /path/to/slapd.conf -F $TMPDIR
502502+$ slapcat -F $TMPDIR -n0 -H 'ldap:///???(!(objectClass=olcSchemaConfig))'
503503+</programlisting>
504504+ <para>
505505+ This will dump your current configuration in LDIF format,
506506+ which should be straightforward to convert into Nix settings.
507507+ This does not show your schema configuration, as this is
508508+ unnecessarily verbose for users of the default schemas and
509509+ <literal>slaptest</literal> is buggy with schemas directly in
510510+ the config file.
511511+ </para>
512512+ </listitem>
513513+ <listitem>
514514+ <para>
515515+ Amazon EC2 and OpenStack Compute (nova) images now re-fetch
516516+ instance meta data and user data from the instance metadata
517517+ service (IMDS) on each boot. For example: stopping an EC2
518518+ instance, changing its user data, and restarting the instance
519519+ will now cause it to fetch and apply the new user data.
520520+ </para>
521521+ <warning>
522522+ <para>
523523+ Specifically, <literal>/etc/ec2-metadata</literal> is
524524+ re-populated on each boot. Some NixOS scripts that read from
525525+ this directory are guarded to only run if the files they
526526+ want to manipulate do not already exist, and so will not
527527+ re-apply their changes if the IMDS response changes.
528528+ Examples: <literal>root</literal>'s SSH key is only added if
529529+ <literal>/root/.ssh/authorized_keys</literal> does not
530530+ exist, and SSH host keys are only set from user data if they
531531+ do not exist in <literal>/etc/ssh</literal>.
532532+ </para>
533533+ </warning>
534534+ </listitem>
535535+ <listitem>
536536+ <para>
537537+ The <literal>rspamd</literal> services is now sandboxed. It is
538538+ run as a dynamic user instead of root, so secrets and other
539539+ files may have to be moved or their permissions may have to be
540540+ fixed. The sockets are now located in
541541+ <literal>/run/rspamd</literal> instead of
542542+ <literal>/run</literal>.
543543+ </para>
544544+ </listitem>
545545+ <listitem>
546546+ <para>
547547+ Enabling the Tor client no longer silently also enables and
548548+ configures Privoxy, and the
549549+ <literal>services.tor.client.privoxy.enable</literal> option
550550+ has been removed. To enable Privoxy, and to configure it to
551551+ use Tor's faster port, use the following configuration:
552552+ </para>
553553+ <programlisting language="bash">
554554+{
555555+ opt-services.privoxy.enable = true;
556556+ opt-services.privoxy.enableTor = true;
557557+}
558558+</programlisting>
559559+ </listitem>
560560+ <listitem>
561561+ <para>
562562+ The <literal>services.tor</literal> module has a new
563563+ exhaustively typed
564564+ <link xlink:href="options.html#opt-services.tor.settings">services.tor.settings</link>
565565+ option following RFC 0042; backward compatibility with old
566566+ options has been preserved when aliasing was possible. The
567567+ corresponding systemd service has been hardened, but there is
568568+ a chance that the service still requires more permissions, so
569569+ please report any related trouble on the bugtracker. Onion
570570+ services v3 are now supported in
571571+ <link xlink:href="options.html#opt-services.tor.relay.onionServices">services.tor.relay.onionServices</link>.
572572+ A new
573573+ <link xlink:href="options.html#opt-services.tor.openFirewall">services.tor.openFirewall</link>
574574+ option as been introduced for allowing connections on all the
575575+ TCP ports configured.
576576+ </para>
577577+ </listitem>
578578+ <listitem>
579579+ <para>
580580+ The options
581581+ <literal>services.slurm.dbdserver.storagePass</literal> and
582582+ <literal>services.slurm.dbdserver.configFile</literal> have
583583+ been removed. Use
584584+ <literal>services.slurm.dbdserver.storagePassFile</literal>
585585+ instead to provide the database password. Extra config options
586586+ can be given via the option
587587+ <literal>services.slurm.dbdserver.extraConfig</literal>. The
588588+ actual configuration file is created on the fly on startup of
589589+ the service. This avoids that the password gets exposed in the
590590+ nix store.
591591+ </para>
592592+ </listitem>
593593+ <listitem>
594594+ <para>
595595+ The <literal>wafHook</literal> hook does not wrap Python
596596+ anymore. Packages depending on <literal>wafHook</literal> need
597597+ to include any Python into their
598598+ <literal>nativeBuildInputs</literal>.
599599+ </para>
600600+ </listitem>
601601+ <listitem>
602602+ <para>
603603+ Starting with version 1.7.0, the project formerly named
604604+ <literal>CodiMD</literal> is now named
605605+ <literal>HedgeDoc</literal>. New installations will no longer
606606+ use the old name for users, state directories and such, this
607607+ needs to be considered when moving state to a more recent
608608+ NixOS installation. Based on
609609+ <link xlink:href="options.html#opt-system.stateVersion">system.stateVersion</link>,
610610+ existing installations will continue to work.
611611+ </para>
612612+ </listitem>
613613+ <listitem>
614614+ <para>
615615+ The fish-foreign-env package has been replaced with
616616+ fishPlugins.foreign-env, in which the fish functions have been
617617+ relocated to the <literal>vendor_functions.d</literal>
618618+ directory to be loaded automatically.
619619+ </para>
620620+ </listitem>
621621+ <listitem>
622622+ <para>
623623+ The prometheus json exporter is now managed by the prometheus
624624+ community. Together with additional features some backwards
625625+ incompatibilities were introduced. Most importantly the
626626+ exporter no longer accepts a fixed command-line parameter to
627627+ specify the URL of the endpoint serving JSON. It now expects
628628+ this URL to be passed as an URL parameter, when scraping the
629629+ exporter's <literal>/probe</literal> endpoint. In the
630630+ prometheus scrape configuration the scrape target might look
631631+ like this:
632632+ </para>
633633+ <programlisting>
634634+http://some.json-exporter.host:7979/probe?target=https://example.com/some/json/endpoint
635635+</programlisting>
636636+ <para>
637637+ Existing configuration for the exporter needs to be updated,
638638+ but can partially be re-used. Documentation is available in
639639+ the upstream repository and a small example for NixOS is
640640+ available in the corresponding NixOS test.
641641+ </para>
642642+ <para>
643643+ These changes also affect
644644+ <link xlink:href="options.html#opt-services.prometheus.exporters.rspamd.enable">services.prometheus.exporters.rspamd.enable</link>,
645645+ which is just a preconfigured instance of the json exporter.
646646+ </para>
647647+ <para>
648648+ For more information, take a look at the
649649+ <link xlink:href="https://github.com/prometheus-community/json_exporter">
650650+ official documentation</link> of the json_exporter.
651651+ </para>
652652+ </listitem>
653653+ <listitem>
654654+ <para>
655655+ Androidenv was updated, removing the
656656+ <literal>includeDocs</literal> and
657657+ <literal>lldbVersions</literal> arguments. Docs only covered a
658658+ single version of the Android SDK, LLDB is now bundled with
659659+ the NDK, and both are no longer available to download from the
660660+ Android package repositories. Additionally, since the package
661661+ lists have been updated, some older versions of Android
662662+ packages may not be bundled. If you depend on older versions
663663+ of Android packages, we recommend overriding the repo.
664664+ </para>
665665+ <para>
666666+ Android packages are now loaded from a repo.json file created
667667+ by parsing Android repo XML files. The arguments
668668+ <literal>repoJson</literal> and <literal>repoXmls</literal>
669669+ have been added to allow overriding the built-in androidenv
670670+ repo.json with your own. Additionally, license files are now
671671+ written to allow compatibility with Gradle-based tools, and
672672+ the <literal>extraLicenses</literal> argument has been added
673673+ to accept more SDK licenses if your project requires it. See
674674+ the androidenv documentation for more details.
675675+ </para>
676676+ </listitem>
677677+ <listitem>
678678+ <para>
679679+ The attribute <literal>mpi</literal> is now consistently used
680680+ to provide a default, system-wide MPI implementation. The
681681+ default implementation is openmpi, which has been used before
682682+ by all derivations affects by this change. Note that all
683683+ packages that have used <literal>mpi ? null</literal> in the
684684+ input for optional MPI builds, have been changed to the
685685+ boolean input paramater <literal>useMpi</literal> to enable
686686+ building with MPI. Building all packages with
687687+ <literal>mpich</literal> instead of the default
688688+ <literal>openmpi</literal> can now be achived like this:
689689+ </para>
690690+ <programlisting language="bash">
691691+self: super:
692692+{
693693+ mpi = super.mpich;
694694+}
695695+</programlisting>
696696+ </listitem>
697697+ <listitem>
698698+ <para>
699699+ The Searx module has been updated with the ability to
700700+ configure the service declaratively and uWSGI integration. The
701701+ option <literal>services.searx.configFile</literal> has been
702702+ renamed to
703703+ <link xlink:href="options.html#opt-services.searx.settingsFile">services.searx.settingsFile</link>
704704+ for consistency with the new
705705+ <link xlink:href="options.html#opt-services.searx.settings">services.searx.settings</link>.
706706+ In addition, the <literal>searx</literal> uid and gid
707707+ reservations have been removed since they were not necessary:
708708+ the service is now running with a dynamically allocated uid.
709709+ </para>
710710+ </listitem>
711711+ <listitem>
712712+ <para>
713713+ The libinput module has been updated with the ability to
714714+ configure mouse and touchpad settings separately. The options
715715+ in <literal>services.xserver.libinput</literal> have been
716716+ renamed to
717717+ <literal>services.xserver.libinput.touchpad</literal>, while
718718+ there is a new
719719+ <literal>services.xserver.libinput.mouse</literal> for mouse
720720+ related configuration.
721721+ </para>
722722+ <para>
723723+ Since touchpad options no longer apply to all devices, you may
724724+ want to replicate your touchpad configuration in mouse
725725+ section.
726726+ </para>
727727+ </listitem>
728728+ <listitem>
729729+ <para>
730730+ ALSA OSS emulation
731731+ (<literal>sound.enableOSSEmulation</literal>) is now disabled
732732+ by default.
733733+ </para>
734734+ </listitem>
735735+ <listitem>
736736+ <para>
737737+ Thinkfan as been updated to <literal>1.2.x</literal>, which
738738+ comes with a new YAML based configuration format. For this
739739+ reason, several NixOS options of the thinkfan module have been
740740+ changed to non-backward compatible types. In addition, a new
741741+ <link xlink:href="options.html#opt-services.thinkfan.settings">services.thinkfan.settings</link>
742742+ option has been added.
743743+ </para>
744744+ <para>
745745+ Please read the
746746+ <link xlink:href="https://github.com/vmatare/thinkfan#readme">
747747+ thinkfan documentation</link> before updating.
748748+ </para>
749749+ </listitem>
750750+ <listitem>
751751+ <para>
752752+ Adobe Flash Player support has been dropped from the tree. In
753753+ particular, the following packages no longer support it:
754754+ </para>
755755+ <itemizedlist>
756756+ <listitem>
757757+ <para>
758758+ chromium
759759+ </para>
760760+ </listitem>
761761+ <listitem>
762762+ <para>
763763+ firefox
764764+ </para>
765765+ </listitem>
766766+ <listitem>
767767+ <para>
768768+ qt48
769769+ </para>
770770+ </listitem>
771771+ <listitem>
772772+ <para>
773773+ qt5.qtwebkit
774774+ </para>
775775+ </listitem>
776776+ </itemizedlist>
777777+ <para>
778778+ Additionally, packages flashplayer and hal-flash were removed
779779+ along with the <literal>services.flashpolicyd</literal>
780780+ module.
781781+ </para>
782782+ </listitem>
783783+ <listitem>
784784+ <para>
785785+ The <literal>security.rngd</literal> module has been removed.
786786+ It was disabled by default in 20.09 as it was functionally
787787+ redundant with krngd in the linux kernel. It is not necessary
788788+ for any device that the kernel recognises as an hardware RNG,
789789+ as it will automatically run the krngd task to periodically
790790+ collect random data from the device and mix it into the
791791+ kernel's RNG.
792792+ </para>
793793+ <para>
794794+ The default SMTP port for GitLab has been changed to
795795+ <literal>25</literal> from its previous default of
796796+ <literal>465</literal>. If you depended on this default, you
797797+ should now set the
798798+ <link xlink:href="options.html#opt-services.gitlab.smtp.port">services.gitlab.smtp.port</link>
799799+ option.
800800+ </para>
801801+ </listitem>
802802+ <listitem>
803803+ <para>
804804+ The default version of ImageMagick has been updated from 6 to
805805+ 7. You can use imagemagick6, imagemagick6_light, and
806806+ imagemagick6Big if you need the older version.
807807+ </para>
808808+ </listitem>
809809+ <listitem>
810810+ <para>
811811+ <link xlink:href="options.html#opt-services.xserver.videoDrivers">services.xserver.videoDrivers</link>
812812+ no longer uses the deprecated <literal>cirrus</literal> and
813813+ <literal>vesa</literal> device dependent X drivers by default.
814814+ It also enables both <literal>amdgpu</literal> and
815815+ <literal>nouveau</literal> drivers by default now.
816816+ </para>
817817+ </listitem>
818818+ <listitem>
819819+ <para>
820820+ The <literal>kindlegen</literal> package is gone, because it
821821+ is no longer supported or hosted by Amazon. Sadly, its
822822+ replacement, Kindle Previewer, has no Linux support. However,
823823+ there are other ways to generate MOBI files. See
824824+ <link xlink:href="https://github.com/NixOS/nixpkgs/issues/96439">the
825825+ discussion</link> for more info.
826826+ </para>
827827+ </listitem>
828828+ <listitem>
829829+ <para>
830830+ The apacheKafka packages are now built with version-matched
831831+ JREs. Versions 2.6 and above, the ones that recommend it, use
832832+ jdk11, while versions below remain on jdk8. The NixOS service
833833+ has been adjusted to start the service using the same version
834834+ as the package, adjustable with the new
835835+ <link xlink:href="options.html#opt-services.apache-kafka.jre">services.apache-kafka.jre</link>
836836+ option. Furthermore, the default list of
837837+ <link xlink:href="options.html#opt-services.apache-kafka.jvmOptions">services.apache-kafka.jvmOptions</link>
838838+ have been removed. You should set your own according to the
839839+ <link xlink:href="https://kafka.apache.org/documentation/#java">upstream
840840+ documentation</link> for your Kafka version.
841841+ </para>
842842+ </listitem>
843843+ <listitem>
844844+ <para>
845845+ The kodi package has been modified to allow concise addon
846846+ management. Consider the following configuration from previous
847847+ releases of NixOS to install kodi, including the
848848+ kodiPackages.inputstream-adaptive and kodiPackages.vfs-sftp
849849+ addons:
850850+ </para>
851851+ <programlisting language="bash">
852852+{
853853+ environment.systemPackages = [
854854+ pkgs.kodi
855855+ ];
856856+857857+ nixpkgs.config.kodi = {
858858+ enableInputStreamAdaptive = true;
859859+ enableVFSSFTP = true;
860860+ };
861861+}
862862+</programlisting>
863863+ <para>
864864+ All Kodi <literal>config</literal> flags have been removed,
865865+ and as a result the above configuration should now be written
866866+ as:
867867+ </para>
868868+ <programlisting language="bash">
869869+{
870870+ environment.systemPackages = [
871871+ (pkgs.kodi.withPackages (p: with p; [
872872+ inputstream-adaptive
873873+ vfs-sftp
874874+ ]))
875875+ ];
876876+}
877877+</programlisting>
878878+ </listitem>
879879+ <listitem>
880880+ <para>
881881+ <literal>environment.defaultPackages</literal> now includes
882882+ the nano package. If pkgs.nano is not added to the list, make
883883+ sure another editor is installed and the
884884+ <literal>EDITOR</literal> environment variable is set to it.
885885+ Environment variables can be set using
886886+ <literal>environment.variables</literal>.
887887+ </para>
888888+ </listitem>
889889+ <listitem>
890890+ <para>
891891+ <literal>services.minio.dataDir</literal> changed type to a
892892+ list of paths, required for specifiyng multiple data
893893+ directories for using with erasure coding. Currently, the
894894+ service doesn't enforce nor checks the correct number of paths
895895+ to correspond to minio requirements.
896896+ </para>
897897+ </listitem>
898898+ <listitem>
899899+ <para>
900900+ All CUDA toolkit versions prior to CUDA 10 have been removed.
901901+ </para>
902902+ </listitem>
903903+ <listitem>
904904+ <para>
905905+ The kbdKeymaps package was removed since dvp and neo are now
906906+ included in kbd. If you want to use the Programmer Dvorak
907907+ Keyboard Layout, you have to use
908908+ <literal>dvorak-programmer</literal> in
909909+ <literal>console.keyMap</literal> now instead of
910910+ <literal>dvp</literal>. In
911911+ <literal>services.xserver.xkbVariant</literal> it's still
912912+ <literal>dvp</literal>.
913913+ </para>
914914+ </listitem>
915915+ <listitem>
916916+ <para>
917917+ The babeld service is now being run as an unprivileged user.
918918+ To achieve that the module configures
919919+ <literal>skip-kernel-setup true</literal> and takes care of
920920+ setting forwarding and rp_filter sysctls by itself as well as
921921+ for each interface in
922922+ <literal>services.babeld.interfaces</literal>.
923923+ </para>
924924+ </listitem>
925925+ <listitem>
926926+ <para>
927927+ The <literal>services.zigbee2mqtt.config</literal> option has
928928+ been renamed to
929929+ <literal>services.zigbee2mqtt.settings</literal> and now
930930+ follows
931931+ <link xlink:href="https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md">RFC
932932+ 0042</link>.
933933+ </para>
934934+ </listitem>
935935+ </itemizedlist>
936936+ <para>
937937+ The yadm dotfile manager has been updated from 2.x to 3.x, which
938938+ has new (XDG) default locations for some data/state files. Most
939939+ yadm commands will fail and print a legacy path warning (which
940940+ describes how to upgrade/migrate your repository). If you have
941941+ scripts, daemons, scheduled jobs, shell profiles, etc. that invoke
942942+ yadm, expect them to fail or misbehave until you perform this
943943+ migration and prepare accordingly.
944944+ </para>
945945+ <itemizedlist>
946946+ <listitem>
947947+ <para>
948948+ Instead of determining
949949+ <literal>services.radicale.package</literal> automatically
950950+ based on <literal>system.stateVersion</literal>, the latest
951951+ version is always used because old versions are not officially
952952+ supported.
953953+ </para>
954954+ <para>
955955+ Furthermore, Radicale's systemd unit was hardened which might
956956+ break some deployments. In particular, a non-default
957957+ <literal>filesystem_folder</literal> has to be added to
958958+ <literal>systemd.services.radicale.serviceConfig.ReadWritePaths</literal>
959959+ if the deprecated <literal>services.radicale.config</literal>
960960+ is used.
961961+ </para>
962962+ </listitem>
963963+ <listitem>
964964+ <para>
965965+ In the <literal>security.acme</literal> module, use of
966966+ <literal>--reuse-key</literal> parameter for Lego has been
967967+ removed. It was introduced for HKPK, but this security feature
968968+ is now deprecated. It is a better security practice to rotate
969969+ key pairs instead of always keeping the same. If you need to
970970+ keep this parameter, you can add it back using
971971+ <literal>extraLegoRenewFlags</literal> as an option for the
972972+ appropriate certificate.
973973+ </para>
974974+ </listitem>
975975+ </itemizedlist>
976976+ </section>
977977+ <section xml:id="sec-release-21.05-notable-changes">
978978+ <title>Other Notable Changes</title>
979979+ <itemizedlist>
980980+ <listitem>
981981+ <para>
982982+ <literal>stdenv.lib</literal> has been deprecated and will
983983+ break eval in 21.11. Please use <literal>pkgs.lib</literal>
984984+ instead. See
985985+ <link xlink:href="https://github.com/NixOS/nixpkgs/issues/108938">#108938</link>
986986+ for details.
987987+ </para>
988988+ </listitem>
989989+ <listitem>
990990+ <para>
991991+ <link xlink:href="https://www.gnuradio.org/">GNURadio</link>
992992+ has a <literal>pkgs</literal> attribute set, and there's a
993993+ <literal>gnuradio.callPackage</literal> function that extends
994994+ <literal>pkgs</literal> with a
995995+ <literal>mkDerivation</literal>, and a
996996+ <literal>mkDerivationWith</literal>, like Qt5. Now all
997997+ <literal>gnuradio.pkgs</literal> are defined with
998998+ <literal>gnuradio.callPackage</literal> and some packages that
999999+ depend on gnuradio are defined with this as well.
10001000+ </para>
10011001+ </listitem>
10021002+ <listitem>
10031003+ <para>
10041004+ <link xlink:href="https://www.privoxy.org/">Privoxy</link> has
10051005+ been updated to version 3.0.32 (See
10061006+ <link xlink:href="https://lists.privoxy.org/pipermail/privoxy-announce/2021-February/000007.html">announcement</link>).
10071007+ Compared to the previous release, Privoxy has gained support
10081008+ for HTTPS inspection (still experimental), Brotli
10091009+ decompression, several new filters and lots of bug fixes,
10101010+ including security ones. In addition, the package is now built
10111011+ with compression and external filters support, which were
10121012+ previously disabled.
10131013+ </para>
10141014+ <para>
10151015+ Regarding the NixOS module, new options for HTTPS inspection
10161016+ have been added and
10171017+ <literal>services.privoxy.extraConfig</literal> has been
10181018+ replaced by the new
10191019+ <link xlink:href="options.html#opt-services.privoxy.settings">services.privoxy.settings</link>
10201020+ (See
10211021+ <link xlink:href="https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md">RFC
10221022+ 0042</link> for the motivation).
10231023+ </para>
10241024+ </listitem>
10251025+ <listitem>
10261026+ <para>
10271027+ <link xlink:href="https://kodi.tv/">Kodi</link> has been
10281028+ updated to version 19.1 "Matrix". See the
10291029+ <link xlink:href="https://kodi.tv/article/kodi-190-matrix-release">announcement</link>
10301030+ for further details.
10311031+ </para>
10321032+ </listitem>
10331033+ <listitem>
10341034+ <para>
10351035+ The <literal>services.packagekit.backend</literal> option has
10361036+ been removed as it only supported a single setting which would
10371037+ always be the default. Instead new
10381038+ <link xlink:href="https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md">RFC
10391039+ 0042</link> compliant
10401040+ <link xlink:href="options.html#opt-services.packagekit.settings">services.packagekit.settings</link>
10411041+ and
10421042+ <link xlink:href="options.html#opt-services.packagekit.vendorSettings">services.packagekit.vendorSettings</link>
10431043+ options have been introduced.
10441044+ </para>
10451045+ </listitem>
10461046+ <listitem>
10471047+ <para>
10481048+ <link xlink:href="https://nginx.org">Nginx</link> has been
10491049+ updated to stable version 1.20.0. Now nginx uses the zlib-ng
10501050+ library by default.
10511051+ </para>
10521052+ </listitem>
10531053+ <listitem>
10541054+ <para>
10551055+ KDE Gear (formerly KDE Applications) is upgraded to 21.04, see
10561056+ its
10571057+ <link xlink:href="https://kde.org/announcements/gear/21.04/">release
10581058+ notes</link> for details.
10591059+ </para>
10601060+ <para>
10611061+ The <literal>kdeApplications</literal> package set is now
10621062+ <literal>kdeGear</literal>, in keeping with the new name. The
10631063+ old name remains for compatibility, but it is deprecated.
10641064+ </para>
10651065+ </listitem>
10661066+ <listitem>
10671067+ <para>
10681068+ <link xlink:href="https://libreswan.org/">Libreswan</link> has
10691069+ been updated to version 4.4. The package now includes example
10701070+ configurations and manual pages by default. The NixOS module
10711071+ has been changed to use the upstream systemd units and write
10721072+ the configuration in the <literal>/etc/ipsec.d/ </literal>
10731073+ directory. In addition, two new options have been added to
10741074+ specify connection policies
10751075+ (<link xlink:href="options.html#opt-services.libreswan.policies">services.libreswan.policies</link>)
10761076+ and disable send/receive redirects
10771077+ (<link xlink:href="options.html#opt-services.libreswan.disableRedirects">services.libreswan.disableRedirects</link>).
10781078+ </para>
10791079+ </listitem>
10801080+ <listitem>
10811081+ <para>
10821082+ The Mailman NixOS module (<literal>services.mailman</literal>)
10831083+ has a new option
10841084+ <link xlink:href="options.html#opt-services.mailman.enablePostfix">services.mailman.enablePostfix</link>,
10851085+ defaulting to true, that controls integration with Postfix.
10861086+ </para>
10871087+ <para>
10881088+ If this option is disabled, default MTA config becomes not set
10891089+ and you should set the options in
10901090+ <literal>services.mailman.settings.mta</literal> according to
10911091+ the desired configuration as described in
10921092+ <link xlink:href="https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html">Mailman
10931093+ documentation</link>.
10941094+ </para>
10951095+ </listitem>
10961096+ <listitem>
10971097+ <para>
10981098+ The default-version of <literal>nextcloud</literal> is
10991099+ nextcloud21. Please note that it's <emphasis>not</emphasis>
11001100+ possible to upgrade <literal>nextcloud</literal> across
11011101+ multiple major versions! This means that it's e.g. not
11021102+ possible to upgrade from nextcloud18 to nextcloud20 in a
11031103+ single deploy and most <literal>20.09</literal> users will
11041104+ have to upgrade to nextcloud20 first.
11051105+ </para>
11061106+ <para>
11071107+ The package can be manually upgraded by setting
11081108+ <link xlink:href="options.html#opt-services.nextcloud.package">services.nextcloud.package</link>
11091109+ to nextcloud21.
11101110+ </para>
11111111+ </listitem>
11121112+ <listitem>
11131113+ <para>
11141114+ The setting
11151115+ <link xlink:href="options.html#opt-services.redis.bind">services.redis.bind</link>
11161116+ defaults to <literal>127.0.0.1</literal> now, making Redis
11171117+ listen on the loopback interface only, and not all public
11181118+ network interfaces.
11191119+ </para>
11201120+ </listitem>
11211121+ <listitem>
11221122+ <para>
11231123+ NixOS now emits a deprecation warning if systemd's
11241124+ <literal>StartLimitInterval</literal> setting is used in a
11251125+ <literal>serviceConfig</literal> section instead of in a
11261126+ <literal>unitConfig</literal>; that setting is deprecated and
11271127+ now undocumented for the service section by systemd upstream,
11281128+ but still effective and somewhat buggy there, which can be
11291129+ confusing. See
11301130+ <link xlink:href="https://github.com/NixOS/nixpkgs/issues/45785">#45785</link>
11311131+ for details.
11321132+ </para>
11331133+ <para>
11341134+ All services should use
11351135+ <link xlink:href="options.html#opt-systemd.services._name_.startLimitIntervalSec">systemd.services.<emphasis>name</emphasis>.startLimitIntervalSec</link>
11361136+ or <literal>StartLimitIntervalSec</literal> in
11371137+ <link xlink:href="options.html#opt-systemd.services._name_.unitConfig">systemd.services.<emphasis>name</emphasis>.unitConfig</link>
11381138+ instead.
11391139+ </para>
11401140+ </listitem>
11411141+ <listitem>
11421142+ <para>
11431143+ The <literal>mediatomb</literal> service declares new options.
11441144+ It also adapts existing options so the configuration
11451145+ generation is now lazy. The existing option
11461146+ <literal>customCfg</literal> (defaults to false), when
11471147+ enabled, stops the service configuration generation
11481148+ completely. It then expects the users to provide their own
11491149+ correct configuration at the right location (whereas the
11501150+ configuration was generated and not used at all before). The
11511151+ new option <literal>transcodingOption</literal> (defaults to
11521152+ no) allows a generated configuration. It makes the mediatomb
11531153+ service pulls the necessary runtime dependencies in the nix
11541154+ store (whereas it was generated with hardcoded values before).
11551155+ The new option <literal>mediaDirectories</literal> allows the
11561156+ users to declare autoscan media directories from their nixos
11571157+ configuration:
11581158+ </para>
11591159+ <programlisting language="bash">
11601160+{
11611161+ services.mediatomb.mediaDirectories = [
11621162+ { path = "/var/lib/mediatomb/pictures"; recursive = false; hidden-files = false; }
11631163+ { path = "/var/lib/mediatomb/audio"; recursive = true; hidden-files = false; }
11641164+ ];
11651165+}
11661166+</programlisting>
11671167+ </listitem>
11681168+ <listitem>
11691169+ <para>
11701170+ The Unbound DNS resolver service
11711171+ (<literal>services.unbound</literal>) has been refactored to
11721172+ allow reloading, control sockets and to fix startup ordering
11731173+ issues.
11741174+ </para>
11751175+ <para>
11761176+ It is now possible to enable a local UNIX control socket for
11771177+ unbound by setting the
11781178+ <link xlink:href="options.html#opt-services.unbound.localControlSocketPath">services.unbound.localControlSocketPath</link>
11791179+ option.
11801180+ </para>
11811181+ <para>
11821182+ Previously we just applied a very minimal set of restrictions
11831183+ and trusted unbound to properly drop root privs and
11841184+ capabilities.
11851185+ </para>
11861186+ <para>
11871187+ As of this we are (for the most part) just using the upstream
11881188+ example unit file for unbound. The main difference is that we
11891189+ start unbound as <literal>unbound</literal> user with the
11901190+ required capabilities instead of letting unbound do the chroot
11911191+ & uid/gid changes.
11921192+ </para>
11931193+ <para>
11941194+ The upstream unit configuration this is based on is a lot
11951195+ stricter with all kinds of permissions then our previous
11961196+ variant. It also came with the default of having the
11971197+ <literal>Type</literal> set to <literal>notify</literal>,
11981198+ therefore we are now also using the
11991199+ <literal>unbound-with-systemd</literal> package here. Unbound
12001200+ will start up, read the configuration files and start
12011201+ listening on the configured ports before systemd will declare
12021202+ the unit <literal>active (running)</literal>. This will likely
12031203+ help with startup order and the occasional race condition
12041204+ during system activation where the DNS service is started but
12051205+ not yet ready to answer queries. Services depending on
12061206+ <literal>nss-lookup.target</literal> or
12071207+ <literal>unbound.service</literal> are now be able to use
12081208+ unbound when those targets have been reached.
12091209+ </para>
12101210+ <para>
12111211+ Additionally to the much stricter runtime environment the
12121212+ <literal>/dev/urandom</literal> mount lines we previously had
12131213+ in the code (that randomly failed during the stop-phase) have
12141214+ been removed as systemd will take care of those for us.
12151215+ </para>
12161216+ <para>
12171217+ The <literal>preStart</literal> script is now only required if
12181218+ we enabled the trust anchor updates (which are still enabled
12191219+ by default).
12201220+ </para>
12211221+ <para>
12221222+ Another benefit of the refactoring is that we can now issue
12231223+ reloads via either <literal>pkill -HUP unbound</literal> and
12241224+ <literal>systemctl reload unbound</literal> to reload the
12251225+ running configuration without taking the daemon offline. A
12261226+ prerequisite of this was that unbound configuration is
12271227+ available on a well known path on the file system. We are
12281228+ using the path <literal>/etc/unbound/unbound.conf</literal> as
12291229+ that is the default in the CLI tooling which in turn enables
12301230+ us to use <literal>unbound-control</literal> without passing a
12311231+ custom configuration location.
12321232+ </para>
12331233+ <para>
12341234+ The module has also been reworked to be
12351235+ <link xlink:href="https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md">RFC
12361236+ 0042</link> compliant. As such,
12371237+ <literal>sevices.unbound.extraConfig</literal> has been
12381238+ removed and replaced by
12391239+ <link xlink:href="options.html#opt-services.unbound.settings">services.unbound.settings</link>.
12401240+ <literal>services.unbound.interfaces</literal> has been
12411241+ renamed to
12421242+ <literal>services.unbound.settings.server.interface</literal>.
12431243+ </para>
12441244+ <para>
12451245+ <literal>services.unbound.forwardAddresses</literal> and
12461246+ <literal>services.unbound.allowedAccess</literal> have also
12471247+ been changed to use the new settings interface. You can follow
12481248+ the instructions when executing
12491249+ <literal>nixos-rebuild</literal> to upgrade your configuration
12501250+ to use the new interface.
12511251+ </para>
12521252+ </listitem>
12531253+ <listitem>
12541254+ <para>
12551255+ The <literal>services.dnscrypt-proxy2</literal> module now
12561256+ takes the upstream's example configuration and updates it with
12571257+ the user's settings. An option has been added to restore the
12581258+ old behaviour if you prefer to declare the configuration from
12591259+ scratch.
12601260+ </para>
12611261+ </listitem>
12621262+ <listitem>
12631263+ <para>
12641264+ NixOS now defaults to the unified cgroup hierarchy
12651265+ (cgroupsv2). See the
12661266+ <link xlink:href="https://www.redhat.com/sysadmin/fedora-31-control-group-v2">Fedora
12671267+ Article for 31</link> for details on why this is desirable,
12681268+ and how it impacts containers.
12691269+ </para>
12701270+ <para>
12711271+ If you want to run containers with a runtime that does not yet
12721272+ support cgroupsv2, you can switch back to the old behaviour by
12731273+ setting
12741274+ <link xlink:href="options.html#opt-systemd.enableUnifiedCgroupHierarchy">systemd.enableUnifiedCgroupHierarchy</link>
12751275+ = <literal>false</literal>; and rebooting.
12761276+ </para>
12771277+ </listitem>
12781278+ <listitem>
12791279+ <para>
12801280+ PulseAudio was upgraded to 14.0, with changes to the handling
12811281+ of default sinks. See its
12821282+ <link xlink:href="https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/14.0/">release
12831283+ notes</link>.
12841284+ </para>
12851285+ </listitem>
12861286+ <listitem>
12871287+ <para>
12881288+ GNOME users may wish to delete their
12891289+ <literal>~/.config/pulse</literal> due to the changes to
12901290+ stream routing logic. See
12911291+ <link xlink:href="https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/832">PulseAudio
12921292+ bug 832</link> for more information.
12931293+ </para>
12941294+ </listitem>
12951295+ <listitem>
12961296+ <para>
12971297+ The zookeeper package does not provide
12981298+ <literal>zooInspector.sh</literal> anymore, as that
12991299+ "contrib" has been dropped from upstream releases.
13001300+ </para>
13011301+ </listitem>
13021302+ <listitem>
13031303+ <para>
13041304+ In the ACME module, the data used to build the hash for the
13051305+ account directory has changed to accomodate new features to
13061306+ reduce account rate limit issues. This will trigger new
13071307+ account creation on the first rebuild following this update.
13081308+ No issues are expected to arise from this, thanks to the new
13091309+ account creation handling.
13101310+ </para>
13111311+ </listitem>
13121312+ <listitem>
13131313+ <para>
13141314+ <link xlink:href="options.html#opt-users.users._name_.createHome">users.users.<emphasis>name</emphasis>.createHome</link>
13151315+ now always ensures home directory permissions to be
13161316+ <literal>0700</literal>. Permissions had previously been
13171317+ ignored for already existing home directories, possibly
13181318+ leaving them readable by others. The option's description was
13191319+ incorrect regarding ownership management and has been
13201320+ simplified greatly.
13211321+ </para>
13221322+ </listitem>
13231323+ <listitem>
13241324+ <para>
13251325+ When defining a new user, one of
13261326+ <link xlink:href="options.html#opt-users.users._name_.isNormalUser">users.users.<emphasis>name</emphasis>.isNormalUser</link>
13271327+ and
13281328+ <link xlink:href="options.html#opt-users.users._name_.isSystemUser">users.users.<emphasis>name</emphasis>.isSystemUser</link>
13291329+ is now required. This is to prevent accidentally giving a UID
13301330+ above 1000 to system users, which could have unexpected
13311331+ consequences, like running user activation scripts for system
13321332+ users. Note that users defined with an explicit UID below 500
13331333+ are exempted from this check, as
13341334+ <link xlink:href="options.html#opt-users.users._name_.isSystemUser">users.users.<emphasis>name</emphasis>.isSystemUser</link>
13351335+ has no effect for those.
13361336+ </para>
13371337+ </listitem>
13381338+ <listitem>
13391339+ <para>
13401340+ The <literal>security.apparmor</literal> module, for the
13411341+ <link xlink:href="https://gitlab.com/apparmor/apparmor/-/wikis/Documentation">AppArmor</link>
13421342+ Mandatory Access Control system, has been substantialy
13431343+ improved along with related tools, so that module maintainers
13441344+ can now more easily write AppArmor profiles for NixOS. The
13451345+ most notable change on the user-side is the new option
13461346+ <link xlink:href="options.html#opt-security.apparmor.policies">security.apparmor.policies</link>,
13471347+ replacing the previous <literal>profiles</literal> option to
13481348+ provide a way to disable a profile and to select whether to
13491349+ confine in enforce mode (default) or in complain mode (see
13501350+ <literal>journalctl -b --grep apparmor</literal>).
13511351+ Security-minded users may also want to enable
13521352+ <link xlink:href="options.html#opt-security.apparmor.killUnconfinedConfinables">security.apparmor.killUnconfinedConfinables</link>,
13531353+ at the cost of having some of their processes killed when
13541354+ updating to a NixOS version introducing new AppArmor profiles.
13551355+ </para>
13561356+ </listitem>
13571357+ <listitem>
13581358+ <para>
13591359+ The GNOME desktop manager once again installs gnome.epiphany
13601360+ by default.
13611361+ </para>
13621362+ </listitem>
13631363+ <listitem>
13641364+ <para>
13651365+ NixOS now generates empty <literal>/etc/netgroup</literal>.
13661366+ <literal>/etc/netgroup</literal> defines network-wide groups
13671367+ and may affect to setups using NIS.
13681368+ </para>
13691369+ </listitem>
13701370+ <listitem>
13711371+ <para>
13721372+ Platforms, like <literal>stdenv.hostPlatform</literal>, no
13731373+ longer have a <literal>platform</literal> attribute. It has
13741374+ been (mostly) flattened away:
13751375+ </para>
13761376+ <itemizedlist>
13771377+ <listitem>
13781378+ <para>
13791379+ <literal>platform.gcc</literal> is now
13801380+ <literal>gcc</literal>
13811381+ </para>
13821382+ </listitem>
13831383+ <listitem>
13841384+ <para>
13851385+ <literal>platform.kernel*</literal> is now
13861386+ <literal>linux-kernel.*</literal>
13871387+ </para>
13881388+ </listitem>
13891389+ </itemizedlist>
13901390+ <para>
13911391+ Additionally, <literal>platform.kernelArch</literal> moved to
13921392+ the top level as <literal>linuxArch</literal> to match the
13931393+ other <literal>*Arch</literal> variables.
13941394+ </para>
13951395+ <para>
13961396+ The <literal>platform</literal> grouping of these things never
13971397+ meant anything, and was just a historial/implementation
13981398+ artifact that was overdue removal.
13991399+ </para>
14001400+ </listitem>
14011401+ <listitem>
14021402+ <para>
14031403+ <literal>services.restic</literal> now uses a dedicated cache
14041404+ directory for every backup defined in
14051405+ <literal>services.restic.backups</literal>. The old global
14061406+ cache directory, <literal>/root/.cache/restic</literal>, is
14071407+ now unused and can be removed to free up disk space.
14081408+ </para>
14091409+ </listitem>
14101410+ <listitem>
14111411+ <para>
14121412+ <literal>isync</literal>: The <literal>isync</literal>
14131413+ compatibility wrapper was removed and the Master/Slave
14141414+ terminology has been deprecated and should be replaced with
14151415+ Far/Near in the configuration file.
14161416+ </para>
14171417+ </listitem>
14181418+ <listitem>
14191419+ <para>
14201420+ The nix-gc service now accepts randomizedDelaySec (default: 0)
14211421+ and persistent (default: true) parameters. By default nix-gc
14221422+ will now run immediately if it would have been triggered at
14231423+ least once during the time when the timer was inactive.
14241424+ </para>
14251425+ </listitem>
14261426+ <listitem>
14271427+ <para>
14281428+ The <literal>rustPlatform.buildRustPackage</literal> function
14291429+ is split into several hooks: cargoSetupHook to set up
14301430+ vendoring for Cargo-based projects, cargoBuildHook to build a
14311431+ project using Cargo, cargoInstallHook to install a project
14321432+ using Cargo, and cargoCheckHook to run tests in Cargo-based
14331433+ projects. With this change, mixed-language projects can use
14341434+ the relevant hooks within builders other than
14351435+ <literal>buildRustPackage</literal>. However, these changes
14361436+ also required several API changes to
14371437+ <literal>buildRustPackage</literal> itself:
14381438+ </para>
14391439+ <itemizedlist>
14401440+ <listitem>
14411441+ <para>
14421442+ The <literal>target</literal> argument was removed.
14431443+ Instead, <literal>buildRustPackage</literal> will always
14441444+ use the same target as the C/C++ compiler that is used.
14451445+ </para>
14461446+ </listitem>
14471447+ <listitem>
14481448+ <para>
14491449+ The <literal>cargoParallelTestThreads</literal> argument
14501450+ was removed. Parallel tests are now disabled through
14511451+ <literal>dontUseCargoParallelTests</literal>.
14521452+ </para>
14531453+ </listitem>
14541454+ </itemizedlist>
14551455+ </listitem>
14561456+ <listitem>
14571457+ <para>
14581458+ The <literal>rustPlatform.maturinBuildHook</literal> hook was
14591459+ added. This hook can be used with
14601460+ <literal>buildPythonPackage</literal> to build Python packages
14611461+ that are written in Rust and use Maturin as their build tool.
14621462+ </para>
14631463+ </listitem>
14641464+ <listitem>
14651465+ <para>
14661466+ Kubernetes has
14671467+ <link xlink:href="https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/">deprecated
14681468+ docker</link> as container runtime. As a consequence, the
14691469+ Kubernetes module now has support for configuration of custom
14701470+ remote container runtimes and enables containerd by default.
14711471+ Note that containerd is more strict regarding container image
14721472+ OCI-compliance. As an example, images with CMD or ENTRYPOINT
14731473+ defined as strings (not lists) will fail on containerd, while
14741474+ working fine on docker. Please test your setup and container
14751475+ images with containerd prior to upgrading.
14761476+ </para>
14771477+ </listitem>
14781478+ <listitem>
14791479+ <para>
14801480+ The GitLab module now has support for automatic backups. A
14811481+ schedule can be set with the
14821482+ <link xlink:href="options.html#opt-services.gitlab.backup.startAt">services.gitlab.backup.startAt</link>
14831483+ option.
14841484+ </para>
14851485+ </listitem>
14861486+ <listitem>
14871487+ <para>
14881488+ Prior to this release, systemd would also read system units
14891489+ from an undocumented
14901490+ <literal>/etc/systemd-mutable/system</literal> path. This path
14911491+ has been dropped from the defaults. That path (or others) can
14921492+ be re-enabled by adding it to the
14931493+ <link xlink:href="options.html#opt-boot.extraSystemdUnitPaths">boot.extraSystemdUnitPaths</link>
14941494+ list.
14951495+ </para>
14961496+ </listitem>
14971497+ <listitem>
14981498+ <para>
14991499+ PostgreSQL 9.5 is scheduled EOL during the 21.05 life cycle
15001500+ and has been removed.
15011501+ </para>
15021502+ </listitem>
15031503+ <listitem>
15041504+ <para>
15051505+ <link xlink:href="https://www.xfce.org/">Xfce4</link> relies
15061506+ on GIO/GVfs for userspace virtual filesystem access in
15071507+ applications like
15081508+ <link xlink:href="https://docs.xfce.org/xfce/thunar/">thunar</link>
15091509+ and
15101510+ <link xlink:href="https://docs.xfce.org/apps/gigolo/">gigolo</link>.
15111511+ For that to work, the gvfs nixos service is enabled by
15121512+ default, and it can be configured with the specific package
15131513+ that provides GVfs. Until now Xfce4 was setting it to use a
15141514+ lighter version of GVfs (without support for samba). To avoid
15151515+ conflicts with other desktop environments this setting has
15161516+ been dropped. Users that still want it should add the
15171517+ following to their system configuration:
15181518+ </para>
15191519+ <programlisting language="bash">
15201520+{
15211521+ services.gvfs.package = pkgs.gvfs.override { samba = null; };
15221522+}
15231523+</programlisting>
15241524+ </listitem>
15251525+ <listitem>
15261526+ <para>
15271527+ The newly enabled <literal>systemd-pstore.service</literal>
15281528+ now automatically evacuates crashdumps and panic logs from the
15291529+ persistent storage to
15301530+ <literal>/var/lib/systemd/pstore</literal>. This prevents
15311531+ NVRAM from filling up, which ensures the latest diagnostic
15321532+ data is always stored and alleviates problems with writing new
15331533+ boot configurations.
15341534+ </para>
15351535+ </listitem>
15361536+ <listitem>
15371537+ <para>
15381538+ Nixpkgs now contains
15391539+ <link xlink:href="https://github.com/NixOS/nixpkgs/pull/118232">automatically
15401540+ packaged GNOME Shell extensions</link> from the
15411541+ <link xlink:href="https://extensions.gnome.org/">GNOME
15421542+ Extensions</link> portal. You can find them, filed by their
15431543+ UUID, under <literal>gnome38Extensions</literal> attribute for
15441544+ GNOME 3.38 and under <literal>gnome40Extensions</literal> for
15451545+ GNOME 40. Finally, the <literal>gnomeExtensions</literal>
15461546+ attribute contains extensions for the latest GNOME Shell
15471547+ version in Nixpkgs, listed under a more human-friendly name.
15481548+ The unqualified attribute scope also contains manually
15491549+ packaged extensions. Note that the automatically packaged
15501550+ extensions are provided for convenience and are not checked or
15511551+ guaranteed to work.
15521552+ </para>
15531553+ </listitem>
15541554+ <listitem>
15551555+ <para>
15561556+ Erlang/OTP versions older than R21 got dropped. We also
15571557+ dropped the cuter package, as it was purely an example of how
15581558+ to build a package. We also dropped <literal>lfe_1_2</literal>
15591559+ as it could not build with R21+. Moving forward, we expect to
15601560+ only support 3 yearly releases of OTP.
15611561+ </para>
15621562+ </listitem>
15631563+ </itemizedlist>
15641564+ </section>
15651565+</section>
···341341 attempts from the SSH logs.
342342 </para>
343343 </listitem>
344344+ <listitem>
345345+ <para>
346346+ Sway: The terminal emulator <literal>rxvt-unicode</literal> is
347347+ no longer installed by default via
348348+ <literal>programs.sway.extraPackages</literal>. The current
349349+ default configuration uses <literal>alacritty</literal> (and
350350+ soon <literal>foot</literal>) so this is only an issue when
351351+ using a customized configuration and not installing
352352+ <literal>rxvt-unicode</literal> explicitly.
353353+ </para>
354354+ </listitem>
344355 </itemizedlist>
345356 </section>
346357</section>
···11+# Release 21.05 ("Okapi", 2021.05/31) {#sec-release-21.05}
22+33+Support is planned until the end of December 2021, handing over to 21.11.
44+55+## Highlights {#sec-release-21.05-highlights}
66+77+In addition to numerous new and upgraded packages, this release has the following highlights:
88+99+- Core version changes:
1010+1111+ - gcc: 9.3.0 -\> 10.3.0
1212+1313+ - glibc: 2.30 -\> 2.32
1414+1515+ - default linux: 5.4 -\> 5.10, all supported kernels available
1616+1717+ - mesa: 20.1.7 -\> 21.0.1
1818+1919+- Desktop Environments:
2020+2121+ - GNOME: 3.36 -\> 40, see its [release notes](https://help.gnome.org/misc/release-notes/40.0/)
2222+2323+ - Plasma5: 5.18.5 -\> 5.21.3
2424+2525+ - kdeApplications: 20.08.1 -\> 20.12.3
2626+2727+ - cinnamon: 4.6 -\> 4.8.1
2828+2929+- Programming Languages and Frameworks:
3030+3131+ - Python optimizations were disabled again. Builds with optimizations enabled are not reproducible. Optimizations can now be enabled with an option.
3232+3333+- The linux_latest kernel was updated to the 5.12 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).
3434+3535+## New Services {#sec-release-21.05-new-services}
3636+3737+The following new services were added since the last release:
3838+3939+- [GNURadio](https://www.gnuradio.org/) 3.8 was [finally](https://github.com/NixOS/nixpkgs/issues/82263) 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` 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](https://github.com/NixOS/nixpkgs/issues/75478)).
4040+4141+- [Keycloak](https://www.keycloak.org/), an open source identity and access management server with support for [OpenID Connect](https://openid.net/connect/), [OAUTH 2.0](https://oauth.net/2/) and [SAML 2.0](https://en.wikipedia.org/wiki/SAML_2.0).
4242+4343+ See the [Keycloak section of the NixOS manual](#module-services-keycloak) for more information.
4444+4545+- [services.samba-wsdd.enable](options.html#opt-services.samba-wsdd.enable) Web Services Dynamic Discovery host daemon
4646+4747+- [Discourse](https://www.discourse.org/), a modern and open source discussion platform.
4848+4949+ See the [Discourse section of the NixOS manual](#module-services-discourse) for more information.
5050+5151+- [services.nebula.networks](options.html#opt-services.nebula.networks) [Nebula VPN](https://github.com/slackhq/nebula)
5252+5353+## Backward Incompatibilities {#sec-release-21.05-incompatibilities}
5454+5555+When upgrading from a previous release, please be aware of the following incompatible changes:
5656+5757+- GNOME desktop environment was upgraded to 40, see the release notes for [40.0](https://help.gnome.org/misc/release-notes/40.0/) and [3.38](https://help.gnome.org/misc/release-notes/3.38/). The `gnome3` attribute set has been renamed to `gnome` and so have been the NixOS options.
5858+5959+- 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](#sec-custom-ifnames) section of the NixOS manual for an example using networkd links.
6060+6161+- The `security.hideProcessInformation` module has been removed. It was broken since the switch to cgroups-v2.
6262+6363+- The `linuxPackages.ati_drivers_x11` kernel modules have been removed. The drivers only supported kernels prior to 4.2, and thus have become obsolete.
6464+6565+- 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.
6666+6767+- `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](https://github.com/parse-nl/SystemdJournal2Gelf/issues/10).
6868+6969+- 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.
7070+7171+- 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 {}`.
7272+7373+- `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](https://github.com/NixOS/nixpkgs/pull/90151) for more info.
7474+7575+- 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`!
7676+7777+- The option `fonts.enableFontDir` has been renamed to [fonts.fontDir.enable](options.html#opt-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.
7878+7979+- 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`.
8080+8181+- The socket for the `pdns-recursor` module was moved from `/var/lib/pdns-recursor` to `/run/pdns-recursor` to match upstream.
8282+8383+- 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](https://forum.openpaper.work/t/paperwork-2-0/112/5) for more details.
8484+8585+- PowerDNS has been updated from `4.2.x` to `4.3.x`. Please be sure to review the [Upgrade Notes](https://doc.powerdns.com/authoritative/upgrading.html#x-to-4-3-0) 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`.
8686+8787+- 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:
8888+8989+ ```nix
9090+ {
9191+ services.mediatomb.package = pkgs.mediatomb;
9292+ }
9393+ ```
9494+9595+ 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:
9696+9797+ ```nix
9898+ {
9999+ services.mediatomb.openFirewall = true;
100100+ }
101101+ ```
102102+103103+- 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`.
104104+105105+- 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](options.html#opt-services.uwsgi.capabilities). The previous behaviour can be restored by setting:
106106+107107+ ```nix
108108+ {
109109+ services.uwsgi.user = "root";
110110+ services.uwsgi.group = "root";
111111+ services.uwsgi.instance =
112112+ {
113113+ uid = "uwsgi";
114114+ gid = "uwsgi";
115115+ };
116116+ }
117117+ ```
118118+119119+ 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.
120120+121121+- btc1 has been abandoned upstream, and removed.
122122+123123+- cpp_ethereum (aleth) has been abandoned upstream, and removed.
124124+125125+- riak-cs package removed along with `services.riak-cs` module.
126126+127127+- stanchion package removed along with `services.stanchion` module.
128128+129129+- 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](http://www.mutt.org/relnotes/2.0/).
130130+131131+- `vim` and `neovim` switched to Python 3, dropping all Python 2 support.
132132+133133+- [networking.wireguard.interfaces.\<name\>.generatePrivateKeyFile](options.html#opt-networking.wireguard.interfaces), 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](https://github.com/NixOS/nixpkgs/pull/121294).
134134+135135+- [boot.zfs.forceImportAll](options.html#opt-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.
136136+137137+- openafs now points to openafs_1_8, which is the new stable release. OpenAFS 1.6 was removed.
138138+139139+- 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](https://lists.zx2c4.com/pipermail/wireguard/2017-November/002028.html)).
140140+141141+- 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](https://mariadb.com/kb/en/upgrading-from-mariadb-104-to-mariadb-105/#incompatible-changes-between-104-and-105). After the upgrade you will need to run `mysql_upgrade`.
142142+143143+- 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](https://mariadb.com/kb/en/tokudb/) and [MDEV-19780: Remove the TokuDB storage engine](https://jira.mariadb.org/browse/MDEV-19780).
144144+145145+- 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`.
146146+147147+ 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.
148148+149149+ ```ShellSession
150150+ $ TMPDIR=$(mktemp -d)
151151+ $ slaptest -f /path/to/slapd.conf -F $TMPDIR
152152+ $ slapcat -F $TMPDIR -n0 -H 'ldap:///???(!(objectClass=olcSchemaConfig))'
153153+ ```
154154+155155+ 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.
156156+157157+- 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.
158158+159159+ ::: {.warning}
160160+ 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`.
161161+ :::
162162+163163+- 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`.
164164+165165+- 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:
166166+167167+ ```nix
168168+ {
169169+ opt-services.privoxy.enable = true;
170170+ opt-services.privoxy.enableTor = true;
171171+ }
172172+ ```
173173+174174+- The `services.tor` module has a new exhaustively typed [services.tor.settings](options.html#opt-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](options.html#opt-services.tor.relay.onionServices). A new [services.tor.openFirewall](options.html#opt-services.tor.openFirewall) option as been introduced for allowing connections on all the TCP ports configured.
175175+176176+- 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.
177177+178178+- The `wafHook` hook does not wrap Python anymore. Packages depending on `wafHook` need to include any Python into their `nativeBuildInputs`.
179179+180180+- 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](options.html#opt-system.stateVersion), existing installations will continue to work.
181181+182182+- 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.
183183+184184+- 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:
185185+186186+ ```
187187+ http://some.json-exporter.host:7979/probe?target=https://example.com/some/json/endpoint
188188+ ```
189189+190190+ 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.
191191+192192+ These changes also affect [services.prometheus.exporters.rspamd.enable](options.html#opt-services.prometheus.exporters.rspamd.enable), which is just a preconfigured instance of the json exporter.
193193+194194+ For more information, take a look at the [ official documentation](https://github.com/prometheus-community/json_exporter) of the json_exporter.
195195+196196+- 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.
197197+198198+ 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.
199199+200200+- 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:
201201+202202+ ```nix
203203+ self: super:
204204+ {
205205+ mpi = super.mpich;
206206+ }
207207+ ```
208208+209209+- 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](options.html#opt-services.searx.settingsFile) for consistency with the new [services.searx.settings](options.html#opt-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.
210210+211211+- 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.
212212+213213+ Since touchpad options no longer apply to all devices, you may want to replicate your touchpad configuration in mouse section.
214214+215215+- ALSA OSS emulation (`sound.enableOSSEmulation`) is now disabled by default.
216216+217217+- 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](options.html#opt-services.thinkfan.settings) option has been added.
218218+219219+ Please read the [ thinkfan documentation](https://github.com/vmatare/thinkfan#readme) before updating.
220220+221221+- Adobe Flash Player support has been dropped from the tree. In particular, the following packages no longer support it:
222222+223223+ - chromium
224224+225225+ - firefox
226226+227227+ - qt48
228228+229229+ - qt5.qtwebkit
230230+231231+ Additionally, packages flashplayer and hal-flash were removed along with the `services.flashpolicyd` module.
232232+233233+- 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.
234234+235235+ 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](options.html#opt-services.gitlab.smtp.port) option.
236236+237237+- 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.
238238+239239+- [services.xserver.videoDrivers](options.html#opt-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.
240240+241241+- 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](https://github.com/NixOS/nixpkgs/issues/96439) for more info.
242242+243243+- 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](options.html#opt-services.apache-kafka.jre) option. Furthermore, the default list of [services.apache-kafka.jvmOptions](options.html#opt-services.apache-kafka.jvmOptions) have been removed. You should set your own according to the [upstream documentation](https://kafka.apache.org/documentation/#java) for your Kafka version.
244244+245245+- 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:
246246+247247+ ```nix
248248+ {
249249+ environment.systemPackages = [
250250+ pkgs.kodi
251251+ ];
252252+253253+ nixpkgs.config.kodi = {
254254+ enableInputStreamAdaptive = true;
255255+ enableVFSSFTP = true;
256256+ };
257257+ }
258258+ ```
259259+260260+ All Kodi `config` flags have been removed, and as a result the above configuration should now be written as:
261261+262262+ ```nix
263263+ {
264264+ environment.systemPackages = [
265265+ (pkgs.kodi.withPackages (p: with p; [
266266+ inputstream-adaptive
267267+ vfs-sftp
268268+ ]))
269269+ ];
270270+ }
271271+ ```
272272+273273+- `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`.
274274+275275+- `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.
276276+277277+- All CUDA toolkit versions prior to CUDA 10 have been removed.
278278+279279+- 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`.
280280+281281+- 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`.
282282+283283+- The `services.zigbee2mqtt.config` option has been renamed to `services.zigbee2mqtt.settings` and now follows [RFC 0042](https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md).
284284+285285+ 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.
286286+287287+- Instead of determining `services.radicale.package` automatically based on `system.stateVersion`, the latest version is always used because old versions are not officially supported.
288288+289289+ 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.
290290+291291+- 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.
292292+293293+## Other Notable Changes {#sec-release-21.05-notable-changes}
294294+295295+- `stdenv.lib` has been deprecated and will break eval in 21.11. Please use `pkgs.lib` instead. See [\#108938](https://github.com/NixOS/nixpkgs/issues/108938) for details.
296296+297297+- [GNURadio](https://www.gnuradio.org/) 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.
298298+299299+- [Privoxy](https://www.privoxy.org/) has been updated to version 3.0.32 (See [announcement](https://lists.privoxy.org/pipermail/privoxy-announce/2021-February/000007.html)). 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.
300300+301301+ 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](options.html#opt-services.privoxy.settings) (See [RFC 0042](https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md) for the motivation).
302302+303303+- [Kodi](https://kodi.tv/) has been updated to version 19.1 \"Matrix\". See the [announcement](https://kodi.tv/article/kodi-190-matrix-release) for further details.
304304+305305+- 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](https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md) compliant [services.packagekit.settings](options.html#opt-services.packagekit.settings) and [services.packagekit.vendorSettings](options.html#opt-services.packagekit.vendorSettings) options have been introduced.
306306+307307+- [Nginx](https://nginx.org) has been updated to stable version 1.20.0. Now nginx uses the zlib-ng library by default.
308308+309309+- KDE Gear (formerly KDE Applications) is upgraded to 21.04, see its [release notes](https://kde.org/announcements/gear/21.04/) for details.
310310+311311+ The `kdeApplications` package set is now `kdeGear`, in keeping with the new name. The old name remains for compatibility, but it is deprecated.
312312+313313+- [Libreswan](https://libreswan.org/) 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](options.html#opt-services.libreswan.policies)) and disable send/receive redirects ([services.libreswan.disableRedirects](options.html#opt-services.libreswan.disableRedirects)).
314314+315315+- The Mailman NixOS module (`services.mailman`) has a new option [services.mailman.enablePostfix](options.html#opt-services.mailman.enablePostfix), defaulting to true, that controls integration with Postfix.
316316+317317+ 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](https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html).
318318+319319+- 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.
320320+321321+ The package can be manually upgraded by setting [services.nextcloud.package](options.html#opt-services.nextcloud.package) to nextcloud21.
322322+323323+- The setting [services.redis.bind](options.html#opt-services.redis.bind) defaults to `127.0.0.1` now, making Redis listen on the loopback interface only, and not all public network interfaces.
324324+325325+- 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](https://github.com/NixOS/nixpkgs/issues/45785) for details.
326326+327327+ All services should use [systemd.services._name_.startLimitIntervalSec](options.html#opt-systemd.services._name_.startLimitIntervalSec) or `StartLimitIntervalSec` in [systemd.services._name_.unitConfig](options.html#opt-systemd.services._name_.unitConfig) instead.
328328+329329+- 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:
330330+331331+ ```nix
332332+ {
333333+ services.mediatomb.mediaDirectories = [
334334+ { path = "/var/lib/mediatomb/pictures"; recursive = false; hidden-files = false; }
335335+ { path = "/var/lib/mediatomb/audio"; recursive = true; hidden-files = false; }
336336+ ];
337337+ }
338338+ ```
339339+340340+- The Unbound DNS resolver service (`services.unbound`) has been refactored to allow reloading, control sockets and to fix startup ordering issues.
341341+342342+ It is now possible to enable a local UNIX control socket for unbound by setting the [services.unbound.localControlSocketPath](options.html#opt-services.unbound.localControlSocketPath) option.
343343+344344+ Previously we just applied a very minimal set of restrictions and trusted unbound to properly drop root privs and capabilities.
345345+346346+ 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.
347347+348348+ 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.
349349+350350+ 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.
351351+352352+ The `preStart` script is now only required if we enabled the trust anchor updates (which are still enabled by default).
353353+354354+ 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.
355355+356356+ The module has also been reworked to be [RFC 0042](https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md) compliant. As such, `sevices.unbound.extraConfig` has been removed and replaced by [services.unbound.settings](options.html#opt-services.unbound.settings). `services.unbound.interfaces` has been renamed to `services.unbound.settings.server.interface`.
357357+358358+ `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.
359359+360360+- 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.
361361+362362+- NixOS now defaults to the unified cgroup hierarchy (cgroupsv2). See the [Fedora Article for 31](https://www.redhat.com/sysadmin/fedora-31-control-group-v2) for details on why this is desirable, and how it impacts containers.
363363+364364+ 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](options.html#opt-systemd.enableUnifiedCgroupHierarchy) = `false`; and rebooting.
365365+366366+- PulseAudio was upgraded to 14.0, with changes to the handling of default sinks. See its [release notes](https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/14.0/).
367367+368368+- GNOME users may wish to delete their `~/.config/pulse` due to the changes to stream routing logic. See [PulseAudio bug 832](https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/832) for more information.
369369+370370+- The zookeeper package does not provide `zooInspector.sh` anymore, as that \"contrib\" has been dropped from upstream releases.
371371+372372+- In the ACME module, the data used to build the hash for the account directory has changed to accomodate 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.
373373+374374+- [users.users._name_.createHome](options.html#opt-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.
375375+376376+- When defining a new user, one of [users.users._name_.isNormalUser](options.html#opt-users.users._name_.isNormalUser) and [users.users._name_.isSystemUser](options.html#opt-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](options.html#opt-users.users._name_.isSystemUser) has no effect for those.
377377+378378+- The `security.apparmor` module, for the [AppArmor](https://gitlab.com/apparmor/apparmor/-/wikis/Documentation) 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](options.html#opt-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](options.html#opt-security.apparmor.killUnconfinedConfinables), at the cost of having some of their processes killed when updating to a NixOS version introducing new AppArmor profiles.
379379+380380+- The GNOME desktop manager once again installs gnome.epiphany by default.
381381+382382+- NixOS now generates empty `/etc/netgroup`. `/etc/netgroup` defines network-wide groups and may affect to setups using NIS.
383383+384384+- Platforms, like `stdenv.hostPlatform`, no longer have a `platform` attribute. It has been (mostly) flattened away:
385385+386386+ - `platform.gcc` is now `gcc`
387387+388388+ - `platform.kernel*` is now `linux-kernel.*`
389389+390390+ Additionally, `platform.kernelArch` moved to the top level as `linuxArch` to match the other `*Arch` variables.
391391+392392+ The `platform` grouping of these things never meant anything, and was just a historial/implementation artifact that was overdue removal.
393393+394394+- `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.
395395+396396+- `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.
397397+398398+- 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.
399399+400400+- 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:
401401+402402+ - The `target` argument was removed. Instead, `buildRustPackage` will always use the same target as the C/C++ compiler that is used.
403403+404404+ - The `cargoParallelTestThreads` argument was removed. Parallel tests are now disabled through `dontUseCargoParallelTests`.
405405+406406+- 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.
407407+408408+- Kubernetes has [deprecated docker](https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-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.
409409+410410+- The GitLab module now has support for automatic backups. A schedule can be set with the [services.gitlab.backup.startAt](options.html#opt-services.gitlab.backup.startAt) option.
411411+412412+- 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](options.html#opt-boot.extraSystemdUnitPaths) list.
413413+414414+- PostgreSQL 9.5 is scheduled EOL during the 21.05 life cycle and has been removed.
415415+416416+- [Xfce4](https://www.xfce.org/) relies on GIO/GVfs for userspace virtual filesystem access in applications like [thunar](https://docs.xfce.org/xfce/thunar/) and [gigolo](https://docs.xfce.org/apps/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:
417417+418418+ ```nix
419419+ {
420420+ services.gvfs.package = pkgs.gvfs.override { samba = null; };
421421+ }
422422+ ```
423423+424424+- 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.
425425+426426+- Nixpkgs now contains [automatically packaged GNOME Shell extensions](https://github.com/NixOS/nixpkgs/pull/118232) from the [GNOME Extensions](https://extensions.gnome.org/) 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.
427427+428428+- 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.
-1266
nixos/doc/manual/release-notes/rl-2105.xml
···11-<section xmlns="http://docbook.org/ns/docbook"
22- xmlns:xlink="http://www.w3.org/1999/xlink"
33- xmlns:xi="http://www.w3.org/2001/XInclude"
44- version="5.0"
55- xml:id="sec-release-21.05">
66- <title>Release 21.05 (“Okapi”, 2021.05/31)</title>
77-88- <para>
99- Support is planned until the end of December 2021, handing over to 21.11.
1010- </para>
1111- <section xmlns="http://docbook.org/ns/docbook"
1212- xmlns:xlink="http://www.w3.org/1999/xlink"
1313- xmlns:xi="http://www.w3.org/2001/XInclude"
1414- version="5.0"
1515- xml:id="sec-release-21.05-highlights">
1616- <title>Highlights</title>
1717-1818- <para>
1919- In addition to numerous new and upgraded packages, this release has the
2020- following highlights:
2121- </para>
2222-2323- <itemizedlist>
2424-2525- <listitem>
2626- <para>
2727- Core version changes:
2828- </para>
2929- <itemizedlist>
3030- <listitem>
3131- <para>
3232- gcc: 9.3.0 -> 10.3.0
3333- </para>
3434- </listitem>
3535- <listitem>
3636- <para>
3737- glibc: 2.30 -> 2.32
3838- </para>
3939- </listitem>
4040- <listitem>
4141- <para>
4242- default linux: 5.4 -> 5.10, all supported kernels available
4343- </para>
4444- </listitem>
4545- <listitem>
4646- <para>
4747- mesa: 20.1.7 -> 21.0.1
4848- </para>
4949- </listitem>
5050- </itemizedlist>
5151- </listitem>
5252- <listitem>
5353- <para>
5454- Desktop Environments:
5555- </para>
5656- <itemizedlist>
5757- <listitem>
5858- <para>
5959- GNOME: 3.36 -> 40, see its <link xlink:href="https://help.gnome.org/misc/release-notes/40.0/">release notes</link>
6060- </para>
6161- </listitem>
6262- <listitem>
6363- <para>
6464- Plasma5: 5.18.5 -> 5.21.3
6565- </para>
6666- </listitem>
6767- <listitem>
6868- <para>
6969- kdeApplications: 20.08.1 -> 20.12.3
7070- </para>
7171- </listitem>
7272- <listitem>
7373- <para>
7474- cinnamon: 4.6 -> 4.8.1
7575- </para>
7676- </listitem>
7777- </itemizedlist>
7878- </listitem>
7979-8080- <listitem>
8181- <para>
8282- Programming Languages and Frameworks:
8383- </para>
8484- <itemizedlist>
8585-8686- <listitem>
8787- <para>
8888- Python optimizations were disabled again. Builds with optimizations enabled
8989- are not reproducible. Optimizations can now be enabled with an option.
9090- </para>
9191- </listitem>
9292-9393- </itemizedlist>
9494- </listitem>
9595- <listitem>
9696- <para>The <package>linux_latest</package> kernel was updated to the 5.12 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). </para>
9797- </listitem>
9898-9999- </itemizedlist>
100100- </section>
101101-102102- <section xmlns="http://docbook.org/ns/docbook"
103103- xmlns:xlink="http://www.w3.org/1999/xlink"
104104- xmlns:xi="http://www.w3.org/2001/XInclude"
105105- version="5.0"
106106- xml:id="sec-release-21.05-new-services">
107107- <title>New Services</title>
108108-109109- <para>
110110- The following new services were added since the last release:
111111- </para>
112112-113113- <itemizedlist>
114114- <listitem>
115115- <para>
116116- <link xlink:href="https://www.gnuradio.org/">GNURadio</link> 3.8 and 3.9 were
117117- <link xlink:href="https://github.com/NixOS/nixpkgs/issues/82263">finally</link>
118118- packaged, along with a rewrite to the Nix expressions, allowing users to
119119- override the features upstream supports selecting to compile or not to.
120120- Additionally, the attribute <code>gnuradio</code> (3.9), <code>gnuradio3_8</code> and <code>gnuradio3_7</code>
121121- now point to an externally wrapped by default derivations, that allow you to
122122- also add `extraPythonPackages` to the Python interpreter used by GNURadio.
123123- Missing environmental variables needed for operational GUI were also added
124124- (<link xlink:href="https://github.com/NixOS/nixpkgs/issues/75478">#75478</link>).
125125- </para>
126126- </listitem>
127127-128128- <listitem>
129129- <para>
130130- <link xlink:href="https://www.keycloak.org/">Keycloak</link>,
131131- an open source identity and access management server with
132132- support for <link
133133- xlink:href="https://openid.net/connect/">OpenID Connect</link>,
134134- <link xlink:href="https://oauth.net/2/">OAUTH 2.0</link> and
135135- <link xlink:href="https://en.wikipedia.org/wiki/SAML_2.0">SAML
136136- 2.0</link>.
137137- </para>
138138- <para>
139139- See the <link linkend="module-services-keycloak">Keycloak
140140- section of the NixOS manual</link> for more information.
141141- </para>
142142- </listitem>
143143- <listitem>
144144- <para>
145145- <xref linkend="opt-services.samba-wsdd.enable" /> Web Services Dynamic Discovery host daemon
146146- </para>
147147- </listitem>
148148- <listitem>
149149- <para>
150150- <link xlink:href="https://www.discourse.org/">Discourse</link>, a
151151- modern and open source discussion platform.
152152- </para>
153153- <para>
154154- See the <link linkend="module-services-discourse">Discourse
155155- section of the NixOS manual</link> for more information.
156156- </para>
157157- </listitem>
158158- <listitem>
159159- <para>
160160- <xref linkend="opt-services.nebula.networks" /> <link xlink:href="https://github.com/slackhq/nebula">Nebula VPN</link>
161161- </para>
162162- </listitem>
163163- </itemizedlist>
164164-165165- </section>
166166-167167- <section xmlns="http://docbook.org/ns/docbook"
168168- xmlns:xlink="http://www.w3.org/1999/xlink"
169169- xmlns:xi="http://www.w3.org/2001/XInclude"
170170- version="5.0"
171171- xml:id="sec-release-21.05-incompatibilities">
172172- <title>Backward Incompatibilities</title>
173173-174174- <para>
175175- When upgrading from a previous release, please be aware of the following
176176- incompatible changes:
177177- </para>
178178-179179- <itemizedlist>
180180- <listitem>
181181- <para>GNOME desktop environment was upgraded to 40, see the release notes for <link xlink:href="https://help.gnome.org/misc/release-notes/40.0/">40.0</link> and <link xlink:href="https://help.gnome.org/misc/release-notes/3.38/">3.38</link>. The <code>gnome3</code> attribute set has been renamed to <code>gnome</code> and so have been the NixOS options.</para>
182182- </listitem>
183183-184184- <listitem>
185185- <para>
186186- If you are using <option>services.udev.extraRules</option> to assign
187187- custom names to network interfaces, this may stop working due to a change
188188- in the initialisation of dhcpcd and systemd networkd. To avoid this, either
189189- move them to <option>services.udev.initrdRules</option> or see the new
190190- <link linkend="sec-custom-ifnames">Assigning custom names</link> section
191191- of the NixOS manual for an example using networkd links.
192192- </para>
193193- </listitem>
194194- <listitem>
195195- <para>
196196- The <option>security.hideProcessInformation</option> module has been removed.
197197- It was broken since the switch to cgroups-v2.
198198- </para>
199199- </listitem>
200200- <listitem>
201201- <para>
202202- The <literal>linuxPackages.ati_drivers_x11</literal> kernel modules have been removed.
203203- The drivers only supported kernels prior to 4.2, and thus have become obsolete.
204204- </para>
205205- </listitem>
206206- <listitem>
207207- <para>
208208- The <literal>systemConfig</literal> 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.
209209- </para>
210210- </listitem>
211211- <listitem>
212212- <para>
213213- <literal>systemd-journal2gelf</literal> no longer parses json and expects the receiving system to handle it. How to achieve this with Graylog is described in this <link xlink:href="https://github.com/parse-nl/SystemdJournal2Gelf/issues/10">GitHub issue</link>.
214214- </para>
215215- </listitem>
216216- <listitem>
217217- <para>
218218- If the <varname>services.dbus</varname> module is enabled, then
219219- the user D-Bus session is now always socket activated. The
220220- associated options <varname>services.dbus.socketActivated</varname>
221221- and <varname>services.xserver.startDbusSession</varname> have
222222- therefore been removed and you will receive a warning if
223223- they are present in your configuration. This change makes the
224224- user D-Bus session available also for non-graphical logins.
225225- </para>
226226- </listitem>
227227- <listitem>
228228- <para>
229229- The <varname>networking.wireless.iwd</varname> module now installs
230230- the upstream-provided 80-iwd.link file, which sets the NamePolicy=
231231- for all wlan devices to "keep kernel", to avoid race conditions
232232- between iwd and networkd. If you don't want this, you can set
233233- <literal>systemd.network.links."80-iwd" = lib.mkForce {}</literal>.
234234- </para>
235235- </listitem>
236236- <listitem>
237237- <para>
238238- <literal>rubyMinimal</literal> was removed due to being unused and
239239- unusable. The default ruby interpreter includes JIT support, which makes
240240- it reference it's compiler. Since JIT support is probably needed by some
241241- Gems, it was decided to enable this feature with all cc references by
242242- default, and allow to build a Ruby derivation without references to cc,
243243- by setting <literal>jitSupport = false;</literal> in an overlay. See
244244- <link xlink:href="https://github.com/NixOS/nixpkgs/pull/90151">#90151</link>
245245- for more info.
246246- </para>
247247- </listitem>
248248- <listitem>
249249- <para>
250250- Setting <option>services.openssh.authorizedKeysFiles</option> now also affects which keys <option>security.pam.enableSSHAgentAuth</option> will use.
251251-252252- WARNING: If you are using these options in combination do make sure that any key paths you use are present in <option>services.openssh.authorizedKeysFiles</option>!
253253- </para>
254254- </listitem>
255255- <listitem>
256256- <para>
257257- The option <option>fonts.enableFontDir</option> has been renamed to
258258- <xref linkend="opt-fonts.fontDir.enable"/>. The path of font directory
259259- has also been changed to <literal>/run/current-system/sw/share/X11/fonts</literal>,
260260- for consistency with other X11 resources.
261261- </para>
262262- </listitem>
263263- <listitem>
264264- <para>
265265- A number of options have been renamed in the kicad interface. <literal>oceSupport</literal>
266266- has been renamed to <literal>withOCE</literal>, <literal>withOCCT</literal> has been renamed
267267- to <literal>withOCC</literal>, <literal>ngspiceSupport</literal> has been renamed to
268268- <literal>withNgspice</literal>, and <literal>scriptingSupport</literal> has been renamed to
269269- <literal>withScripting</literal>. Additionally, <literal>kicad/base.nix</literal> no longer
270270- provides default argument values since these are provided by
271271- <literal>kicad/default.nix</literal>.
272272- </para>
273273- </listitem>
274274- <listitem>
275275- <para>
276276- The socket for the <literal>pdns-recursor</literal> module was moved from <literal>/var/lib/pdns-recursor</literal>
277277- to <literal>/run/pdns-recursor</literal> to match upstream.
278278- </para>
279279- </listitem>
280280- <listitem>
281281- <para>
282282- Paperwork was updated to version 2. The on-disk format slightly changed,
283283- and it is not possible to downgrade from Paperwork 2 back to Paperwork
284284- 1.3. Back your documents up before upgrading. See <link xlink:href="https://forum.openpaper.work/t/paperwork-2-0/112/5">this thread</link> for more details.
285285- </para>
286286- </listitem>
287287- <listitem>
288288- <para>
289289- PowerDNS has been updated from <literal>4.2.x</literal> to <literal>4.3.x</literal>. Please
290290- be sure to review the <link xlink:href="https://doc.powerdns.com/authoritative/upgrading.html#x-to-4-3-0">Upgrade Notes</link>
291291- provided by upstream before upgrading. Worth specifically noting is that the service now runs
292292- entirely as a dedicated <literal>pdns</literal> user, instead of starting as <literal>root</literal>
293293- and dropping privileges, as well as the default <literal>socket-dir</literal> location changing from
294294- <literal>/var/lib/powerdns</literal> to <literal>/run/pdns</literal>.
295295- </para>
296296- </listitem>
297297- <listitem>
298298- <para>
299299- The <literal>mediatomb</literal> service is
300300- now using by default the new and maintained fork
301301- <literal>gerbera</literal> package instead of the unmaintained
302302- <literal>mediatomb</literal> package. If you want to keep the old
303303- behavior, you must declare it with:
304304- <programlisting>
305305- services.mediatomb.package = pkgs.mediatomb;
306306- </programlisting>
307307- One new option <literal>openFirewall</literal> has been introduced which
308308- defaults to false. If you relied on the service declaration to add the
309309- firewall rules itself before, you should now declare it with:
310310- <programlisting>
311311- services.mediatomb.openFirewall = true;
312312- </programlisting>
313313- </para>
314314- </listitem>
315315- <listitem>
316316- <para>
317317- xfsprogs was update from 4.19 to 5.11. It now enables reflink support by default on filesystem creation.
318318- Support for reflinks was added with an experimental status to kernel 4.9 and deemed stable in kernel 4.16.
319319- 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
320320- with <literal>mkfs.xfs -m reflink=0</literal>.
321321- </para>
322322- </listitem>
323323- <listitem>
324324- <para>
325325- The uWSGI server is now built with POSIX capabilities. As a consequence,
326326- root is no longer required in emperor mode and the service defaults to
327327- running as the unprivileged <literal>uwsgi</literal> user. Any additional
328328- capability can be added via the new option
329329- <xref linkend="opt-services.uwsgi.capabilities"/>.
330330- The previous behaviour can be restored by setting:
331331-<programlisting>
332332- <xref linkend="opt-services.uwsgi.user"/> = "root";
333333- <xref linkend="opt-services.uwsgi.group"/> = "root";
334334- <xref linkend="opt-services.uwsgi.instance"/> =
335335- {
336336- uid = "uwsgi";
337337- gid = "uwsgi";
338338- };
339339-</programlisting>
340340- </para>
341341- <para>
342342- Another incompatibility from the previous release is that vassals running under a
343343- different user or group need to use <literal>immediate-{uid,gid}</literal>
344344- instead of the usual <literal>uid,gid</literal> options.
345345- </para>
346346- </listitem>
347347- <listitem>
348348- <para>
349349- <package>btc1</package> has been abandoned upstream, and removed.
350350- </para>
351351- </listitem>
352352- <listitem>
353353- <para>
354354- <package>cpp_ethereum</package> (aleth) has been abandoned upstream, and removed.
355355- </para>
356356- </listitem>
357357- <listitem>
358358- <para>
359359- <package>riak-cs</package> package removed along with <varname>services.riak-cs</varname> module.
360360- </para>
361361- </listitem>
362362- <listitem>
363363- <para>
364364- <package>stanchion</package> package removed along with <varname>services.stanchion</varname> module.
365365- </para>
366366- </listitem>
367367- <listitem>
368368- <para>
369369- <package>mutt</package> has been updated to a new major version (2.x), which comes with
370370- some backward incompatible changes that are described in the
371371- <link xlink:href="http://www.mutt.org/relnotes/2.0/">release notes for Mutt 2.0</link>.
372372- </para>
373373- </listitem>
374374- <listitem>
375375- <para>
376376- <literal>vim</literal> and <literal>neovim</literal> switched to Python 3, dropping all Python 2 support.
377377- </para>
378378- </listitem>
379379- <listitem>
380380- <para>
381381- <link linkend="opt-networking.wireguard.interfaces">networking.wireguard.interfaces.<name>.generatePrivateKeyFile</link>,
382382- which is off by default, had a <literal>chmod</literal> race condition
383383- fixed. As an aside, the parent directory's permissions were widened,
384384- and the key files were made owner-writable.
385385- This only affects newly created keys.
386386- However, if the exact permissions are important for your setup, read
387387- <link xlink:href="https://github.com/NixOS/nixpkgs/pull/121294">#121294</link>.
388388- </para>
389389- </listitem>
390390- <listitem>
391391- <para>
392392- <link linkend="opt-boot.zfs.forceImportAll">boot.zfs.forceImportAll</link>
393393- previously did nothing, but has been fixed. However its default has been
394394- changed to <literal>false</literal> to preserve the existing default
395395- behaviour. If you have this explicitly set to <literal>true</literal>,
396396- please note that your non-root pools will now be forcibly imported.
397397- </para>
398398- </listitem>
399399- <listitem>
400400- <para>
401401- <package>openafs</package> now points to <package>openafs_1_8</package>,
402402- which is the new stable release. OpenAFS 1.6 was removed.
403403- </para>
404404- </listitem>
405405- <listitem>
406406- <para>
407407- The WireGuard module gained a new option
408408- <option>networking.wireguard.interfaces.<name>.peers.*.dynamicEndpointRefreshSeconds</option>
409409- that implements refreshing the IP of DNS-based endpoints periodically
410410- (which WireGuard itself
411411- <link xlink:href="https://lists.zx2c4.com/pipermail/wireguard/2017-November/002028.html">cannot do</link>).
412412- </para>
413413- </listitem>
414414- <listitem>
415415- <para>
416416- MariaDB has been updated to 10.5.
417417- Before you upgrade, it would be best to take a backup of your database and read
418418- <link xlink:href="https://mariadb.com/kb/en/upgrading-from-mariadb-104-to-mariadb-105/#incompatible-changes-between-104-and-105">
419419- Incompatible Changes Between 10.4 and 10.5</link>.
420420- After the upgrade you will need to run <literal>mysql_upgrade</literal>.
421421- </para>
422422- </listitem>
423423- <listitem>
424424- <para>
425425- The TokuDB storage engine dropped in <package>mariadb</package> 10.5 and removed in <package>mariadb</package> 10.6.
426426- It is recommended to switch to RocksDB. See also <link xlink:href="https://mariadb.com/kb/en/tokudb/">TokuDB</link> and
427427- <link xlink:href="https://jira.mariadb.org/browse/MDEV-19780">MDEV-19780: Remove the TokuDB storage engine</link>.
428428- </para>
429429- </listitem>
430430- <listitem>
431431- <para>
432432- The <literal>openldap</literal> module now has support for OLC-style
433433- configuration, users of the <literal>configDir</literal> option may wish
434434- to migrate. If you continue to use <literal>configDir</literal>, ensure that
435435- <literal>olcPidFile</literal> is set to <literal>/run/slapd/slapd.pid</literal>.
436436- </para>
437437- <para>
438438- As a result, <literal>extraConfig</literal> and <literal>extraDatabaseConfig</literal>
439439- are removed. To help with migration, you can convert your <literal>slapd.conf</literal>
440440- file to OLC configuration with the following script (find the location of this
441441- configuration file by running <literal>systemctl status openldap</literal>, it is the
442442- <literal>-f</literal> option.
443443- </para>
444444- <programlisting>
445445- TMPDIR=$(mktemp -d)
446446- slaptest -f /path/to/slapd.conf -F $TMPDIR
447447- slapcat -F $TMPDIR -n0 -H 'ldap:///???(!(objectClass=olcSchemaConfig))'
448448- </programlisting>
449449- <para>
450450- This will dump your current configuration in LDIF format, which should be
451451- straightforward to convert into Nix settings. This does not show your schema
452452- configuration, as this is unnecessarily verbose for users of the default schemas
453453- and <literal>slaptest</literal> is buggy with schemas directly in the config file.
454454- </para>
455455- </listitem>
456456- <listitem>
457457- <para>
458458- Amazon EC2 and OpenStack Compute (nova) images now re-fetch instance meta data and user data from the instance
459459- metadata service (IMDS) on each boot. For example: stopping an EC2 instance, changing its user data, and
460460- restarting the instance will now cause it to fetch and apply the new user data.
461461- </para>
462462- <warning>
463463- <para>
464464- Specifically, <literal>/etc/ec2-metadata</literal> is re-populated on each boot. Some NixOS scripts that read
465465- from this directory are guarded to only run if the files they want to manipulate do not already exist, and so
466466- will not re-apply their changes if the IMDS response changes. Examples: <literal>root</literal>'s SSH key is
467467- only added if <literal>/root/.ssh/authorized_keys</literal> does not exist, and SSH host keys are only set from
468468- user data if they do not exist in <literal>/etc/ssh</literal>.
469469- </para>
470470- </warning>
471471- </listitem>
472472- <listitem>
473473- <para>
474474- The <literal>rspamd</literal> services is now sandboxed. It is run as
475475- a dynamic user instead of root, so secrets and other files may have to
476476- be moved or their permissions may have to be fixed. The sockets are now
477477- located in <literal>/run/rspamd</literal> instead of <literal>/run</literal>.
478478- </para>
479479- </listitem>
480480- <listitem>
481481- <para>
482482- Enabling the Tor client no longer silently also enables and
483483- configures Privoxy, and the
484484- <varname>services.tor.client.privoxy.enable</varname> option has
485485- been removed. To enable Privoxy, and to configure it to use
486486- Tor's faster port, use the following configuration:
487487- </para>
488488- <programlisting>
489489- <xref linkend="opt-services.privoxy.enable" /> = true;
490490- <xref linkend="opt-services.privoxy.enableTor" /> = true;
491491- </programlisting>
492492- </listitem>
493493- <listitem>
494494- <para>
495495- The <literal>services.tor</literal> module has a new exhaustively typed <xref linkend="opt-services.tor.settings" /> option following RFC 0042; backward compatibility with old options has been preserved when aliasing was possible.
496496- The corresponding systemd service has been hardened,
497497- but there is a chance that the service still requires more permissions,
498498- so please report any related trouble on the bugtracker.
499499- Onion services v3 are now supported in <xref linkend="opt-services.tor.relay.onionServices" />.
500500- A new <xref linkend="opt-services.tor.openFirewall" /> option as been introduced for allowing connections on all the TCP ports configured.
501501- </para>
502502- </listitem>
503503- <listitem>
504504- <para>
505505- The options <literal>services.slurm.dbdserver.storagePass</literal>
506506- and <literal>services.slurm.dbdserver.configFile</literal> have been removed.
507507- Use <literal>services.slurm.dbdserver.storagePassFile</literal> instead to provide the database password.
508508- Extra config options can be given via the option <literal>services.slurm.dbdserver.extraConfig</literal>. The actual configuration file is created on the fly on startup of the service.
509509- This avoids that the password gets exposed in the nix store.
510510- </para>
511511- </listitem>
512512- <listitem>
513513- <para>
514514- The <literal>wafHook</literal> hook does not wrap Python anymore.
515515- Packages depending on <literal>wafHook</literal> need to include any Python into their <literal>nativeBuildInputs</literal>.
516516- </para>
517517- </listitem>
518518- <listitem>
519519- <para>
520520- Starting with version 1.7.0, the project formerly named <literal>CodiMD</literal>
521521- is now named <literal>HedgeDoc</literal>.
522522- 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.
523523- Based on <xref linkend="opt-system.stateVersion" />, existing installations will continue to work.
524524- </para>
525525- </listitem>
526526- <listitem>
527527- <para>
528528- The <package>fish-foreign-env</package> package has been replaced with
529529- <package>fishPlugins.foreign-env</package>, in which the fish
530530- functions have been relocated to the
531531- <literal>vendor_functions.d</literal> directory to be loaded automatically.
532532- </para>
533533- </listitem>
534534- <listitem>
535535- <para>
536536- The prometheus json exporter is now managed by the prometheus community. Together with additional features
537537- some backwards incompatibilities were introduced.
538538- Most importantly the exporter no longer accepts a fixed command-line parameter to specify the URL of the
539539- endpoint serving JSON. It now expects this URL to be passed as an URL parameter, when scraping the exporter's
540540- <literal>/probe</literal> endpoint.
541541- In the prometheus scrape configuration the scrape target might look like this:
542542- <programlisting>
543543-http://some.json-exporter.host:7979/probe?target=https://example.com/some/json/endpoint
544544- </programlisting>
545545- </para>
546546- <para>
547547- Existing configuration for the exporter needs to be updated, but can partially be re-used.
548548- Documentation is available in the upstream repository and a small example for NixOS is available
549549- in the corresponding NixOS test.
550550- </para>
551551- <para>
552552- These changes also affect <xref linkend="opt-services.prometheus.exporters.rspamd.enable" />, which is
553553- just a preconfigured instance of the json exporter.
554554- </para>
555555- <para>
556556- For more information, take a look at the <link xlink:href="https://github.com/prometheus-community/json_exporter">
557557- official documentation</link> of the json_exporter.
558558- </para>
559559- </listitem>
560560- <listitem>
561561- <para>
562562- Androidenv was updated, removing the <literal>includeDocs</literal> and <literal>lldbVersions</literal>
563563- arguments. Docs only covered a single version of the Android SDK, LLDB is now bundled with the NDK,
564564- and both are no longer available to download from the Android package repositories. Additionally, since
565565- the package lists have been updated, some older versions of Android packages may not be bundled. If you
566566- depend on older versions of Android packages, we recommend overriding the repo.
567567- </para>
568568- <para>
569569- Android packages are now loaded from a repo.json file created by parsing Android repo XML files. The arguments
570570- <literal>repoJson</literal> and <literal>repoXmls</literal> have been added to allow overriding the built-in
571571- androidenv repo.json with your own. Additionally, license files are now written to allow compatibility
572572- with Gradle-based tools, and the <literal>extraLicenses</literal> argument has been added to accept more
573573- SDK licenses if your project requires it. See the androidenv documentation for more details.
574574- </para>
575575- </listitem>
576576- <listitem>
577577- <para>
578578- The attribute <varname>mpi</varname> is now consistently used to
579579- provide a default, system-wide MPI implementation.
580580- The default implementation is openmpi, which has been used before by
581581- all derivations affects by this change.
582582- Note that all packages that have used <varname>mpi ? null</varname> in the input
583583- for optional MPI builds, have been changed to the boolean input paramater
584584- <varname>useMpi</varname> to enable building with MPI.
585585-586586- Building all packages with <varname>mpich</varname> instead
587587- of the default <varname>openmpi</varname> can now be achived like this:
588588- <programlisting>
589589-self: super:
590590-{
591591- mpi = super.mpich;
592592-}
593593- </programlisting>
594594- </para>
595595- </listitem>
596596- <listitem>
597597- <para>
598598- The Searx module has been updated with the ability to configure the
599599- service declaratively and uWSGI integration.
600600- The option <literal>services.searx.configFile</literal> has been renamed
601601- to <xref linkend="opt-services.searx.settingsFile"/> for consistency with
602602- the new <xref linkend="opt-services.searx.settings"/>. In addition, the
603603- <literal>searx</literal> uid and gid reservations have been removed
604604- since they were not necessary: the service is now running with a
605605- dynamically allocated uid.
606606- </para>
607607- </listitem>
608608- <listitem>
609609- <para>
610610- The libinput module has been updated with the ability to configure mouse and touchpad settings separately.
611611- The options in <literal>services.xserver.libinput</literal> have been renamed to <literal>services.xserver.libinput.touchpad</literal>,
612612- while there is a new <literal>services.xserver.libinput.mouse</literal> for mouse related configuration.
613613- </para>
614614- <para>
615615- Since touchpad options no longer apply to all devices, you may want to replicate your touchpad configuration in
616616- mouse section.
617617- </para>
618618- </listitem>
619619- <listitem>
620620- <para>
621621- ALSA OSS emulation (<varname>sound.enableOSSEmulation</varname>) is now disabled by default.
622622- </para>
623623- </listitem>
624624- <listitem>
625625- <para>
626626- Thinkfan as been updated to <literal>1.2.x</literal>, which comes with a
627627- new YAML based configuration format. For this reason, several NixOS options
628628- of the thinkfan module have been changed to non-backward compatible types.
629629- In addition, a new <xref linkend="opt-services.thinkfan.settings"/> option has
630630- been added.
631631- </para>
632632- <para>
633633- Please read the <link xlink:href="https://github.com/vmatare/thinkfan#readme">
634634- thinkfan documentation</link> before updating.
635635- </para>
636636- </listitem>
637637- <listitem>
638638- <para>
639639- Adobe Flash Player support has been dropped from the tree. In particular,
640640- the following packages no longer support it:
641641- <itemizedlist>
642642- <listitem><simpara><package>chromium</package></simpara></listitem>
643643- <listitem><simpara><package>firefox</package></simpara></listitem>
644644- <listitem><simpara><package>qt48</package></simpara></listitem>
645645- <listitem><simpara><package>qt5.qtwebkit</package></simpara></listitem>
646646- </itemizedlist>
647647- Additionally, packages <package>flashplayer</package> and
648648- <package>hal-flash</package> were removed along with the
649649- <varname>services.flashpolicyd</varname> module.
650650- </para>
651651- </listitem>
652652- <listitem>
653653- <para>
654654- The <literal>security.rngd</literal> module has been removed.
655655- It was disabled by default in 20.09 as it was functionally redundant
656656- with krngd in the linux kernel. It is not necessary for any device that the kernel recognises
657657- as an hardware RNG, as it will automatically run the krngd task to periodically collect random
658658- data from the device and mix it into the kernel's RNG.
659659- </para>
660660- <para>
661661- The default SMTP port for GitLab has been changed to
662662- <literal>25</literal> from its previous default of
663663- <literal>465</literal>. If you depended on this default, you
664664- should now set the <xref linkend="opt-services.gitlab.smtp.port" />
665665- option.
666666- </para>
667667- </listitem>
668668- <listitem>
669669- <para>
670670- The default version of ImageMagick has been updated from 6 to 7.
671671- You can use <package>imagemagick6</package>,
672672- <package>imagemagick6_light</package>, and
673673- <package>imagemagick6Big</package> if you need the older version.
674674- </para>
675675- </listitem>
676676- <listitem>
677677- <para>
678678- <xref linkend="opt-services.xserver.videoDrivers" /> no longer uses the deprecated <literal>cirrus</literal> and <literal>vesa</literal> device dependent X drivers by default. It also enables both <literal>amdgpu</literal> and <literal>nouveau</literal> drivers by default now.
679679- </para>
680680- </listitem>
681681- <listitem>
682682- <para>
683683- The <literal>kindlegen</literal> 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 <link xlink:href="https://github.com/NixOS/nixpkgs/issues/96439">the discussion</link> for more info.
684684- </para>
685685- </listitem>
686686- <listitem>
687687- <para>
688688- The <package>apacheKafka</package> packages are now built with
689689- version-matched JREs. Versions 2.6 and above, the ones that recommend it,
690690- use jdk11, while versions below remain on jdk8. The NixOS service has
691691- been adjusted to start the service using the same version as the package,
692692- adjustable with the new
693693- <link linkend="opt-services.apache-kafka.jre">services.apache-kafka.jre</link>
694694- option. Furthermore, the default list of
695695- <link linkend="opt-services.apache-kafka.jvmOptions">services.apache-kafka.jvmOptions</link>
696696- have been removed. You should set your own according to the
697697- <link xlink:href="https://kafka.apache.org/documentation/#java">upstream documentation</link>
698698- for your Kafka version.
699699- </para>
700700- </listitem>
701701- <listitem>
702702- <para>
703703- The <package>kodi</package> package has been modified to allow concise addon management. Consider
704704- the following configuration from previous releases of NixOS to install <package>kodi</package>,
705705- including the <package>kodiPackages.inputstream-adaptive</package> and <package>kodiPackages.vfs-sftp</package>
706706- addons:
707707-708708- <programlisting>
709709-environment.systemPackages = [
710710- pkgs.kodi
711711-];
712712-713713-nixpkgs.config.kodi = {
714714- enableInputStreamAdaptive = true;
715715- enableVFSSFTP = true;
716716-};
717717- </programlisting>
718718-719719- All Kodi <literal>config</literal> flags have been removed, and as a result the above configuration
720720- should now be written as:
721721-722722- <programlisting>
723723-environment.systemPackages = [
724724- (pkgs.kodi.withPackages (p: with p; [
725725- inputstream-adaptive
726726- vfs-sftp
727727- ]))
728728-];
729729- </programlisting>
730730- </para>
731731- </listitem>
732732- <listitem>
733733- <para>
734734- <option>environment.defaultPackages</option> now includes the nano package.
735735- If <package>pkgs.nano</package> is not added to the list,
736736- make sure another editor is installed and the <literal>EDITOR</literal>
737737- environment variable is set to it.
738738- Environment variables can be set using <option>environment.variables</option>.
739739- </para>
740740- </listitem>
741741- <listitem>
742742- <para>
743743- <option>services.minio.dataDir</option> changed type to a list of paths, required for specifiyng multiple data directories for using with erasure coding.
744744- Currently, the service doesn't enforce nor checks the correct number of paths to correspond to minio requirements.
745745- </para>
746746- </listitem>
747747- <listitem>
748748- <para>
749749- All CUDA toolkit versions prior to CUDA 10 have been removed.
750750- </para>
751751- </listitem>
752752- <listitem>
753753- <para>
754754- The <package>kbdKeymaps</package> package was removed since dvp and neo
755755- are now included in <package>kbd</package>.
756756-757757- If you want to use the Programmer Dvorak Keyboard Layout, you have to use
758758- <literal>dvorak-programmer</literal> in <option>console.keyMap</option>
759759- now instead of <literal>dvp</literal>.
760760- In <option>services.xserver.xkbVariant</option> it's still <literal>dvp</literal>.
761761- </para>
762762- </listitem>
763763- <listitem>
764764- <para>
765765- The <package>babeld</package> service is now being run as an unprivileged user. To achieve that the module configures
766766- <literal>skip-kernel-setup true</literal> and takes care of setting forwarding and rp_filter sysctls by itself as well
767767- as for each interface in <varname>services.babeld.interfaces</varname>.
768768- </para>
769769- </listitem>
770770- <listitem>
771771- <para>
772772- The <option>services.zigbee2mqtt.config</option> option has been renamed to <option>services.zigbee2mqtt.settings</option> and
773773- now follows <link xlink:href="https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md">RFC 0042</link>.
774774- </para>
775775- </listitem>
776776- <listitem>
777777- <para>
778778- The <package>yadm</package> 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.
779779- </para>
780780- </listitem>
781781- <listitem>
782782- <para>
783783- Instead of determining <option>services.radicale.package</option>
784784- automatically based on <option>system.stateVersion</option>, the latest
785785- version is always used because old versions are not officially supported.
786786- </para>
787787- <para>
788788- Furthermore, Radicale's systemd unit was hardened which might break some
789789- deployments. In particular, a non-default
790790- <literal>filesystem_folder</literal> has to be added to
791791- <option>systemd.services.radicale.serviceConfig.ReadWritePaths</option> if
792792- the deprecated <option>services.radicale.config</option> is used.
793793- </para>
794794- </listitem>
795795- <listitem>
796796- <para>
797797- In the <option>security.acme</option> module, use of <literal>--reuse-key</literal>
798798- parameter for Lego has been removed. It was introduced for HKPK, but this security
799799- feature is now deprecated. It is a better security practice to rotate key pairs
800800- instead of always keeping the same. If you need to keep this parameter, you can add
801801- it back using <literal>extraLegoRenewFlags</literal> as an option for the
802802- appropriate certificate.
803803- </para>
804804- </listitem>
805805- </itemizedlist>
806806- </section>
807807-808808- <section xmlns="http://docbook.org/ns/docbook"
809809- xmlns:xlink="http://www.w3.org/1999/xlink"
810810- xmlns:xi="http://www.w3.org/2001/XInclude"
811811- version="5.0"
812812- xml:id="sec-release-21.05-notable-changes">
813813- <title>Other Notable Changes</title>
814814-815815- <itemizedlist>
816816- <listitem>
817817- <para>
818818- <literal>stdenv.lib</literal> has been deprecated and will break
819819- eval in 21.11. Please use <literal>pkgs.lib</literal> instead.
820820- See <link xlink:href="https://github.com/NixOS/nixpkgs/issues/108938">#108938</link>
821821- for details.
822822- </para>
823823- </listitem>
824824-825825- <listitem>
826826- <para>
827827- <link xlink:href="https://www.gnuradio.org/">GNURadio</link> has a
828828- <code>pkgs</code> attribute set, and there's a <code>gnuradio.callPackage</code>
829829- function that extends <code>pkgs</code> with a <code>mkDerivation</code>, and a
830830- <code>mkDerivationWith</code>, like Qt5. Now all <code>gnuradio.pkgs</code> are
831831- defined with <code>gnuradio.callPackage</code> and some packages that depend
832832- on gnuradio are defined with this as well.
833833- </para>
834834- </listitem>
835835- <listitem>
836836- <para>
837837- <link xlink:href="https://www.privoxy.org/">Privoxy</link> has been updated
838838- to version 3.0.32 (See <link xlink:href="https://lists.privoxy.org/pipermail/privoxy-announce/2021-February/000007.html">announcement</link>).
839839- Compared to the previous release, Privoxy has gained support for HTTPS
840840- inspection (still experimental), Brotli decompression, several new filters
841841- and lots of bug fixes, including security ones. In addition, the package
842842- is now built with compression and external filters support, which were
843843- previously disabled.
844844- </para>
845845- <para>
846846- Regarding the NixOS module, new options for HTTPS inspection have been added
847847- and <option>services.privoxy.extraConfig</option> has been replaced by the new
848848- <xref linkend="opt-services.privoxy.settings"/>
849849- (See <link xlink:href="https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md">RFC 0042</link>
850850- for the motivation).
851851- </para>
852852- </listitem>
853853- <listitem>
854854- <para>
855855- <link xlink:href="https://kodi.tv/">Kodi</link> has been updated to version 19.1 "Matrix". See
856856- the <link xlink:href="https://kodi.tv/article/kodi-19-0-matrix-release">announcement</link> for
857857- further details.
858858- </para>
859859- </listitem>
860860- <listitem>
861861- <para>
862862- The <option>services.packagekit.backend</option> option has been removed as
863863- it only supported a single setting which would always be the default.
864864- Instead new <link
865865- xlink:href="https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md">RFC
866866- 0042</link> compliant <xref linkend="opt-services.packagekit.settings"/>
867867- and <xref linkend="opt-services.packagekit.vendorSettings"/> options have
868868- been introduced.
869869- </para>
870870- </listitem>
871871- <listitem>
872872- <para>
873873- <link xlink:href="https://nginx.org">Nginx</link> has been updated to stable version 1.20.0.
874874- Now nginx uses the zlib-ng library by default.
875875- </para>
876876- </listitem>
877877- <listitem>
878878- <para>
879879- KDE Gear (formerly KDE Applications) is upgraded to 21.04, see its
880880- <link xlink:href="https://kde.org/announcements/gear/21.04/">release
881881- notes</link> for details.
882882- </para>
883883- <para>
884884- The <code>kdeApplications</code> package set is now <code>kdeGear</code>,
885885- in keeping with the new name. The old name remains for compatibility, but
886886- it is deprecated.
887887- </para>
888888- </listitem>
889889- <listitem>
890890- <para>
891891- <link xlink:href="https://libreswan.org/">Libreswan</link> has been updated
892892- to version 4.4. The package now includes example configurations and manual
893893- pages by default. The NixOS module has been changed to use the upstream
894894- systemd units and write the configuration in the <literal>/etc/ipsec.d/
895895- </literal> directory. In addition, two new options have been added to
896896- specify connection policies
897897- (<xref linkend="opt-services.libreswan.policies"/>)
898898- and disable send/receive redirects
899899- (<xref linkend="opt-services.libreswan.disableRedirects"/>).
900900- </para>
901901- </listitem>
902902-903903- <listitem>
904904- <para>
905905- The Mailman NixOS module (<literal>services.mailman</literal>) has a new
906906- option <xref linkend="opt-services.mailman.enablePostfix" />, defaulting
907907- to true, that controls integration with Postfix.
908908- </para>
909909- <para>
910910- If this option is disabled, default MTA config becomes not set and you
911911- should set the options in <literal>services.mailman.settings.mta</literal>
912912- according to the desired configuration as described in
913913- <link xlink:href="https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html">Mailman documentation</link>.
914914- </para>
915915- </listitem>
916916- <listitem>
917917- <para>
918918- The default-version of <literal>nextcloud</literal> is <package>nextcloud21</package>.
919919- Please note that it's <emphasis>not</emphasis> possible to upgrade <literal>nextcloud</literal>
920920- across multiple major versions! This means that it's e.g. not possible to upgrade
921921- from <package>nextcloud18</package> to <package>nextcloud20</package> in a single deploy and
922922- most <literal>20.09</literal> users will have to upgrade to <package>nextcloud20</package>
923923- first.
924924- </para>
925925- <para>
926926- The package can be manually upgraded by setting <xref linkend="opt-services.nextcloud.package" />
927927- to <package>nextcloud21</package>.
928928- </para>
929929- </listitem>
930930- <listitem>
931931- <para>
932932- The setting <xref linkend="opt-services.redis.bind" /> defaults to <literal>127.0.0.1</literal> now, making Redis listen on the loopback interface only, and not all public network interfaces.
933933- </para>
934934- </listitem>
935935- <listitem>
936936- <para>
937937- NixOS now emits a deprecation warning if systemd's <literal>StartLimitInterval</literal> setting is used in a <literal>serviceConfig</literal> section instead of in a <literal>unitConfig</literal>; 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 <link xlink:href="https://github.com/NixOS/nixpkgs/issues/45785">#45785</link> for details.
938938- </para>
939939- <para>
940940- All services should use <xref linkend="opt-systemd.services._name_.startLimitIntervalSec" /> or <literal>StartLimitIntervalSec</literal> in <xref linkend="opt-systemd.services._name_.unitConfig" /> instead.
941941- </para>
942942- </listitem>
943943- <listitem>
944944- <para>
945945- The <literal>mediatomb</literal> service
946946- declares new options. It also adapts existing options so the
947947- configuration generation is now lazy. The existing option
948948- <literal>customCfg</literal> (defaults to false), when enabled, stops
949949- the service configuration generation completely. It then expects the
950950- users to provide their own correct configuration at the right location
951951- (whereas the configuration was generated and not used at all before).
952952- The new option <literal>transcodingOption</literal> (defaults to no)
953953- allows a generated configuration. It makes the mediatomb service pulls
954954- the necessary runtime dependencies in the nix store (whereas it was
955955- generated with hardcoded values before). The new option
956956- <literal>mediaDirectories</literal> allows the users to declare autoscan
957957- media directories from their nixos configuration:
958958- <programlisting>
959959- services.mediatomb.mediaDirectories = [
960960- { path = "/var/lib/mediatomb/pictures"; recursive = false; hidden-files = false; }
961961- { path = "/var/lib/mediatomb/audio"; recursive = true; hidden-files = false; }
962962- ];
963963- </programlisting>
964964- </para>
965965- </listitem>
966966- <listitem>
967967- <para>
968968- The Unbound DNS resolver service (<literal>services.unbound</literal>) has been refactored to allow reloading, control sockets and to fix startup ordering issues.
969969- </para>
970970-971971- <para>
972972- It is now possible to enable a local UNIX control socket for unbound by setting the <xref linkend="opt-services.unbound.localControlSocketPath" />
973973- option.
974974- </para>
975975-976976- <para>
977977- Previously we just applied a very minimal set of restrictions and
978978- trusted unbound to properly drop root privs and capabilities.
979979- </para>
980980-981981- <para>
982982- As of this we are (for the most part) just using the upstream
983983- example unit file for unbound. The main difference is that we start
984984- unbound as <literal>unbound</literal> user with the required capabilities instead of
985985- letting unbound do the chroot & uid/gid changes.
986986- </para>
987987-988988- <para>
989989- The upstream unit configuration this is based on is a lot stricter with
990990- all kinds of permissions then our previous variant. It also came with
991991- the default of having the <literal>Type</literal> set to <literal>notify</literal>, therefore we are now also
992992- using the <literal>unbound-with-systemd</literal> package here. Unbound will start up,
993993- read the configuration files and start listening on the configured ports
994994- before systemd will declare the unit <literal>active (running)</literal>.
995995- This will likely help with startup order and the occasional race condition during system
996996- activation where the DNS service is started but not yet ready to answer
997997- queries. Services depending on <literal>nss-lookup.target</literal> or <literal>unbound.service</literal>
998998- are now be able to use unbound when those targets have been reached.
999999- </para>
10001000-10011001- <para>
10021002- Additionally to the much stricter runtime environment the
10031003- <literal>/dev/urandom</literal> mount lines we previously had in the code (that
10041004- randomly failed during the stop-phase) have been removed as systemd will take care of those for us.
10051005- </para>
10061006-10071007- <para>
10081008- The <literal>preStart</literal> script is now only required if we enabled the trust
10091009- anchor updates (which are still enabled by default).
10101010- </para>
10111011-10121012- <para>
10131013- Another benefit of the refactoring is that we can now issue reloads via
10141014- either <literal>pkill -HUP unbound</literal> and <literal>systemctl reload unbound</literal> to reload the
10151015- running configuration without taking the daemon offline. A prerequisite
10161016- of this was that unbound configuration is available on a well known path
10171017- on the file system. We are using the path <literal>/etc/unbound/unbound.conf</literal> as that is the
10181018- default in the CLI tooling which in turn enables us to use
10191019- <literal>unbound-control</literal> without passing a custom configuration location.
10201020- </para>
10211021-10221022- <para>
10231023- The module has also been reworked to be <link
10241024- xlink:href="https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md">RFC
10251025- 0042</link> compliant. As such,
10261026- <option>sevices.unbound.extraConfig</option> has been removed and replaced
10271027- by <xref linkend="opt-services.unbound.settings"/>. <option>services.unbound.interfaces</option>
10281028- has been renamed to <option>services.unbound.settings.server.interface</option>.
10291029- </para>
10301030-10311031- <para>
10321032- <option>services.unbound.forwardAddresses</option> and
10331033- <option>services.unbound.allowedAccess</option> have also been changed to
10341034- use the new settings interface. You can follow the instructions when
10351035- executing <literal>nixos-rebuild</literal> to upgrade your configuration to
10361036- use the new interface.
10371037- </para>
10381038- </listitem>
10391039- <listitem>
10401040- <para>
10411041- The <literal>services.dnscrypt-proxy2</literal> module now takes the upstream's example configuration and updates it with the user's settings.
10421042-10431043- An option has been added to restore the old behaviour if you prefer to declare the configuration from scratch.
10441044- </para>
10451045- </listitem>
10461046- <listitem>
10471047- <para>
10481048- NixOS now defaults to the unified cgroup hierarchy (cgroupsv2).
10491049- See the <link xlink:href="https://www.redhat.com/sysadmin/fedora-31-control-group-v2">Fedora Article for 31</link>
10501050- for details on why this is desirable, and how it impacts containers.
10511051- </para>
10521052- <para>
10531053- If you want to run containers with a runtime that does not yet support cgroupsv2,
10541054- you can switch back to the old behaviour by setting
10551055- <xref linkend="opt-systemd.enableUnifiedCgroupHierarchy"/> = <literal>false</literal>;
10561056- and rebooting.
10571057- </para>
10581058- </listitem>
10591059- <listitem>
10601060- <para>
10611061- PulseAudio was upgraded to 14.0, with changes to the handling of default sinks.
10621062- See its <link xlink:href="https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/14.0/">release notes</link>.
10631063- </para>
10641064- </listitem>
10651065- <listitem>
10661066- <para>
10671067- GNOME users may wish to delete their <literal>~/.config/pulse</literal> due to the changes to stream routing
10681068- logic. See <link xlink:href="https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/832">PulseAudio bug 832</link>
10691069- for more information.
10701070- </para>
10711071- </listitem>
10721072- <listitem>
10731073- <para>
10741074- The <package>zookeeper</package> package does not provide
10751075- <literal>zooInspector.sh</literal> anymore, as that "contrib" has
10761076- been dropped from upstream releases.
10771077- </para>
10781078- </listitem>
10791079- <listitem>
10801080- <para>
10811081- In the ACME module, the data used to build the hash for the account
10821082- directory has changed to accomodate new features to reduce account
10831083- rate limit issues. This will trigger new account creation on the first
10841084- rebuild following this update. No issues are expected to arise from this,
10851085- thanks to the new account creation handling.
10861086- </para>
10871087- </listitem>
10881088- <listitem>
10891089- <para>
10901090- <xref linkend="opt-users.users._name_.createHome" /> now always ensures home directory permissions to be <literal>0700</literal>.
10911091- Permissions had previously been ignored for already existing home directories, possibly leaving them readable by others.
10921092- The option's description was incorrect regarding ownership management and has been simplified greatly.
10931093- </para>
10941094- </listitem>
10951095- <listitem>
10961096- <para>
10971097- When defining a new user, one of <xref linkend="opt-users.users._name_.isNormalUser" /> and <xref linkend="opt-users.users._name_.isSystemUser" /> is now required.
10981098- 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.
10991099- Note that users defined with an explicit UID below 500 are exempted from this check, as <xref linkend="opt-users.users._name_.isSystemUser" /> has no effect for those.
11001100- </para>
11011101- </listitem>
11021102- <listitem>
11031103- <para>
11041104- The <literal>security.apparmor</literal> module,
11051105- for the <link xlink:href="https://gitlab.com/apparmor/apparmor/-/wikis/Documentation">AppArmor</link>
11061106- Mandatory Access Control system,
11071107- has been substantialy improved along with related tools,
11081108- so that module maintainers can now more easily write AppArmor profiles for NixOS.
11091109- The most notable change on the user-side is the new option <xref linkend="opt-security.apparmor.policies"/>,
11101110- replacing the previous <literal>profiles</literal> option
11111111- to provide a way to disable a profile
11121112- and to select whether to confine in enforce mode (default)
11131113- or in complain mode (see <literal>journalctl -b --grep apparmor</literal>).
11141114- Security-minded users may also want to enable <xref linkend="opt-security.apparmor.killUnconfinedConfinables"/>,
11151115- at the cost of having some of their processes killed
11161116- when updating to a NixOS version introducing new AppArmor profiles.
11171117- </para>
11181118- </listitem>
11191119- <listitem>
11201120- <para>
11211121- The GNOME desktop manager once again installs <package>gnome.epiphany</package> by default.
11221122- </para>
11231123- </listitem>
11241124- <listitem>
11251125- <para>
11261126- NixOS now generates empty <literal>/etc/netgroup</literal>.
11271127- <literal>/etc/netgroup</literal> defines network-wide groups and may affect to setups using NIS.
11281128- </para>
11291129- </listitem>
11301130- <listitem>
11311131- <para>
11321132- Platforms, like <varname>stdenv.hostPlatform</varname>, no longer have a <varname>platform</varname> attribute.
11331133- It has been (mostly) flattened away:
11341134- </para>
11351135- <itemizedlist>
11361136- <listitem><para><varname>platform.gcc</varname> is now <varname>gcc</varname></para></listitem>
11371137- <listitem><para><literal>platform.kernel*</literal> is now <literal>linux-kernel.*</literal></para></listitem>
11381138- </itemizedlist>
11391139- <para>
11401140- Additionally, <varname>platform.kernelArch</varname> moved to the top level as <varname>linuxArch</varname> to match the other <literal>*Arch</literal> variables.
11411141- </para>
11421142- <para>
11431143- The <varname>platform</varname> grouping of these things never meant anything, and was just a historial/implementation artifact that was overdue removal.
11441144- </para>
11451145- </listitem>
11461146- <listitem>
11471147- <para>
11481148- <varname>services.restic</varname> now uses a dedicated cache directory for every backup defined in <varname>services.restic.backups</varname>. The old global cache directory, <literal>/root/.cache/restic</literal>, is now unused and can be removed to free up disk space.
11491149- </para>
11501150- </listitem>
11511151- <listitem>
11521152- <para>
11531153- <literal>isync</literal>: The <literal>isync</literal> compatibility wrapper was removed and the Master/Slave
11541154- terminology has been deprecated and should be replaced with Far/Near in the configuration file.
11551155- </para>
11561156- </listitem>
11571157- <listitem>
11581158- <para>
11591159- The nix-gc service now accepts randomizedDelaySec (default: 0) and persistent (default: true) parameters.
11601160- By default nix-gc will now run immediately if it would have been triggered at least
11611161- once during the time when the timer was inactive.
11621162- </para>
11631163- </listitem>
11641164- <listitem>
11651165- <para>
11661166- The <literal>rustPlatform.buildRustPackage</literal> function is split into several hooks:
11671167- <package>cargoSetupHook</package> to set up vendoring for Cargo-based projects,
11681168- <package>cargoBuildHook</package> to build a project using Cargo,
11691169- <package>cargoInstallHook</package> to install a project using Cargo, and
11701170- <package>cargoCheckHook</package> to run tests in Cargo-based projects. With this change,
11711171- mixed-language projects can use the relevant hooks within builders other than
11721172- <literal>buildRustPackage</literal>. However, these changes also required several API changes to
11731173- <literal>buildRustPackage</literal> itself:
11741174-11751175- <itemizedlist>
11761176- <listitem>
11771177- <para>
11781178- The <literal>target</literal> argument was removed. Instead, <literal>buildRustPackage</literal>
11791179- will always use the same target as the C/C++ compiler that is used.
11801180- </para>
11811181- </listitem>
11821182- <listitem>
11831183- <para>
11841184- The <literal>cargoParallelTestThreads</literal> argument was removed. Parallel tests are
11851185- now disabled through <literal>dontUseCargoParallelTests</literal>.
11861186- </para>
11871187- </listitem>
11881188- </itemizedlist>
11891189- </para>
11901190- </listitem>
11911191- <listitem>
11921192- <para>
11931193- The <literal>rustPlatform.maturinBuildHook</literal> hook was added. This hook can be used
11941194- with <literal>buildPythonPackage</literal> to build Python packages that are written in Rust
11951195- and use Maturin as their build tool.
11961196- </para>
11971197- </listitem>
11981198- <listitem>
11991199- <para>
12001200- Kubernetes has <link xlink:href="https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/">deprecated docker</link> as container runtime.
12011201- As a consequence, the Kubernetes module now has support for configuration of custom remote container runtimes and enables containerd by default.
12021202- Note that containerd is more strict regarding container image OCI-compliance.
12031203- As an example, images with CMD or ENTRYPOINT defined as strings (not lists) will fail on containerd, while working fine on docker.
12041204- Please test your setup and container images with containerd prior to upgrading.
12051205- </para>
12061206- </listitem>
12071207- <listitem>
12081208- <para>
12091209- The GitLab module now has support for automatic backups. A
12101210- schedule can be set with the
12111211- <link linkend="opt-services.gitlab.backup.startAt">services.gitlab.backup.startAt</link>
12121212- option.
12131213- </para>
12141214- </listitem>
12151215- <listitem>
12161216- <para>
12171217- Prior to this release, systemd would also read system units from an undocumented <literal>/etc/systemd-mutable/system</literal> path.
12181218- This path has been dropped from the defaults. That path (or others) can be re-enabled by adding it to the
12191219- <link linkend="opt-boot.extraSystemdUnitPaths">boot.extraSystemdUnitPaths</link> list.
12201220- </para>
12211221- </listitem>
12221222- <listitem>
12231223- <para>
12241224- PostgreSQL 9.5 is scheduled EOL during the 21.05 life cycle and has been removed.
12251225- </para>
12261226- </listitem>
12271227- <listitem>
12281228- <para>
12291229- <link xlink:href="https://www.xfce.org/">Xfce4</link> relies on
12301230- GIO/GVfs for userspace virtual filesystem access in applications
12311231- like <link xlink:href="https://docs.xfce.org/xfce/thunar/">thunar</link> and
12321232- <link xlink:href="https://docs.xfce.org/apps/gigolo/">gigolo</link>.
12331233- For that to work, the gvfs nixos service is enabled by default,
12341234- and it can be configured with the specific package that provides
12351235- GVfs. Until now Xfce4 was setting it to use a lighter version of
12361236- GVfs (without support for samba). To avoid conflicts with other
12371237- desktop environments this setting has been dropped. Users that
12381238- still want it should add the following to their system
12391239- configuration:
12401240- <programlisting>
12411241-<xref linkend="opt-services.gvfs.package" /> = pkgs.gvfs.override { samba = null; };
12421242- </programlisting>
12431243- </para>
12441244- </listitem>
12451245- <listitem>
12461246- <para>
12471247- The newly enabled <literal>systemd-pstore.service</literal> now automatically evacuates crashdumps and panic logs from the persistent storage to <literal>/var/lib/systemd/pstore</literal>.
12481248- This prevents NVRAM from filling up, which ensures the latest diagnostic data is always stored and alleviates problems with writing new boot configurations.
12491249- </para>
12501250- </listitem>
12511251- <listitem>
12521252- <para>
12531253- Nixpkgs now contains <link xlink:href="https://github.com/NixOS/nixpkgs/pull/118232">automatically packaged GNOME Shell extensions</link> from the <link xlink:href="https://extensions.gnome.org/">GNOME Extensions</link> portal. You can find them, filed by their UUID, under <literal>gnome38Extensions</literal> attribute for GNOME 3.38 and under <literal>gnome40Extensions</literal> for GNOME 40. Finally, the <literal>gnomeExtensions</literal> 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.
12541254- </para>
12551255- </listitem>
12561256- <listitem>
12571257- <para>
12581258- 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.
12591259- We also dropped <literal>lfe_1_2</literal> as it could not build with R21+.
12601260- Moving forward, we expect to only support 3 yearly releases of OTP.
12611261- </para>
12621262- </listitem>
12631263-12641264- </itemizedlist>
12651265- </section>
12661266-</section>
+2
nixos/doc/manual/release-notes/rl-2111.section.md
···8383- The setting [`services.openssh.logLevel`](options.html#opt-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.
84848585 However, if [`services.fail2ban.enable`](options.html#opt-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.
8686+8787+- 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.
+1-2
nixos/modules/programs/sway.nix
···9191 type = with types; listOf package;
9292 default = with pkgs; [
9393 swaylock swayidle alacritty dmenu
9494- rxvt-unicode # For backward compatibility (old default terminal)
9594 ];
9695 defaultText = literalExample ''
9797- with pkgs; [ swaylock swayidle rxvt-unicode alacritty dmenu ];
9696+ with pkgs; [ swaylock swayidle alacritty dmenu ];
9897 '';
9998 example = literalExample ''
10099 with pkgs; [
···3939, zlib
4040}:
4141let
4242- version = "2012";
4242+ version = "2103";
43434444 sysArch =
4545 if stdenv.hostPlatform.system == "x86_64-linux" then "x64"
4646 else throw "Unsupported system: ${stdenv.hostPlatform.system}";
4747- # The downloaded archive also contains i386 and ARM binaries, but these have not been tested.
4747+ # The downloaded archive also contains ARM binaries, but these have not been tested.
48484949 vmwareHorizonClientFiles = stdenv.mkDerivation {
5050 name = "vmwareHorizonClientFiles";
5151 inherit version;
5252 src = fetchurl {
5353- url = "https://download3.vmware.com/software/view/viewclients/CART21FQ4/VMware-Horizon-Client-Linux-2012-8.1.0-17349998.tar.gz";
5454- sha256 = "0afda1f3116e75a4e7f89990d8ee60ccea5f3bb8a2360652162fa11c795724ce";
5353+ url = "https://download3.vmware.com/software/view/viewclients/CART22FQ1/VMware-Horizon-Client-Linux-2103-8.2.0-17742757.tar.gz";
5454+ sha256 = "62f95bb802b058a98f5ee6c2296b89bd7e15884a24dc8a8ba7ce89de7e0798e4";
5555 };
5656 nativeBuildInputs = [ makeWrapper ];
5757 installPhase = ''
···3636 blockdiagcontrib-cisco = throw "blockdiagcontrib-cisco is not compatible with blockdiag 2.0.0 and has been removed."; # Added 2020-11-29
3737 bugseverywhere = throw "bugseverywhere has been removed: Abandoned by upstream."; # Added 2019-11-27
3838 detox = throw "detox is no longer maintained, and was broken since may 2019"; # added 2020-07-04
3939+ dns = dnspython; # Alias for compatibility, 2017-12-10
3940 faulthandler = throw "faulthandler is built into ${python.executable}";
4041 gitdb2 = throw "gitdb2 has been deprecated, use gitdb instead."; # added 2020-03-14
4142 glances = throw "glances has moved to pkgs.glances"; # added 2020-20-28