* mark as broken on darwin
```
these derivations will be built:
/nix/store/f29hm2393h56xh4slil62zlb72j5k0nq-wtf-0.32.0.drv
building '/nix/store/f29hm2393h56xh4slil62zlb72j5k0nq-wtf-0.32.0.drv'...
unpacking sources
unpacking source archive /nix/store/7xd1c92n7i0pcpxb71qgfz7d0hasbcrf-source
source root is source
patching sources
configuring
building
Building subPackage ./.
modules/azuredevops/widget.go:7:2: cannot find package "." in:
/private/var/folders/hk/77b9kbln51v8hgc1c6j767k00000gn/T/nix-build-wtf-0.32.0.drv-0/source/vendor/github.com/microsoft/azure-devops-go-api/azuredevops
modules/azuredevops/client.go:7:2: cannot find package "." in:
/private/var/folders/hk/77b9kbln51v8hgc1c6j767k00000gn/T/nix-build-wtf-0.32.0.drv-0/source/vendor/github.com/microsoft/azure-devops-go-api/azuredevops/build
builder for '/nix/store/f29hm2393h56xh4slil62zlb72j5k0nq-wtf-0.32.0.drv' failed with exit code 1
error: build of '/nix/store/f29hm2393h56xh4slil62zlb72j5k0nq-wtf-0.32.0.drv' failed
```
Secrets are injected from the environment into the rendered
configuration before each startup using envsubst.
The test now makes use of this feature for the server password.
When using the ACME DNS-01 challenge, there is a possibility of a
failure to resolve the challenge if the record is not propagated
fast enough. To circumvent this generic DNS problem, this adds
a setting to explicitly tell the ACME provider to use a certain DNS
resolver to lookup the challenge.
Signed-off-by: Jeroen Simonetti <jeroen@simonetti.nl>
This reverts commit fb6d63f3fd.
I really hope this finally fixes #99236: evaluation on Hydra.
This time I really did check basically the same commit on Hydra:
https://hydra.nixos.org/eval/1618011
Right now I don't have energy to find what exactly is wrong in the
commit, and it doesn't seem important in comparison to nixos-unstable
channel being stuck on a commit over one week old.
There has been no new release since 2.3.2 for some years now (around 2016) [1]
The most recent master branch for the amule project includes a commit [2] which
fixes compilation breakage with the next libupnp version [3].
So this bumps the amule version to the latest commit of that repository.
[1] https://github.com/amule-project/amule/issues/219
[2] 8784480c79
[3] #93048
This ensures that we aren't applying any of the experiemental pipewire
patches when the dependencies aren't enabled. As of now pipewire only
works with wayland and webrtc. If either of them are not activated we
can't build with pipewireSupport and we should not.
This should hopefully solve races with DNS servers (such as unbound)
during the activation of a new generation. Previously unbound could
still be unavailable and thus the acme script would fail.
