You are not logged in.
Hello,
php-sysvsem is expected since Nextcloud 26.0.
This package does not exists in official packages of php-* suite.
Package exists in AUR's but as php82-* which implies to install php82 & php82-* packages and change Nginx/Nextcloud configuration.
Can you expect us to introduce this package?
Cromagnon31
Il vaut mieux un qui sait que dix qui cherchent / Better one who knows than ten looking.
Offline
0 ✓ srv ~ $ LANG=C pacman -Qo /usr/lib/php/modules/sysvsem.so
/usr/lib/php/modules/sysvsem.so is owned by php 8.2.4-2
0 ✓ srv ~ $
macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }
Offline
It's also present in php-legacy ( currently at version 8.1.17 ) which is mentioned as required for nextclould on archwiki page for nextcloud .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building to complicated ?
Try clean chroot manager by graysky
Online
With the nextcloud 26 update, you can run nextcloud with php 8.2 as provided by the php package.
macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }
Offline
Ok, so the proposed solution is to run
pacman -Syu php
.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building to complicated ?
Try clean chroot manager by graysky
Online
Since OP already appears to be running Nextcloud ("since Nextcloud 26.0"), they should also already be running either php or php-legacy, both of which ship the extension in question.
Apart from enabling it in the respective php.ini no further action should be necessary.
0 ✓ srv ~ $ grep -n sysvsem /etc/php/php.ini
949:extension=sysvsem
0 ✓ srv ~ $
Last edited by schard (2023-04-12 08:11:44)
macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }
Offline
@shard
Thanks for your help but I feel a little silly...
Il vaut mieux un qui sait que dix qui cherchent / Better one who knows than ten looking.
Offline