sourceballs.service fails because of permission issues
It seems like the sourceballs service is hitting permission issues because it runs as the sourceballs service user and does not have permissions to create its own lock:
$ systemctl status sourceballs.service
× sourceballs.service - Sourceballs
Loaded: loaded (/etc/systemd/system/sourceballs.service; static)
Active: failed (Result: exit-code) since Wed 2024-02-21 14:39:02 UTC; 6h ago
TriggeredBy: ● sourceballs.timer
Process: 2906584 ExecStart=/srv/repos/git-packages/dbscripts/cron-jobs/sourceballs (code=exited, status=1/FAILURE)
Main PID: 2906584 (code=exited, status=1/FAILURE)
CPU: 53ms
Feb 21 14:39:01 gemini.archlinux.org systemd[1]: Starting Sourceballs...
Feb 21 14:39:02 gemini.archlinux.org sourceballs[2906584]: /srv/repos/git-packages/dbscripts/cron-jobs/../db-functions: line 137: /srv/repos/lock/script-sourceballs.lock: Permission denied
Feb 21 14:39:02 gemini.archlinux.org systemd[1]: sourceballs.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 14:39:02 gemini.archlinux.org systemd[1]: sourceballs.service: Failed with result 'exit-code'.
Feb 21 14:39:02 gemini.archlinux.org systemd[1]: Failed to start Sourceballs.
$ ls -ld /srv/repos/lock/
drwxrwxr-x+ 1 git-packages junior-packager 11558 Feb 21 11:41 /srv/repos/lock/
$ id sourceballs
uid=1083(sourceballs) gid=1083(sourceballs) groups=1083(sourceballs)
I am not sure whats a good way forward on this
cc @anthraxx