On a recent py27-calendarserver-9.0 (freebsd ports) should one expect caldavd
to auto upgrade a 24 -> 63 (postgress backend) database ?
A cursory glance at the code suggest this - but I see:
017-01-12T17:11:27+0000
[txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn]
Beginning database schema check.
2017-01-12T17:11:27+0000
[txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn]
Required database key VERSION: 63.
2017-01-12T17:11:27+0000 [twext.enterprise.adbapi2#debug] ConnectionPool: txn
busy 'UpgradeDatabaseCoreStep.getVersions': free=0, busy=1, waiting=0
2017-01-12T17:11:27+0000 [twext.enterprise.adbapi2#debug] ConnectionPool: txn
free 'UpgradeDatabaseCoreStep.getVersions': free=1, busy=0, waiting=0
2017-01-12T17:11:27+0000
[txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn]
Actual database key VERSION: 24.
2017-01-12T17:11:27+0000 [calendarserver.tap.caldav#error] Data store not
available; shutting down
and unfortunately
calendarserver_upgrade
Seems mired with some circular dependencies in this version:
Traceback (most recent call last):
File "/usr/local/bin/calendarserver_upgrade", line 11, in <module>
load_entry_point('CalendarServer==9.0', 'console_scripts',
'calendarserver_upgrade')()
...
File "/usr/local/lib/python2.7/site-packages/calendarserver/tap/util.py",
line 38, in <module>
from calendarserver.tools.util import checkDirectory
Any advice appreciated,
Dw
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/calendarserver-users
