Package Details: radicale 2.1.8-2

Git Clone URL: (read-only)
Package Base: radicale
Description: Simple calendar (CalDAV) and contact (CardDAV) server
Upstream URL:
Licenses: GPL3
Submitter: guibou
Maintainer: mlq (fordprefect)
Last Packager: fordprefect
Votes: 65
Popularity: 1.924838
First Submitted: 2011-02-14 23:17
Last Updated: 2017-11-27 21:53

Latest Comments

robinde commented on 2017-11-30 09:49

@ntfc the `ProtectSystem` option relates to hardening security by mounting the entire fs ro. I didn't find much more info than this:

I was having a similar [Errno 30] Read-only file system problem until I noticed there is a ReadWritePath in the supplied radicale.service I added my /var/lib/radicale to this which I assume gave radicale write permission. You may need to add /var/log/radicale in order to give radicale rw permission on this folder. If this doesn't work you may also try `ProtectSystem=full` I don't know what this does in detail but it should be more secure than commenting out the option.

ntfc commented on 2017-11-28 21:23

Using the `radicale.service` option `ProtectSystem=strict`, I find that my radicale instance cannot write logs to `/var/log/radicale/log`, and thus is always restarting itself. Journalctl output:
Nov 28 21:17:23 hostname systemd[1]: Started radicale - A simple CalDAV (calendar) and CardDAV (contact) server.
Nov 28 21:17:25 hostname radicale[4235]: ERROR: Failed to start logger: Failed to load logging configuration file '/etc/radicale/logging': [Errno 30] Read-only file system: '/var/log/radicale/log'
Nov 28 21:17:25 hostname systemd[1]: radicale.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 21:17:25 hostname systemd[1]: radicale.service: Failed with result 'exit-code'.

Disabling `ProtectSystem=strict` fixed it for me

fordprefect commented on 2017-11-27 21:54

@SataMaxx: you are right, I commented the unit at that point, which seemed to me like the best solution.

SataMaxx commented on 2017-11-27 03:33

@aurl & @fordprefect: except the last line in this service file is referencing an arbitrary absolute path (albeit the default one), which breaks the installations of users who decided to set their own path.

It would be cool if you could insert a warning in the .install file :-)

To users who set their own collection path, simply edit the .service file in /usr/lib/systemd/system/radicale.service after the update and change the ReadWritePaths to your custom path.

fordprefect commented on 2017-11-26 21:50

@aurl: thank you for your suggestion, I included the best of both worlds.

aurl commented on 2017-11-26 21:38

The documentation ( comes with a more comprehensive systemd service file than what is packaged here. I think it may be worthwhile to borrow it.

MazeChaZer commented on 2017-10-19 04:53

Sure, in radicale/ pkg_resources is being imported, which is provided by setuptools.

fordprefect commented on 2017-10-18 21:32

@MazeChaZer: sorry, just catched up with this. Thanks for the hint with the dependencies. However, I was not able to find any hints that setuptools is a runtime dependency. Its only occurence is in the, which is only called during package build. Could you detail your finding?

MazeChaZer commented on 2017-10-10 21:00

Radicale 2.0 additionally has a runtime dependency on python-setuptools. This is easily overlooked because many other python packages depend on it so it's likely already installed on many machines.

MazeChaZer commented on 2017-10-08 00:07

Could you clean up the optional dependencies? python-dulwich is definitly not used anymore in version 2.0. Neither is python-requests, as it seems, but I'm not sure about that.

All comments