On Wednesday 20 January 2016 09:56 PM, Ximin Luo wrote:
On 20/01/16 15:23, Ximin Luo wrote:
Hey, I just tested 7.0+dfsg from git and it seems to work fine. Thanks for the 
work, and looking forward to the eventual upload! Just a few notes:

(a) [..]

(b) [..]

(c) [..]

(d) [..]

Some extra notes, after trying to migrate 5.2.2+dfsg-2 to 7.0+dfsg-1 (commit 
01c5df30):

(e) python-twext should declare

Replaces: calendarserver (<< 7.0+dfsg-1)
Breaks: calendarserver (<< 7.0+dfsg-1)
Done.

(see Policy 7.6.1)

(f) We should tell people explicitly in README.Debian to run 
calendarserver_upgrade. At least, I assume this is what I have to do, because 
error.log says this:

2016-01-20 17:11:25+0100 [-] Log opened.
2016-01-20 17:11:25+0100 [-] 
[txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] 
Beginning database schema check.
2016-01-20 17:11:25+0100 [-] 
[txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] 
Required database key VERSION: 58.
2016-01-20 17:11:25+0100 [-] 
[txdav.common.datastore.upgrade.sql.upgrade.UpgradeDatabaseSchemaStep#warn] 
Actual database key VERSION: 28.
2016-01-20 17:11:25+0100 [-] [calendarserver.tap.caldav#error] Data store not 
available; shutting down
2016-01-20 17:11:25+0100 [-] [memcached-Default] Signal handled: Terminated.
Done.

(g) I also need to edit 
/usr/lib/python2.7/dist-packages/CalendarServer-7.0a1+unknown.egg-info/requires.txt and 
remove the line that says "kerberos" (I am not using it anyway). Probably we 
need to remove that from setup.py in the source package.
What does this break?

(h) calendarserver_upgrade is not working for me at the moment. I've migrated accounts.xml to the new format 
(<accounts> -> <directory> and <user> -> <record>) and I get this:

$ sudo calendarserver_upgrade -D -s
Converting augments.xml
Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 81, 
in callWithContext
     return func(*args,**kw)
   File "/usr/lib/python2.7/dist-packages/twext/internet/threadutils.py", line 
48, in _run
     while self._qpull():
   File "/usr/lib/python2.7/dist-packages/twext/internet/threadutils.py", line 
69, in _qpull
     return True
   File "/usr/lib/python2.7/dist-packages/twext/internet/threadutils.py", line 
82, in _oneWorkUnit
     self._reactor.callFromThread(deferred.callback, result)
--- <exception caught here> ---
   File "/usr/lib/python2.7/dist-packages/twext/internet/threadutils.py", line 
74, in _oneWorkUnit
     result = instruction()
   File "/usr/lib/python2.7/dist-packages/twext/enterprise/adbapi2.py", line 
1158, in initCursor
     txn._connection = self.connectionFactory()
   File "/usr/lib/python2.7/dist-packages/txdav/base/datastore/dbapiclient.py", 
line 243, in connect
     connection = self.dbModule.connect(*self.connectArgs, **self.connectKw)
   File "/usr/lib/python2.7/dist-packages/pg8000/__init__.py", line 103, in 
connect
     user, host, unix_sock, port, database, password, ssl, timeout)
   File "/usr/lib/python2.7/dist-packages/pg8000/core.py", line 1618, in 
__init__
     raise self.error
pg8000.core.InterfaceError: md5 password authentication failed
^CTraceback (most recent call last):
Failure: twext.enterprise.ienterprise.ConnectionError: connection pool shut 
down while txn waiting for database connection.
[previous 2 lines repeated another 8 times]

I also tried setting <key>Enabled</key><false/> for md5 authentication in 
caldavd.plist and the result was the same.

Upgrade failure is something that I am aware of and have started a conversation on calendarserver mailing list. However, I do believe that you have found a fix for this.
X


Reply via email to