[Tickets #12577] SyncML sync discards data

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12577
------------------------------------------------------------------------------
  Ticket             | 12577
  Created By         | spam at ancow.no-ip.org
  Summary            | SyncML sync discards data
  Queue              | Turba
  Version            | 4.1.1
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


spam at ancow.no-ip.org (2013-08-16 03:22) wrote:

I don't know whether this bug is in turba, the syncml component, or both.
I've been trying to sync my N900's contacts with turba using SyncML  
and SyncEvolution. The syncing process works fine, except that on  
every other sync, half the data for some contacts is deleted.
 From the SyncEvolution output, my re-adding the missing data results  
in the following sync:

-------------------------------------------------------------------------------
BEGIN:VCARD                              BEGIN:VCARD
N:SomeName    N:SomeName
  Middlename                Middlename
                                        > ADR;TYPE=HOME:;;Einestraße  
999;Einhaus
                                        >  en;KeinBundesland;99999;Deutschl
                                        >  and
ADR;TYPE=HOME:XXXXXX;;XXXXXXXXXXXXXX    ADR;TYPE=HOME:XXXXXX;;XXXXXXXXXXXXXX
  XXXXXXX;XXXXXXXXX;XXXXXXXXX;XXXXXX |         
XXXXXXX;XXXXXXXXX;XXXXXXXXX;XXXXXX;XX
                                       > XXXXXX
BDAY:XXXXXXXX                            BDAY:BDAY:XXXXXXXX
CATEGORIES:Freunde                       CATEGORIES:Freunde
EMAIL:XXXXXX at mail.ru         | EMAIL;TYPE=HOME:XXXXXX at mail
                                        >  .ru
                                        > EMAIL;TYPE=HOME:XXXXXX at y
                                        >  a.ru
                                        > EMAIL;TYPE=HOME:XXXXXX at y
                                        >  andex.ru
FN:Some Mid    FN:Some Mid
  dle Name               dle Name
PHOTO: 5680 b64 characters = 4259 byt  | PHOTO;VALUE=uri:file:///home/user/.os
  es, c444dc24a9b89d243e547a0006e3146e  |  so-abook/photos/EUEJ1W
  md5sum                                <
ROLE:XXXXXX         ROLE:XXXXXX
                                        > TEL;+XXXXXX1
                                        > TEL;+XXXXXX2
TEL;TYPE=HOME:+XXXXXX4    TEL;TYPE=HOME:+XXXXXX4
                                        > TEL;+XXXXXX3
VERSION:3.0                              VERSION:3.0
                                        > X-GENDER:female
                                        > X-SKYPE;TYPE=SKYPE:XXXXXX
END:VCARD                                END:VCARD
-------------------------------------------------------------------------------


Doing a second sync immediately after that, with no changes in turba  
or on the phone results in the following sync:

-------------------------------------------------------------------------------
BEGIN:VCARD                              BEGIN:VCARD
N:SomeName    N:SomeName
  Middlename                Middlename
ADR;TYPE=HOME:;;Einestraße 999;Einhaus  <
  en;KeinBundesland;99999;Deutschl <
  and                                   <
ADR;TYPE=HOME:XXXXXX;;XXXXXXXXXXXXXX    ADR;TYPE=HOME:XXXXXX;;XXXXXXXXXXXXXX
  XXXXXXX;XXXXXXXXX;XXXXXXXXX;XXXXXX;XX |    XXXXXXX;XXXXXXXXX;XXXXXXXXX;XXXXXX
  XXXXXX                                <
BDAY:XXXXXXXX                            BDAY:XXXXXXXX
CATEGORIES:Freunde                       CATEGORIES:Freunde
EMAIL:XXXXXX at mail.ru           EMAIL:XXXXXX at mail.ru
EMAIL:XXXXXX at ya.ru        <
EMAIL:XXXXXX at yandex.ru    <
FN:Some Mid    FN:Some Mid
  dle Name               dle Name
PHOTO;VALUE=uri:file:///home/user/.os  | PHOTO: 5680 b64 characters = 4259 byt
  so-abook/photos/7HOT1W                |  es, c444dc24a9b89d243e547a0006e3146e
                                        >  md5sum
ROLE:XXXXXX         ROLE:XXXXXX
TEL:+XXXXXX1                     <
TEL:+XXXXXX2                      <
TEL:+XXXXXX3                     <
TEL;TYPE=HOME:+XXXXXX4    TEL;TYPE=HOME:+XXXXXX4
VERSION:3.0                              VERSION:3.0
X-GENDER:female                        <
X-SKYPE:XXXXXX                     <
END:VCARD                                END:VCARD
-------------------------------------------------------------------------------

(The data is anonymised.)
The right side in the first sync represents the data present on the  
phone, the left side the data synced from turba. In the second sync,  
the sides are reversed as the direction of the data flow is reversed.

This excerpt from the sync protocol shows, that with multiple fields  
of the same type, only one of those fields is kept (see EMAIL,  
ADR;TYPE=HOME). Some types of fields, presumably those unknown to  
turba, are silently dropped (see TEL).


Since both problems represent data loss bugs and make turba unusable  
(not being able to have multiple fields of the same type is a serious  
problem!), this bug is pretty important.