--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2009-07-25 08:59:54 ---
(In reply to comment #5)
(In reply to comment #3)
> a typo: no "slow-way", should be "slow" :)
> (In reply to comment #2)
> > What I have learned from these steps is that 'two-way' doesn't
> > normally after slow-way synchronization.
I can reproduce this 100% of the time with SyncEvolution 0.9.
I can not reproduce this ever with SyncEvolution 0.8.1a.
In my brief look at why I suspect a mapping problem after the slow sync in
SyncEvolution doesn't do any mapping. How can it have a problem with it then?
Reason: AAmBm creation
What is AAmBm?
on the server is failing with
SyncEvolution 0.9 because there is some incorrect mapping; the server tries to
get a mapping between the deleted item on the server and the existing item in
SyncEvolution 0.9 and fails.
How can that failure be caused by the client?
Since this works with the Stable version of SyncEvolution 0.8.1a
to believe this is a bug in SyncEvolution 0.9.
It's interesting that it doesn't occur with 0.8.1. Perhaps a comparison of the
two would show what the relevant difference is.
How can I help to solve this? I don't see what I can do without access to the
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.