Closed LunarLambda closed 5 months ago
Hi, thanks a lot for the report!
Turns out, there is a typo in https://github.com/NixOS/nixpkgs/blob/2726f127c15a4cc9810843b96cad73c7eb39e443/pkgs/applications/version-management/forgejo/default.nix#L66
It should be modules/setting/server.go
not modules/setting/setting.go
, just like the patch:
This went unnoticed when using forgejo with the nixos module, because we explicitly set STATIC_ROOT_PATH
in the app.ini
to pkgs.forgejo.data
by default^1.
Will open a PR with a fix shortly :)
Thank you very much! I didn't notice the typo, glad I was able to provide enough information anyhow ^^
I heard substituteInPlace has a new --replace-fail option(?). Using that should prevent silent failures like this.
There is #299811 now.
I heard substituteInPlace has a new --replace-fail option(?). Using that should prevent silent failures like this.
From what I can tell, --replace-fail
does not apply to --subst-var
.
But feel free to check and write a review in #299811 :)
Describe the bug
forgejo fails to start up because the static file root path that is meant to point at the
data
output of the package was not correctly patched at build timeSteps To Reproduce
Steps to reproduce the behavior:
/nix/var/nix/profiles/default/bin/gitea doctor check -c /etc/forgejo/app.ini
(I was moving an existing install to the nix package to be up to date)Expected behavior
Forgejo should find the required frontend files provided by the
data
output and start properly.Additional context
I am aware that using nix and especially nixpkgs-unstable on a non-NixOS system comes with essentially no warranty whatsoever. However, given that the nix derivation is clearly intended to remove this
@data@
placeholder (source) and that it failing to do so seems to be the only thing wrong with my installation, I do not believe there is an error on my part.Notify maintainers
@emilylange @urandom @bendlas @adamcstephens
Metadata