Arch Linux User Repository

When updating your PHP, have a look whether Baikal still works and checkout the comments here for possible issues. Any hints/patches from your side are welcome of course, too. PHP is known to break things and it broke Baikal in the past. At the bottom of this comment you also find NGINX configuration snippets to use an older PHP version. Using an older PHP version is likely the best for being on the safe side although support for older PHP versions is also dropped from time to time from Baikal's side.

All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs
There's also a binary repository, also including older PHP versions: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#ownstuff

head -n 20 /etc/nginx/nginx.conf 
[...]
http {
    include php-handler.conf;
    include phpXX-handler.conf;

cat /etc/nginx/php.conf 
location ~ ^(/baikal.+?\.php)(/.*)?$ {
  try_files $1 =404;
  include fastcgi.conf;
  fastcgi_pass phpXX-handler; # handler registered via phpXX-handler.conf included in nginx.conf
  fastcgi_index index.php;
  fastcgi_param SCRIPT_FILENAME $document_root$1;
  fastcgi_param PATH_INFO $2;
  fastcgi_param HTTPS on;
}
location ~ ^(.+?\.php)(/.*)?$ {
  try_files $1 =404;
  include fastcgi.conf;
  fastcgi_pass php-handler; # handler registered via php-handler.conf included in nginx.conf
  fastcgi_index index.php;
  fastcgi_param SCRIPT_FILENAME $document_root$1;
  fastcgi_param PATH_INFO $2;
  fastcgi_param HTTPS on;
}

cat /etc/nginx/phpXX-handler.conf 
upstream phpXX-handler {
  server unix:/run/phpXX-fpm/php-fpm.sock;
}
cat /etc/nginx/php-handler.conf 
upstream php-handler {
  server unix:/run/php-fpm/php-fpm.sock;
}

(XX is of course supposed to be replaced by the actual PHP version.)

@wahsot I've updated the package. Thanks for letting me know about problems.

Please include this patch for further PHP 7.4 compatibility:

fixes #451 - respect operator precedence

It applies to vendor/sabre/vobject.

When updating to PHP 7.4 be sure to update to Baikal 0.6.1 as well.

The new version 0.6.0 seems to work nicely with PHP 7.3. (At least DavDroid shows no error message.) So one can ignore my previous comment. Because PHP devs apparently like to break things in minor releases it is still always a good idea to check whether everything is still working after upgrading PHP even if it is only a minor release update.

Turns out I should've paid closer attention to the comment by @Martchus - indeed Baikal doesn't work properly with PHP 7.3, but I never got an error message about my stuff not syncing properly anymore...

I learned that the hard way when deleting my account from my phone and discovering that I lost all events since February :-/

I'll be disowning that package as I'm switching to Nextcloud, seeing how Baikal is barely maintained.

I think the database initialization stuff isn't needed anymore nowadays, so I removed it from the .install file entirely. If someone could test it with a fresh install that'd be great - don't want to mess with my instance right now as I'm working on my bachelor thesis.

The post-install script wants to move a non-existent file: /usr/share/webapps/baikal/Core/Resources/Db/SQLite/db.sqlite It was renamed upstream to db.sql

@The-Compiler Thanks for the quick update.

I'd like to note that even the latest version (and as far as I've seen also the latest Git master) does not support PHP 7.3 yet.

Since PHP 7.3 landed in the official repositories one has to build php72 from the AUR. It can be install alongside the regular php packages. It was very easy to configure NGINX to use PHP 7.2 for Baikal and mainline PHP for the rest.

I've also added the packages to my binary repo (where you can also find baikal itself): https://wiki.archlinux.org/index.php/Unofficial_user_repositories#ownstuff

Here's a version including the patch mentioned by @cdo: https://github.com/Martchus/PKGBUILDs/blob/master/baikal/default/PKGBUILD

Seems to work so far. But switching to an alternative is likely inevitable in the long run.

In PHP 7.2, the each() function got deprecated and it will be removed in PHP 8 [1]. This results in an error when trying to access the Baikal admin interface. There exists a pull request [2] (although not yet merged to the master -- probably due to the ceased development of the project) which is supposed to resolve this issue.

And again: Thanks a lot for your work on this :-)

[1] https://wiki.php.net/rfc/deprecations_php_7_2#each [2] https://github.com/sabre-io/Baikal/pull/717