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
openfortivpn would look in the nix store for config files, which
obviously doesn't work, so make it go to /etc/openfortivpn instead so
we *can* configure it system-wide.
Also add systemd units on Linux.
Related:
- 9fc5e7e473
- 593e11fd94
- 508ae42a0f
Since the last time I ran this script, the Repology API changed, so I had to
adapt the script used in the previous PR. The new API should be more robust, so
overall this is a positive (no more grepping the error messages for our relevant
data but just a nice json structure).
Here's the new script I used:
```sh
curl https://repology.org/api/v1/repository/nix_unstable/problems \
| jq -r '.[] | select(.type == "homepage_permanent_https_redirect") | .data | "s@\(.url)@\(.target)@"' \
| sort | uniq | tee script.sed
find -name '*.nix' | xargs -P4 -- sed -f script.sed -i
```
I will also add this script to `maintainers/scripts`.
shadowfox-updater compares the version of itself with that of the latest
version released upon startup. If it doesn't know it's own version, this
comparison always falsely leads to it suggesting the user to update it
upon startup, where in fact it is updated. This is a confusing behavior
only NixOS users suffer and now it's solved.
