retest with snapshot 20090730, we now get the correct sync results: 1. create a recurrent eventA on server(schedulewoorld) with occurrence {A1, A2, A3}, refresh them to client(Moblin netbook) through SyncEvolution ==> {A1, A2, A3} are shown in calendar on client ( client received 1 change ) 2. delete A1 on server, and sync in two-way ==> {A2, A3} on client, {A2, A3} on server 3. delete {A2, A3} on server; and refresh A from client to server ==> {A2, A3} on server, and {A2, A3} on client ( client sent 2 changes ) 4. refresh A on server to another client(FC10) ==> {A2, A3} in evolution on fc9 Before verifying this bug, I got a small question about the statistics of occurrences. We could see that in step1, client received 1 change, while in step3, client sent 2 changes. seems that they are counted by different rules, with step1 by counting the entire(parent) recurrent event, and step3 by counting every instance(child)?