Tickets :: [#12577] SyncML sync discards data

6.0.0-alpha14

7/2/25

Summary	SyncML sync discards data
Queue	Turba
Queue Version	4.1.1
Type	Bug
State	Duplicate
Priority	2. Medium
Owners
Requester	spam (at) ancow (dot) no-ip (dot) org
Created	08/16/2013 (4338 days ago)
Due
Updated	08/16/2013 (4338 days ago)
Assigned	08/16/2013 (4338 days ago)
Resolved	08/16/2013 (4338 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

08/16/2013 01:54:21 PM	spam (at) ancow (dot) no-ip (dot) org	Comment #5	Reply to this comment
We can only sync data that we actually support. There is a second part to this report, which ~~Bug 12329~~ only touches on: Nowadays people quite frequently have multiple (private) cell phone numbers and email addresses (I, e.g., have 2 private cell numbers and about 6 private email addresses). Since turba can't deal with them properly, it is completely unusable for synchronisation in all but trivial cases.

08/16/2013 01:18:13 PM	Jan Schneider	Comment #4 State ⇒ Duplicate	Reply to this comment
~~Bug 12329~~. We can only sync data that we actually support.

08/16/2013 12:34:57 PM	spam (at) ancow (dot) no-ip (dot) org	New Attachment: hordesync.txt

08/16/2013 12:34:00 PM	spam (at) ancow (dot) no-ip (dot) org	Comment #3	Reply to this comment
I did some formatting the variable width input window prevented and added syncevolution's legend. Note that the syncevolution output itself wasn't this readable, and probably won't get any better.

08/16/2013 07:37:59 AM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
The data is completely unreadable. Please use attachments instead.

08/16/2013 03:22:17 AM	spam (at) ancow (dot) no-ip (dot) org	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ SyncML sync discards data Queue ⇒ Turba Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
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@mail.ru \| EMAIL;TYPE=HOME:XXXXXX@mail > .ru > EMAIL;TYPE=HOME:XXXXXX@y > a.ru > EMAIL;TYPE=HOME:XXXXXX@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@mail.ru EMAIL:XXXXXX@mail.ru EMAIL:XXXXXX@ya.ru < EMAIL:XXXXXX@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.