Problem running calendarserver 6.2 in Debian
Hi, I am the Debian maintainer for calendarserver. For calendarserver 6.2, I have the new binaries built, including a new package for twext. But when I run it, I get the error: # caldavd -L Traceback (most recent call last): File "/usr/bin/twistd", line 14, in <module> run() File "/usr/lib/python2.7/dist-packages/twisted/scripts/twistd.py", line 27, in run app.run(runApp, ServerOptions) File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 652, in run config.parseOptions() File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 619, in parseOptions usage.Options.parseOptions(self, options) File "/usr/lib/python2.7/dist-packages/twisted/python/usage.py", line 262, in parseOptions for (cmd, short, parser, doc) in self.subCommands: File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 636, in subCommands for plug in sorted(plugins, key=attrgetter('tapname')): File "/usr/lib/python2.7/dist-packages/twisted/plugins/caldav.py", line 29, in getProperty return getattr(reflect.namedClass(self.serviceMakerClass), propname) File "/usr/lib/python2.7/dist-packages/twisted/python/reflect.py", line 168, in namedObject module = namedModule('.'.join(classSplit[:-1])) File "/usr/lib/python2.7/dist-packages/twisted/python/reflect.py", line 154, in namedModule topLevel = __import__(name) File "/usr/lib/python2.7/dist-packages/txdav/dps/server.py", line 21, in <module> from calendarserver.tap.util import getDBPool, storeFromConfigWithDPSServer File "/usr/lib/python2.7/dist-packages/calendarserver/tap/util.py", line 33, in <module> from calendarserver.provision.root import RootResource File "/usr/lib/python2.7/dist-packages/calendarserver/provision/root.py", line 37, in <module> from twistedcaldav.directory.principal import DirectoryPrincipalResource File "/usr/lib/python2.7/dist-packages/twistedcaldav/directory/principal.py", line 56, in <module> from twistedcaldav.resource import CalendarPrincipalCollectionResource, CalendarPrincipalResource File "/usr/lib/python2.7/dist-packages/twistedcaldav/resource.py", line 77, in <module> from calendarserver.push.notifier import getPubSubAPSConfiguration File "/usr/lib/python2.7/dist-packages/calendarserver/push/notifier.py", line 29, in <module> from txdav.common.datastore.sql_tables import schema File "/usr/lib/python2.7/dist-packages/txdav/common/datastore/sql_tables.py", line 78, in <module> schema = _populateSchema() File "/usr/lib/python2.7/dist-packages/txdav/common/datastore/sql_tables.py", line 64, in _populateSchema return SchemaSyntax(schemaFromPath(pathObj)) File "/usr/lib/python2.7/dist-packages/twext/enterprise/dal/parseschema.py", line 105, in schemaFromPath addSQLToSchema(schema, schemaData) File "/usr/lib/python2.7/dist-packages/twext/enterprise/dal/parseschema.py", line 152, in addSQLToSchema t = tableFromCreateStatement(schema, stmt) File "/usr/lib/python2.7/dist-packages/twext/enterprise/dal/parseschema.py", line 89, in tableFromCreateStatement cp.parse() File "/usr/lib/python2.7/dist-packages/twext/enterprise/dal/parseschema.py", line 335, in parse while self.nextColumn(): File "/usr/lib/python2.7/dist-packages/twext/enterprise/dal/parseschema.py", line 347, in nextColumn return self.parseColumn(maybeIdent.get_name()) File "/usr/lib/python2.7/dist-packages/twext/enterprise/dal/parseschema.py", line 515, in parseColumn theDefault.tokens[-1], cls=Parenthesis File "/usr/lib/python2.7/dist-packages/twext/enterprise/dal/parseschema.py", line 710, in expectSingle cls, "%s:%r" % (nextval.__class__.__name__, nextval) twext.enterprise.dal.parseschema.ViolatedExpectation: Expected <class 'sqlparse.sql.Parenthesis'> got Comment:<Comment '-- imp...' at 0x7fe4f014c490> Attaching the caldavd.plist file that I am using. The postgres database is created and pre-populated with the schema. Could you provide any pointers on why this is occurring? On a side note, if I run using the normal way i.e. ./bin/run -n, then it starts properly. So, not sure what is the issue here. Thanks, Rahul.
Hi Rahul, --On October 13, 2015 at 11:42:21 PM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
Attaching the caldavd.plist file that I am using. The postgres database is created and pre-populated with the schema. Could you provide any pointers on why this is occurring?
On a side note, if I run using the normal way i.e. ./bin/run -n, then it starts properly. So, not sure what is the issue here.
Right now we require version 0.1.14 of the sqlparse Python package. There are newer versions of that available but there is an incompatibility with those that we have not yet addressed. -- Cyrus Daboo
Hi Cyrus & Rahul, I have the same problem on FeeBSD ports. Am 13.10.2015 um 20:15 schrieb Cyrus Daboo <cdaboo@apple.com>:
Hi Rahul,
--On October 13, 2015 at 11:42:21 PM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
Attaching the caldavd.plist file that I am using. The postgres database is created and pre-populated with the schema. Could you provide any pointers on why this is occurring?
On a side note, if I run using the normal way i.e. ./bin/run -n, then it starts properly. So, not sure what is the issue here.
Right now we require version 0.1.14 of the sqlparse Python package. There are newer versions of that available but there is an incompatibility with those that we have not yet addressed.
Isn’t sqlparse optional in 6.2? http://www.calendarserver.org/changeset/12305 Axel --- PGP-Key:29E99DD6 ☀ +49 160 9945 7889 ☀ computing @ chaos claudius
Just spoke to my mentor Guido. The best option seems to be to make calendarserver code compatible with 0.16.1. None of the debian python packages that I or my mentor is aware of use pip or virtualenv in order to encourage shared python dependencies. What is the feasibility for making calendarserver compatible with 0.16.1? We can't be stuck at 0.14.1 anyway :). Thanks, Rahul. On Wednesday 14 October 2015 03:42 PM, Axel Rau wrote:
Hi Cyrus & Rahul,
I have the same problem on FeeBSD ports.
Am 13.10.2015 um 20:15 schrieb Cyrus Daboo <cdaboo@apple.com>:
Hi Rahul,
--On October 13, 2015 at 11:42:21 PM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
Attaching the caldavd.plist file that I am using. The postgres database is created and pre-populated with the schema. Could you provide any pointers on why this is occurring?
On a side note, if I run using the normal way i.e. ./bin/run -n, then it starts properly. So, not sure what is the issue here. Right now we require version 0.1.14 of the sqlparse Python package. There are newer versions of that available but there is an incompatibility with those that we have not yet addressed. Isn’t sqlparse optional in 6.2? http://www.calendarserver.org/changeset/12305
Axel --- PGP-Key:29E99DD6 ☀ +49 160 9945 7889 ☀ computing @ chaos claudius
As suggested by dre, adding whitespace to the schema file didn't help (see https://lists.macosforge.org/pipermail/calendarserver-dev/2012-November/0015...). I eventually downgraded to sqlparse 0.1.13, so that I can at least test the other components. But this remains the biggest issue as of now for packaging version 7.0. Could upstream look into making calendarserver / twext compatible with sqlparse 0.1.16? Thanks, Rahul. On Wednesday 14 October 2015 10:47 PM, Rahul Amaram wrote:
Just spoke to my mentor Guido. The best option seems to be to make calendarserver code compatible with 0.16.1. None of the debian python packages that I or my mentor is aware of use pip or virtualenv in order to encourage shared python dependencies.
What is the feasibility for making calendarserver compatible with 0.16.1? We can't be stuck at 0.14.1 anyway :).
Thanks, Rahul.
On Wednesday 14 October 2015 03:42 PM, Axel Rau wrote:
Hi Cyrus & Rahul,
I have the same problem on FeeBSD ports.
Am 13.10.2015 um 20:15 schrieb Cyrus Daboo <cdaboo@apple.com>:
Hi Rahul,
--On October 13, 2015 at 11:42:21 PM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
Attaching the caldavd.plist file that I am using. The postgres database is created and pre-populated with the schema. Could you provide any pointers on why this is occurring?
On a side note, if I run using the normal way i.e. ./bin/run -n, then it starts properly. So, not sure what is the issue here. Right now we require version 0.1.14 of the sqlparse Python package. There are newer versions of that available but there is an incompatibility with those that we have not yet addressed. Isn’t sqlparse optional in 6.2? http://www.calendarserver.org/changeset/12305
Axel --- PGP-Key:29E99DD6 ☀ +49 160 9945 7889 ☀ computing @ chaos claudius
_______________________________________________ calendarserver-dev mailing list calendarserver-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-dev
I believe I have found the incompatibility issue with 0.1.16. Attaching the patch with this email. Can't believe that the fix is this simple :). Thanks, Rahul. On Thursday 15 October 2015 02:06 PM, Rahul Amaram wrote:
As suggested by dre, adding whitespace to the schema file didn't help (see https://lists.macosforge.org/pipermail/calendarserver-dev/2012-November/0015...).
I eventually downgraded to sqlparse 0.1.13, so that I can at least test the other components. But this remains the biggest issue as of now for packaging version 7.0.
Could upstream look into making calendarserver / twext compatible with sqlparse 0.1.16?
Thanks, Rahul.
On Wednesday 14 October 2015 10:47 PM, Rahul Amaram wrote:
Just spoke to my mentor Guido. The best option seems to be to make calendarserver code compatible with 0.16.1. None of the debian python packages that I or my mentor is aware of use pip or virtualenv in order to encourage shared python dependencies.
What is the feasibility for making calendarserver compatible with 0.16.1? We can't be stuck at 0.14.1 anyway :).
Thanks, Rahul.
On Wednesday 14 October 2015 03:42 PM, Axel Rau wrote:
Hi Cyrus & Rahul,
I have the same problem on FeeBSD ports.
Am 13.10.2015 um 20:15 schrieb Cyrus Daboo <cdaboo@apple.com>:
Hi Rahul,
--On October 13, 2015 at 11:42:21 PM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
Attaching the caldavd.plist file that I am using. The postgres database is created and pre-populated with the schema. Could you provide any pointers on why this is occurring?
On a side note, if I run using the normal way i.e. ./bin/run -n, then it starts properly. So, not sure what is the issue here. Right now we require version 0.1.14 of the sqlparse Python package. There are newer versions of that available but there is an incompatibility with those that we have not yet addressed. Isn’t sqlparse optional in 6.2? http://www.calendarserver.org/changeset/12305
Axel --- PGP-Key:29E99DD6 ☀ +49 160 9945 7889 ☀ computing @ chaos claudius
_______________________________________________ calendarserver-dev mailing list calendarserver-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-dev
Thanks for the patch. Works and has been submitted to FreeBSD port repo. Axel Am 25.10.2015 um 17:57 schrieb Rahul Amaram <amaramrahul@users.sourceforge.net>:
I believe I have found the incompatibility issue with 0.1.16. Attaching the patch with this email. Can't believe that the fix is this simple :).
Thanks, Rahul.
On Thursday 15 October 2015 02:06 PM, Rahul Amaram wrote:
As suggested by dre, adding whitespace to the schema file didn't help (see https://lists.macosforge.org/pipermail/calendarserver-dev/2012-November/0015...).
I eventually downgraded to sqlparse 0.1.13, so that I can at least test the other components. But this remains the biggest issue as of now for packaging version 7.0.
Could upstream look into making calendarserver / twext compatible with sqlparse 0.1.16?
Thanks, Rahul.
On Wednesday 14 October 2015 10:47 PM, Rahul Amaram wrote:
Just spoke to my mentor Guido. The best option seems to be to make calendarserver code compatible with 0.16.1. None of the debian python packages that I or my mentor is aware of use pip or virtualenv in order to encourage shared python dependencies.
What is the feasibility for making calendarserver compatible with 0.16.1? We can't be stuck at 0.14.1 anyway :).
Thanks, Rahul.
On Wednesday 14 October 2015 03:42 PM, Axel Rau wrote:
Hi Cyrus & Rahul,
I have the same problem on FeeBSD ports.
Am 13.10.2015 um 20:15 schrieb Cyrus Daboo <cdaboo@apple.com>:
Hi Rahul,
--On October 13, 2015 at 11:42:21 PM +0530 Rahul Amaram <amaramrahul@users.sourceforge.net> wrote:
Attaching the caldavd.plist file that I am using. The postgres database is created and pre-populated with the schema. Could you provide any pointers on why this is occurring?
On a side note, if I run using the normal way i.e. ./bin/run -n, then it starts properly. So, not sure what is the issue here. Right now we require version 0.1.14 of the sqlparse Python package. There are newer versions of that available but there is an incompatibility with those that we have not yet addressed. Isn’t sqlparse optional in 6.2? http://www.calendarserver.org/changeset/12305
Axel --- PGP-Key:29E99DD6 ☀ +49 160 9945 7889 ☀ computing @ chaos claudius
_______________________________________________ calendarserver-dev mailing list calendarserver-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-dev
<sqlparse-0.1.16-fix.patch>
--- PGP-Key:29E99DD6 ☀ +49 160 9945 7889 ☀ computing @ chaos claudius
participants (4)
-
Axel Rau
-
Axel Rau
-
Cyrus Daboo
-
Rahul Amaram