…usId

Specifically for NVIDIA so that only the device section would be created

Needed for PRIME render offload specifically

This makes predictable interfaces names available as soon as possible
with udev by adding the default network link units to initrd which are read
by udev. Also adds some udev rules that are needed but which would normally
loaded from the udev store path which is not included in the initrd.

Depending on the network management backend being used, if the interface
configuration in stage 1 is not cleared, there might still be some old
addresses or routes from stage 1 present in stage 2 after network
configuration has finished.

This apparently has features that the version from Arch's
mkinitcpio-nfs-utils does not have. Fixes #75314.

As outlined in #71447, postCommands should always be run if networking
in initrd is enabled. regardless if the configuration actually
succeeded.

Release notes: https://www.postgresql.org/docs/9.5/release-9-5-21.html

Release notes: https://www.postgresql.org/docs/9.6/release-9-6-17.html

Release notes: https://www.postgresql.org/docs/10/release-10-12.html

Release notes: https://www.postgresql.org/docs/11/release-11-7.html

Release notes: https://www.postgresql.org/docs/current/release-12-2.html

Recent updates to the generic builder have caused haskellPackages.lmdb-simple to
fail to build on Darwin, since it cannot see the lmdb C dynamic library included
by its dependent haskellPackages.lmdb.

The C dynamic library has suffix `.so` not `.dylib`, so this fix allows for
that.

Closes #80190, but that issue may identify a preferable solution.

haskell generic-builder: fix Darwin regression for lmdb

postgresql: 9.5.20 -> 9.5.21, 9.6.16 -> 9.6.17, 10.11 -> 10.12, 11.6 -> 11.7, 12.1 -> 12.2

> Include multiple versions of certain functions in the library,
> and select the ones to use at run-time, depending on available
> processor features. Supported for ARM and x86_64.

The current version seems to accelerate AES and SHA families.

Size increase on x86_64 is <10k in our case.

It can make quite some performance difference; I tried
$ time ./result-dev/bin/nettle-hash -a sha256 /some/file/around/2G
And the total CPU time went down from 8.5s to 2s (single thread).
Now it matches the time of openssl
$ time openssl sha256 /some/file/around/2G
Of course, in real life it will be much harder to notice a difference...

Platforms without support for this (e.g. i686) seem to still build fine,
and ARMv7 cross-build also succeeds for me, so hopefully all is OK.

This reverts commit 2d6f0cb.

postgresql versions < 9.5 have been removed from nixpkgs.

https://lists.exim.org/lurker/message/20200212.174850.6edd8277.en.html

nixpkgs-review: 2.1.1 -> 2.2.0

Backport fix of QT5_MAKE_OUTPUT_FILE CMake macro which causes FreeCAD
build failure when building with qt-5.12.7.

https://bugreports.qt.io/browse/QTBUG-81715

Execute in subshell so that the cwd returns back
to the original directory. This is important as
it enables pythonImportsCheck to work with checkPhase

Perl on darwin (and any other sane platform) has a pretty good threading
support, enable it.

As it turns out, we were building non-multithreaded perl on all systems,
since glibc was not part of the stdenv anymore:

    nix-repl> pkgs = import <nixpkgs> {}

    nix-repl> pkgs.stdenv ? glibc
    false

meaning that the comments were incorrect. Thus, clear up the confusion
and remove the misleading comments, while enabling multithreading by
default. The builds will fail on unsupported platforms, and in this case
the only place is the bootstrap, where we already force
non-multithreaded perl.

As a consequence of the above, this change will cause the full rebuild
of stdenv on all platforms, including linux.

Add myself to maintainers and change meta.platforms to platforms.linux
due to build failures on Darwin.

gptfdisk: 1.0.4 -> 1.0.5

Synching with the riot-web update (commit da45483).