Quoting Timo Boettcher (2017-06-14 00:59:50) > according to the radicale 1 to 2 migration guide > http://radicale.org/1to2/ > > "Calendars and address books are stored in a different way between > 1.x.x and 2.0.x versions. Launching 2.0.x without migrating your > collections first will not work, Radicale won’t be able to read your > previous data." "To migrate data to Radicale 2.0.x the command line > argument --export-storage was added to Radicale 1.1.3." > > As Radicale 1.1.3 is currently the newest release of the Radicale > 1.1.x branch, it is the ownly Radicale release providing the ability > to convert existing data stored in radicale installations to the > format required by Radicale 2.x.x. > > Currently, Radicale 1.1.3 is not available as Debian package. To > enable continued use of the Radicale package by Debian users in the > future 2.x.x releases (already in experimental), I kindly ask Radicale > 1.1.3 to be packaged or the --export-storage functionality backported. > > This would ensure that this functionality is rolled out once it is > needed when migration to Radicale 2.x.x is required.
Thanks for reporting. Yes, we need to include the recently added --export-storage option in order to have a migration path to newer upstream releases. Since the radicale package targeted the upcoming stable Debian release is ahead of the older 1.x branch, we need to backport that code change. And then convince Debian release managers to get that change accepted into a point release of stable Debian. Also, I believe we should add a package-specific routine to create a backup to /var/backup each time the package is updated, similar to how slapd and ejabberd does it. And get that change into a point release too. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
