summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/robotframework-pythonlibcore
diff options
context:
space:
mode:
authoremilylange <git@emilylange.de>2024-03-28 20:10:53 +0100
committeremilylange <git@emilylange.de>2024-03-28 20:10:53 +0100
commit9fb68677e40ad2bfec0cc6cbdbecdf1523c9430a (patch)
tree7f2fed285457e9df32bbc53e68c207653a88d43d /pkgs/development/python-modules/robotframework-pythonlibcore
parentb40caf8c8a7e30fa0befedd3e0139c59c3141af1 (diff)
forgejo: fix applying of our `STATIC_ROOT_PATH` patch
This fixes an issue where running the forgejo package standalone, without the use of our nixos/forgejo module, would try to use a directory named `@data@` for its `STATIC_ROOT_PATH` assets. This went unnoticed until now, because most users use the nixos/forgejo module in which we explicitly set this option/setting/path to `cfg.package.data` by default (`pkgs.forgejo.data`). Also, this commit hard-copies the patch in question from gitea to our nixpkgs derivation directory. We decided a long time ago to part ways, and forgejo inheriting the patch from gitea's drv directory puts strain on gitea. So we don't do that anymore and instead maintain that patch ourselves from now on. Unfortunately, `substituteInPlace --subst-var` does not error, when the substitution fails. This would have prevented this issue from going unnoticed.
Diffstat (limited to 'pkgs/development/python-modules/robotframework-pythonlibcore')
0 files changed, 0 insertions, 0 deletions