Re: [Opensync-users] Sync fails between Evo2 and GPE

[Andrew B. <and...@gm...>]

On Fri, 2006-05-19 at 14:35 +1200, Martin Felis wrote:
> Maybe you can give it a try and send again the
> output.

Here is the output of the updated plugin:

andrew@r51:~$ msynctool --sync zaurus
Synchronizing group "zaurus"
The previous synchronization was unclean. Slow-syncing
Member 1 of type gpe-sync just connected
Member 2 of type evo2-sync just connected
All clients connected or error
andrew@192.168.129.201's password: Received a entry
pas-id-44522C6900000000 with data of size 4 from member 2. Changetype
ADDED
Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004749Z-3935-1000-1-5@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005050Z-3935-1000-1-8@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004922Z-3935-1000-1-6@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T155339Z-4054-1000-1-0@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004703Z-3935-1000-1-4@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004615Z-3935-1000-1-3@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T113610Z-4076-1000-1-0@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005034Z-3935-1000-1-7@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005145Z-3935-1000-1-9@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005343Z-3935-1000-1-12@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005215Z-3935-1000-1-10@r51 with data of size 4
from member 2. Changetype ADDED
Member 2 of type evo2-sync just sent all changes

Member 1 of type gpe-sync just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 2 of type evo2-sync committed all changes.
Error writing entry pas-id-44522C6900000000 to member 1: Couldn't commit
contact:  invalid Base64 sequence
Mapping Write Error: Couldn't commit contact:  invalid Base64 sequence
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004525Z-3935-1000-1-2@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004749Z-3935-1000-1-5@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Error writing entry 20060517T005050Z-3935-1000-1-8@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004922Z-3935-1000-1-6@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004703Z-3935-1000-1-4@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004615Z-3935-1000-1-3@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Error writing entry 20060517T005034Z-3935-1000-1-7@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005145Z-3935-1000-1-9@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005343Z-3935-1000-1-12@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005215Z-3935-1000-1-10@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T155339Z-4054-1000-1-0@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T113610Z-4076-1000-1-0@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Member 1 of type gpe-sync committed all changes.
All clients have written
Member 1 of type gpe-sync just disconnected
Member 2 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects

Hope this helps,
Andrew Barr