On Dec 20, 2016, at 6:06 AM, amaramrahul@users.sourceforge.net wrote:


Even if I upgrade to 0.9, I think I'll still be facing the challenge of how to migrate the data from existing installations. Would I be right in this assumption of mine?

If you meant 9.0, as in CalendarServer 9.0, then the same rules apply here as for any CalendarServer upgrade: there may be a schema update required, so any time you update, be prepared for this possibility.

You can tell if a DB upgrade would be required by looking at txdav/common/datastore/sql_schema/current.sql for a given branch / release, e.g.:

https://github.com/apple/ccs-calendarserver/blob/master/txdav/common/datastore/sql_schema/current.sql

At the bottom, you'll see something like:

insert into CALENDARSERVER values ('VERSION', '65');
insert into CALENDARSERVER values ('CALENDAR-DATAVERSION', '6');

This means CalendarServer running that code would want schema version 65 and dataversion 6. You can check your DB's calendarserver table or look at startup-time logging in error.log to see your current version.

-dre


From: Axel Rau <Axel.Rau@chaos1.de>
Sent: 20-Dec-2016 4:30 PM
To: amaramrahul@users.sourceforge.net
Cc: calendarserver-dev@lists.macosforge.org; dre@apple.com
Subject: Re: [CalendarServer-dev] Calendarserver 7.x compatibility with sqlparse 0.2.2


Am 20.12.2016 um 04:22 schrieb amaramrahul@users.sourceforge.net:

Ouch. So that essentially means that as a Debian package maintainer, either I'll have to package a compatible sqlparse version separate or wait for upstream to release a version that works with sqlparse 0.2.2. given the Debian release timeline, I believe the former is my only option in reality.

I did the same for the FreeBSD port, I maintain:

Axel
---
PGP-Key:29E99DD6  ☀  computing @ chaos claudius