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

[Martin F. <ma...@si...>]

Hello again,

yes it definitely helps. The problem is probably libmimedir on the gpe
side which refuses to parse dates that are not in the format
libmimedir expects.

I have the same problem here. I will let you know if I have a solution.

Cheers,
Martin

On 5/20/06, Andrew Barr <and...@gm...> wrote:
> 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

[...]

> 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
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQBEbfnohuM+Z62a52oRAqE2AJ9DlyK/Mfr/DlgoawtzacPJDPaX/ACgvTYG
> FcVdUG0BQxu2466lUapCRAM=3D
> =3DBnoY
> -----END PGP SIGNATURE-----
>
>
>