Arch Linux User Repository

PHP8 is now supported! Make sure to update your php setup if necessary :)

Hi. This won't currently build in a chroot because yarn install tries to clone a git repository and git isn't in makedepends.

As per default the open_basedir is not in effect i think it is fine and building from source is better in my opinion.

I think a comment in front of the command that would throw the error should be fine.

(It seams that that command is the composer clear-cache maybe it is posible to tell composer to not use a cache?)

@L0ric0 good point. There is a separate php ini file for the php cli, right? So it is possible to loosen your security restrictions there. Defining a custom open_base_dir is possible with php cli, but I think this is ugly, and PKGBUILDs should adhere to system configurations.

What do you think, should I switch back to the zip release file from the grocy team?

when the open_basedir restriction of php is in effect the installation of this package fails in the build function.

I've updated the package to version 3.0.1.

Additionally, the package is now build from the git source instead of the binaries released on their github page.

Also, the data dir (including the database) is now stored at /var/lib/webapps/grocy, the proper place where it should belong (instead of at /usr/share/webapps/grocy/data). This means that you have to backup your database before upgrading and move it there afterwards. Otherwise, the install will fail with an error that "/usr/share/webapps/grocy/data" already exists in the filesystem.

TL;DR (at your own risk):

mv /usr/share/webapps/grocy/data ~/grocy-bak
Update this package
sudo cp -r grocy-bak/* /var/lib/webapps/grocy/

@hashworks Done. Have fun :)

This won't build in a chroot environment:

==> Starting package()...
chown: invalid user: ‘http’
==> ERROR: A failure occurred in package().

Please use the fixed user id 33 instead.

There is a PHP dependencies missing: php-gd