Build is currently failing:
```
/nix/store/za0pnll14dv61b124n6xxnjapd150lcr-go-1.19.4/share/go/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
Undefined symbols for architecture x86_64:
"_pam_start_confdir", referenced from:
__cgo_897673d6bfaf_Cfunc_pam_start_confdir in 000032.o
_check_pam_start_confdir in 000033.o
(maybe you meant: _check_pam_start_confdir, __cgo_897673d6bfaf_Cfunc_check_pam_start_confdir , __cgo_897673d6bfaf_Cfunc_pam_start_confdir )
ld: symbol(s) not found for architecture x86_64
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
error: builder for '/nix/store/zqr2xx5a66km81m8av714sm45gy3ym0g-gitea-1.18.0.drv' failed with exit code 1;
```
This commit causes Hydra to build `nixStatic` on non-NixOS platforms
for which nixStatic is known to build correctly.
Providing Hydra builds of `nixStatic` on these platforms allows users
to bootstrap their local nixpkgs system without either having to:
a. Trust binaries that came from a source other than Hydra or
b. Fight with their host distribution to satisfy all of nix's large
set of build dependencies (this is not easy!)
Currently there are two platforms in this set: mips64el-linux-gnuabi64
and powerpc64le-linux-gnu.
This updates the `true-name` package to include changes up to version
0.1.0.4, as well as compilation failures when building with
template-haskell version 2.16 and higher.
There's nothing about edk2 specific to the host OS, and it builds fine
with e.g. a NetBSD toolchain, so we should only restrict
meta.platforms by architecture, not by OS.
The documentation for `meta.sourceProvenance` in
`doc/stdenv/meta.chapter.md` says: "the `meta.sourceProvenance`
attribute should be a list containing one or more value..."
Let's update check-meta.nix to require that `meta.sourceProvenance` is
a list, as the documentation says, rather than a single element.
Adding two extra keystrokes `[` and `]` when filling out this field is
an insignificant burden for package authors, and being able to assume
that the `meta.sourceProvenance` field is always a list greatly
simplifies any code that acts on the value of this field.
Since `meta.sourceProvenance` was just merged a few hours ago now is
the easiest time to fix this: nobody is using the feature yet.
Maximilian Bosch
gador