[sync] Timezone problem when synchronizing

[Remco Wulms]

DEBUG:  Backend of class SyncML_Backend_Horde created
DEBUG:  New session created: b11414691345dd9eb7671eadf76c077b
DEBUG:  checking auth for user=remcox
DEBUG:  authorized=1 version=1 msgid=1 source=IMEI:355659000917298  
target=http://hordedev.wulms.net/rpc.php user=remcox charset=UTF-8  
wbxml=1
DEBUG:  previous sync found for database: ./calendar; client-ts:  
20070531T113427Z
DEBUG:  SyncML: Anchor match, TwoWaySync since 20070531T113427Z
DEBUG:  Create new sync for ./calendar; synctype=200
DEBUG:  previous sync found for database: ./contacts; client-ts:  
20070531T113427Z
DEBUG:  SyncML: Anchor match, TwoWaySync since 20070531T113427Z
DEBUG:  Create new sync for ./contacts; synctype=200
DEBUG:  HandleFinal for state=0
DEBUG:  HandleFinal for state=0
DEBUG:  Received Final from client.
DEBUG:  Sending Final to client.
DEBUG:  SyncML: return message completed
DEBUG:  Finished at 2007-05-31 13:39:09. Packet logged in  
/tmp/sync/syncml_server_10.wbxml

DEBUG:  Backend of class SyncML_Backend_Horde created
DEBUG:  Existing session continued: b11414691345dd9eb7671eadf76c077b
DEBUG:  authorized=1 version=1 msgid=2 source=IMEI:355659000917298  
target=http://hordedev.wulms.net/rpc.php user=remcox charset=UTF-8  
wbxml=1
DEBUG:  created device class SyncML_Device_Nokia
DEBUG:  HandleFinal for state=1
DEBUG:  server create sync output for syncType=./calendar
DEBUG:  Compiling server changes from 2007-05-31 13:34:08 to  
2007-05-31 13:39:09
DEBUG:  sending 1 server changes for syncType=./calendar
DEBUG:  replace: 20070530134855.3c63evbzgjc4 at hordedev.wulms.net
DEBUG:  HandleFinal for state=1
DEBUG:  server create sync output for syncType=./contacts
DEBUG:  Compiling server changes from 2007-05-31 13:34:08 to  
2007-05-31 13:39:09
DEBUG:  sending 0 server changes for syncType=./contacts
DEBUG:  Received Final from client.
DEBUG:  Sending Final to client.
DEBUG:  SyncML: return message completed
DEBUG:  Finished at 2007-05-31 13:39:13. Packet logged in  
/tmp/sync/syncml_server_11.wbxml

DEBUG:  Backend of class SyncML_Backend_Horde created
DEBUG:  Existing session continued: b11414691345dd9eb7671eadf76c077b
DEBUG:  authorized=1 version=1 msgid=3 source=IMEI:355659000917298  
target=http://hordedev.wulms.net/rpc.php user=remcox charset=UTF-8  
wbxml=1
DEBUG:  HandleFinal for state=3
DEBUG:  HandleFinal for state=3
DEBUG:  Received Final from client.
DEBUG:  Sending Final to client.
INFO:   Successful sync of ./calendar! Summary: failures=0;  
client(Add,Replace,Delete,AddReplaces)=0,0,0,0;  
server(Add,Replace,Delete)=0,1,0
INFO:   Successful sync of ./contacts! Summary: failures=0;  
client(Add,Replace,Delete,AddReplaces)=0,0,0,0;  
server(Add,Replace,Delete)=0,0,0
DEBUG:  Finished at 2007-05-31 13:39:17. Packet logged in  
/tmp/sync/syncml_server_12.wbxml


Quoting Karsten Fourmont <fourmont at gmx.de>:

> Hi,
>
> VEVENT timestamps come in two flavors: in "local time" without an  
> ending "Z" an in UTC time, ending with a trailing "Z".
>
> The normal way of exchanging times is using UTC, that's what  
> currently exported by Horde SyncML.
> It seems the Nokia phone only accepts local time.
> I'll see what I can do.
> Can you send a log of one session (/tmp/sync/syncml_log.txt)?
>
> Thanks,
>  Karsten
>
> Remco Wulms wrote:
>> Hi,
>>
>> I'm trying to synchronize the calender of my Nokia 6681 with   
>> Kronolith, using the cvs HEAD of today. Events that are sent to   
>> Kronolith work fine, but events that are sent from Kronolith end up  
>>  with start and end times 2 hours too early on the phone.
>>
>> The timezone settings of both the phone and Horde are set to  
>> Europe/Amsterdam.
>>
>> From /tmp/sync/data.txt:
>>
>> Client -> server
>>
>> DTSTART:20070601T190000
>> DTEND:20070601T220000
>>
>> These times get sent unconverted to Kronolith, and are displayed in  
>>  the same way, so this is correct.
>>
>> Server -> client
>>
>> DTSTART:20070602T190000Z
>> DTEND:20070602T210000Z
>>
>> These times seem to be converted to GMT, and end up 2 hours early  
>> on  the phone.
>>
>> Any ideas how to get this working properly?
>>
>> Regards, Remco
>>
>
>