FS#78324 - [nextcloud] nextcloud-cron.service hard-coded to php-legacy
Attached to Project:
Arch Linux
Opened by Richard Neumann (rne) - Friday, 28 April 2023, 22:36 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:18 GMT
Opened by Richard Neumann (rne) - Friday, 28 April 2023, 22:36 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:18 GMT
|
Details
Description:
In nextcloud 26.0.1-1 the binary of the systemd unit /usr/lib/systemd/system/nextcloud-cron.service is (still) hard-coded to php-legacy. Since nextcloud 26, nextcloud can be run with php, though, which is what I am doing, resulting in this error: /srv/http> systemctl status nextcloud-cron.service 04/29/2023 12:20:36 AM × nextcloud-cron.service - Nextcloud; run cron.php Loaded: loaded (/usr/lib/systemd/system/nextcloud-cron.service; static) Active: failed (Result: exit-code) since Sat 2023-04-29 00:20:01 CEST; 2min 9s ago Duration: 2ms TriggeredBy: ● nextcloud-cron.timer Process: 694 ExecStart=/usr/bin/php-legacy -f /usr/share/webapps/nextcloud/cron.php (code=exited, status=203/EXEC) Main PID: 694 (code=exited, status=203/EXEC) CPU: 1ms Apr 29 00:20:01 srv.richard-neumann.de systemd[1]: Started Nextcloud; run cron.php. Apr 29 00:20:01 srv.richard-neumann.de (p-legacy)[694]: nextcloud-cron.service: Failed to locate executable /usr/bin/php-legacy: No such file or directory Apr 29 00:20:01 srv.richard-neumann.de (p-legacy)[694]: nextcloud-cron.service: Failed at step EXEC spawning /usr/bin/php-legacy: No such file or directory Apr 29 00:20:01 srv.richard-neumann.de systemd[1]: nextcloud-cron.service: Main process exited, code=exited, status=203/EXEC Apr 29 00:20:01 srv.richard-neumann.de systemd[1]: nextcloud-cron.service: Failed with result 'exit-code'. I worked around this problem for now by systemd-editing the respective unit. |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:18 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/nextcloud/issues/4
Saturday, 25 November 2023, 20:18 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/nextcloud/issues/4
[1] https://wiki.archlinux.org/title/Nextcloud#Installation
[2] https://wiki.archlinux.org/title/Nextcloud#Background_jobs
But you could provide two units, e.g. nextcloud-cron.service and nextcloud-cron-legacy.service using the respective PHP version.
The Wiki is obviously outdated, since it instructs to create a drop-in that would result in the packaged unit again, since it mentions to use the php-legacy binary, which I do not have.
At any rate, if you insist on keeping a hard-coded php-legacy in there, the package should™ also explicitly depend on php-legacy imho, and not just on some PHP version that might not ship the needed binary.
FS#79319