(cherry picked from commit b2748c6e)

enable aarch64-darwin in release.nix

[2.3] Backport libatomic fixes

This fixes both the SunOS/Solaris check, and the libatomic check, which
reference $LIBS, which has not been used since automake was stripped
out of the code.

(cherry picked from commit 196b77b6)

Taken from Mesa configure script:

https://github.com/mesa3d/mesa/blob/17.2/configure.ac#L405-L427
(cherry picked from commit b1c34152)

Fixes #3113

(cherry picked from commit 74b4737d)

[2.3] Pass --static flag to pkg-config when necessary

(cherry picked from commit 3e85c57a)

[2.3] backport contact info changes (including getting rid of Freenode)

Introduced in master in eab14a64.

(cherry picked from commit 822e338e)

When adding a path to the local store (via `LocalStore::addToStore`),
ensure that the `ca` field of the provided `ValidPathInfo` does indeed
correspond to the content of the path.
Otherwise any untrusted user (or any binary cache) can add arbitrary
content-addressed paths to the store (as content-addressed paths don’t
need a signature).

Fix pure build of 2.3

Fix iterating over $NIX_PROFILES in Zsh (backport to 2.3)

NIX_PROFILES is space separated list of directories, and passing it into
for as is is considered to be 1-element list with the whole string. With
shwordsplit option Zsh emulates other shells in this regard ans
implicitely splits unquoted strings into words.

Fixes #4167.

(cherry picked from commit 0431cf6d)
Signed-off-by: Domen Kožar <domen@dev.si>

backport #4411

Backport #4601

When starting a nix-shell with `-i` it was previously possible for it to
silently fail in the scenario where the specified interpreter didn't
exist. This happened due to the `exec` call masking the issue.

With this change we enable `execfail`, which causes the script using
`nix-shell` as interpreter to correctly exit with code 127.

Fixes: #4598
(cherry picked from commit 6e849e3b)

[backport 2.3] Fix #4469

While the progress dots during the copying of the store work fine on a
normal terminal, those look pretty off if the script is run inside a
provisioning script of e.g. `vagrant` or `packer` where `stderr` and
`stdout` are captured:

    default: .
    default: ..
    default: .
    default: .
    default: .

To work around this, the script checks with `-t 0` if it's
running on an actual terminal and doesn't show the progress if that's not
the case.

(cherry picked from commit d9367a2d)

GitHub now omits the etag, but 304 implies it matches the one we
provided. Just use that one to avoid having an etag-less resource.

Fixes #4469

(cherry picked from commit a7668246)

Backport compatibility with newer AWS SDKs to 2.3 (#4316)

Tested against AWS SDK 1.8.99. Fixes #3201.

(cherry picked from commit e20a3ec7)

Backport issue 3964 substitution loop

This reverts commit e90530e4.

It appears that this backported test relies on new functionality.

The error is:

    + nix copy --to file:///build/nix-test/binary-cache /build/nix-test/store/dckdy2xp7sn8qvyx8axxjq7clnxddri1-multi-output
    warning: you don't have Internet access; disabling some network-dependent features
    error: uploading to 'file:///build/nix-test/binary-cache/nar/0hpfhrig9h6fvbjmiwsb7zkaxr19vr2w048y4xb3nrs36bagf92n.nar.xz' is not supported

(cherry picked from commit ea8d3202)

(cherry picked from commit bd9eb5c7)

Allow HTTP binary cache to request absolute uris

Backport json unicode escaping to 2.3

As fromTOML supports \u and \U escapes, bring fromJSON on par. As JSON defaults
to UTF-8 encoding (every JSON parser must support UTF-8), this change parses the
`\u hex hex hex hex` sequence (\u followed by 4 hexadecimal digits) into an
UTF-8 representation.

Add a test to verify correct parsing, using all escape sequences from json.org.