The following patch appears to work for me; all I'm doing is changing the
script so it looks for the python2.6 binary, then the python2.5 binary. (the
default would also check the 'python' binary, which is a link to python2.7 -
and it's the use of python2.7 that is breaking things.
--- caldavd 2012-01-20 15:48:11.287759928 -0700
+++ /usr/bin/caldavd 2012-01-20 15:45:50.183936151 -0700
@@ -46,7 +46,7 @@
return 0;
}
-for v in "" "2.6" "2.5"; do
+for v in "2.6" "2.5"; do
for p in \
"${PYTHON:=}" \
"python${v}"
--
Troy Telford
[email protected]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
