Accidentally broken by 7e5c79a2

We need to support it for the “old” fetch* functions for backwards
compatibility, but we don’t need it for fetchTree (as it’s a new
function).
Given that changing the `name` messes-up the content hashing, we can
just forbid passing a custom `name` argument to it

Fix #3388

Prefer to throw specific errors

Respect TERM=dumb more consistently

upload-release.pl: add aarch64-darwin

Signed-off-by: Pamplemousse <xav.maso@gmail.com>

develop: Discard the input{Overrides,Updates} when getting bash

Restrict jobs built on hydra

This should resolve the failing build.

See https://github.com/NixOS/nixpkgs/pull/128674 for a better fix.

This is broken on aarch64-linux / x86_64-darwin, so might as well just disable it for now.

Forward the experimental features to the nix repl subprocesses

Pass the current experimental features using `NIX_CONFIG` to the various
Nix subprocesses that `nix repl` invokes.

This is quite a hack, but having `nix repl` call Nix with a subprocess
is a hack already, so I guess that’s fine.

Keep the `isFlake` attribute for overriden inputs

When overriding an input that isn’t a flake, mark the override as also not
being a flake.

Fix #3774

Fix gc crash

Add armv6l-linux & armv7l-linux as cross jobs

`nix develop` is getting bash from an (assumed existing) `nixpkgs`
flake. However, when doing so, it reuses the `lockFlags` passed to the
current flake, including the `--input-overrides` and `--input-update`
which generally don’t make sense anymore at that point (and trigger a
warning because of that)

Clear these overrides before getting the nixpkgs flake to get rid of the
warning.

flake.lock: Update

Flake input changes:

* Updated 'nixpkgs': 'github:NixOS/nixpkgs/bb8a5e54845012ed1375ffd5f317d2fdf434b20e' -> 'github:NixOS/nixpkgs/f77036342e2b690c61c97202bf48f2ce13acc022'

man: fix formatting of nix3-profile-remove

Eventually delete the CA paths lock files

Make the CA tests actually test something

Fixes

  error: cannot create symlink '/home/eelco/Dev/nix/tests/result'; already exists

Fixes the problem where a stack pointer outside the original
thread causes the collector to crash.

It could be made more accurate by recording the stack pointer
every time we switch to a coroutine. We can use this information
to update our own coroutine stacks like normal data. When the
stack pointer is on a thread, we can add a field to GC_thread
"fallback_sp" to be used when the thread sp is outside the original
thread range.

Mark the lockfiles as having to eventually be deleted so that they don’t
stay laying around in the store at the end of the build

Fix #4936

Make CA derivations compatible with recursive Nix