Hello, I am using Radicale (on my A20-OLinuXino-LIME2), sharing calendars within my family. Some days ago, syncing has stopped. Now I noticed that FreedomBox/Plinth (19.0) shows the Radicale application as not enabled any more.
This seems to be connected with the update from Radicale 1.x to 2.x: Via ssh, I see: > jondo@freedombox:~$ sudo apt -f install > [sudo] password for jondo: > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following packages were automatically installed and are no longer > required: > ebtables libevent-core-2.1-6 libopts25 ntp python-radicale ruby-rack-test > Use 'sudo apt autoremove' to remove them. > 0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Setting up radicale (2.1.11-4) ... > > Configuration file '/etc/default/radicale' > ==> Modified (by you or by a script) since installation. > ==> Package distributor has shipped an updated version. > What would you like to do about it ? Your options are: > Y or I : install the package maintainer's version > N or O : keep your currently-installed version > D : show the differences between the versions > Z : start a shell to examine the situation > The default action is to keep your current version. > *** radicale (Y/I/N/O/D/Z) [default=N] ? D > --- /etc/default/radicale 2018-07-08 07:41:54.888806318 +0200 > +++ /etc/default/radicale.dpkg-new 2018-12-10 10:49:30.000000000 +0100 > @@ -1,7 +1,7 @@ > # Defaults for radicale calendar server (sourced from /etc/init.d/radicale) > > -# Uncomment to start radicale on system startup > -#ENABLE_RADICALE=yes > +# If you want radicale to be started as a system service, > +# enable it using the command 'update-rc.d radicale enable' > > # Options for radicale on startup > # Note that most options can be specified in /etc/radicale/config > @@ -10,4 +10,3 @@ > # Make initscript verbose, override system default > # (Note: This is ONLY about the initscript!) > VERBOSE=yes > -ENABLE_RADICALE=yes Is this one of the problems that will be fixed by version 19.1? Its release announcement had several items seemingly related to the Radicale update. I guess that simply keeping the old /etc/default/radicale (or even trying to reactivate Radicale via GUI) wouldn't make sense here. Best regards, Robert _______________________________________________ Freedombox-discuss mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
