<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 20, 2016, at 6:06 AM, <a href="mailto:amaramrahul@users.sourceforge.net" class="">amaramrahul@users.sourceforge.net</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; line-height:1.3; color:#1F497D" class=""><div class=""><br class=""></div><div class="">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?<br class=""></div></div></div></blockquote><div><br class=""></div><div>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.</div><div><br class=""></div><div>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.:</div><div><br class=""></div><div><a href="https://github.com/apple/ccs-calendarserver/blob/master/txdav/common/datastore/sql_schema/current.sql" class="">https://github.com/apple/ccs-calendarserver/blob/master/txdav/common/datastore/sql_schema/current.sql</a></div><div><br class=""></div><div>At the bottom, you'll see something like:</div><div><br class=""></div><div>insert into CALENDARSERVER values ('VERSION', '65');<br class="">insert into CALENDARSERVER values ('CALENDAR-DATAVERSION', '6');</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>-dre</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div style="font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; line-height:1.3; color:#1F497D" class=""><div id="signature-x" style="-webkit-user-select:none; font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; color:#1F497D" class="signature_editor"><div class=""><br class=""></div></div></div><div class="quoted_output_body"><div id="quoted_header" class="quoted_header_editor" style="clear:both;"><hr style="border:none; height:1px; color:#E1E1E1; background-color:#E1E1E1;" class=""><div style="border:none; padding:3.0pt 0cm 0cm 0cm" class=""><span style="font-size:11.0pt;font-family:Calibri, Arial, Helvetica, sans-serif" class=""><b class="">From:</b> Axel Rau <<a href="mailto:Axel.Rau@chaos1.de" class="">Axel.Rau@chaos1.de</a>><br class=""><b class="">Sent:</b> 20-Dec-2016 4:30 PM<br class=""><b class="">To:</b> <a href="mailto:amaramrahul@users.sourceforge.net" class="">amaramrahul@users.sourceforge.net</a><br class=""><b class="">Cc:</b> <a href="mailto:calendarserver-dev@lists.macosforge.org" class="">calendarserver-dev@lists.macosforge.org</a>; <a href="mailto:dre@apple.com" class="">dre@apple.com</a><br class=""><b class="">Subject:</b> Re: [CalendarServer-dev] Calendarserver 7.x compatibility with sqlparse 0.2.2<br class=""></span></div></div><br type="attribution" class=""><div id="quoted_body" class="quoted_body_editor"><div style="word-wrap:break-word" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">Am 20.12.2016 um 04:22 schrieb <a href="mailto:amaramrahul@users.sourceforge.net" class="">amaramrahul@users.sourceforge.net</a>:<br class=""></div><br class=""><div class=""><span style="color:rgb( 31 , 73 , 125 );font-family:'calibri' , 'arial' , 'helvetica' , sans-serif;font-size:16px;font-style:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline;float:none" class="">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.</span><br class=""></div></blockquote></div><div class=""><br class=""></div>I did the same for the FreeBSD port, I maintain:<br class=""><div class=""><a href="http://www.freshports.org/www/calendarserver/" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>http://www.freshports.org/www/calendarserver/</a><br class=""></div><div class=""><br class=""></div><div class="">Axel<br class=""><div class=""><div style="letter-spacing: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;" class=""><div style="font-family: helvetica; font-style: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;" class=""><div class="">---<br class="">PGP-Key:29E99DD6 ☀ computing @ chaos claudius<br class=""></div></div></div></div><br class=""></div></div></div></div></div></blockquote></div><br class=""></body></html>