If we're running it from a build (fetchgit, fetchCargoVendor, etc),
none of the code paths that actually call Nix are hit.
If we're _not_ running it from a build, the user can reasonably be expected
to have a Nix present ambiently.
This avoids pulling Nix into the build closure of fetchCargoVendor,
and thus causing infrecs when Nix depends on Rust things.
Follow-up on #169733
For `data`, Nextcloud checks on its own if everything is readable.
However, for `config` it's crucial that the ownership is actually
correct: otherwise, systemd-tmpfiles will refuse any operations inside
because of unsafe path transitions.
This can result in a subtly broken setup by the `override.config.php`
not being updated, but also not part of the system closure anymore
(another override.config.php is referenced now) which means it'll be
GCed eventually even though Nextcloud relies on it.
If this precondition is not met, the following error will be printed:
nextcloud-setup-start[972]: /var/lib/nextcloud/config is not owned by user 'nextcloud'!
nextcloud-setup-start[972]: Please check the logs via 'journalctl -u systemd-tmpfiles-setup'
nextcloud-setup-start[972]: and make sure there are no unsafe path transitions.
nextcloud-setup-start[972]: (https://nixos.org/manual/nixos/stable/#module-services-nextcloud-pitfalls-during-upgrade)
The Go toolchain needed to build these is EOL, and comment says it doesn't want to be build with a newer toolchain, so removing these.
Signed-off-by: Paul Meyer <katexochen0@gmail.com>
Seems like upsteam support for Go 1.23 was added in 69588b0d14,
project builds and run the help command.
Signed-off-by: Paul Meyer <katexochen0@gmail.com>
Upstream project is archived, doesn't build anymore with supported Go toolchains.
Successor is pyroscope, which currently isn't packaged (https://github.com/NixOS/nixpkgs/pull/271139 still open).
Signed-off-by: Paul Meyer <katexochen0@gmail.com>
The toolchain was pinned due to a build failure in
https://hydra.nixos.org/build/276117884/nixlog/1/tail, which I couldn't
reproduce locally with the latest toolchain. The upstream project hasn't
seen updates in 4 years, so if the package breaks again we might just
remove it.
Signed-off-by: Paul Meyer <katexochen0@gmail.com>
