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.)

@cdo Ouch, that sucks :( Applied the patch now. Thanks for letting me know! Time to search for an alternative I guess... What I've seen so far is Radicale (at least when I tested it worked poorly with AgenDAV as it didn't implement date range filters) and OwnCloud/NextCloud (too big if you just want CalDAV/CardDAV)... :-/

Thanks a lot for your work on this. There exists a security issue [1] (possible authentication bypass) in the current upstream version, for which a patch [2] is available. However, the upstream package has recently been abandoned [3, 4]. Would it be possible to include the patch [2] into the PKGBUILD? [1] https://github.com/fruux/Baikal/issues/673 [2] https://github.com/fruux/Baikal/pull/686/files [3] https://evertpot.com/sabredav-eol/ [4] https://evertpot.com/sabredav-maintenance-update/

And the package seems to have issues with the symlinked Specific directory. I'm creating an issue upstream as well EDIT: scratch that, I forgot to restart php-fpm for the updated open_basedir settings

upstream dropped the default sqlite database. The install file needs updating.

Seems to work fine for me, too. By the way, the issue I had with the last update is also gone but I don't know what caused it.

Turns out this was an oversight on my part - updated!

I can't login with 0.4.3 anymore (with Baikal), so keeping this back for now until I have time to find out what's going on (this or next week, I hope).

The-Compiler: I opened two bug reports. Here the links if you want to subscribe for notifications: https://github.com/fruux/Baikal/issues/477 https://bugs.kde.org/show_bug.cgi?id=360097

I will try to investigate on this issue a little bit more before filing a bug report. Since it works with Davdroid I suspect that the cause of the error is not on the server side anyways. And yes, the web interface works. The browser plugin for GET requests works, too.

Hmm, that's odd. Visiting the webinterface works? I suggest you open an issue in their issue tracker, as I suspect this is an upstream issue: https://github.com/fruux/Baikal/issues Feel free to mention me (@The-Compiler) though, so I get notifications.