[CalendarServer-dev] Problem running calendarserver 6.2 in Debian

Axel Rau Axel.Rau at chaos1.de
Mon Oct 26 09:20:38 PDT 2015


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 at 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/001563.html).
>> 
>> 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 at apple.com>:
>>>> 
>>>>> Hi Rahul,
>>>>> 
>>>>> --On October 13, 2015 at 11:42:21 PM +0530 Rahul Amaram
>>>>> <amaramrahul at 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 at 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



More information about the calendarserver-dev mailing list