http://bugzilla.moblin.org/show_bug.cgi?id=4703
--- Comment #2 from shuangeeer <yanshuang.zheng(a)intel.com> 2009-07-23 19:39:15 ---
What I have learned from these steps is that 'two-way' doesn't behavior
normally after slow-way synchronization.
(In reply to comment #0)
package: syncevolution-0.8.1.99.4.09beta3-1.1.moblin2.i586
steps:
1. delete all data first, configure a service with scheduleworld template:
$syncevolution -c -y username=<username> -y password=<password> -l
scheduleworld test
2. create one item on server, and run a sync to make all data synced:
$syncevolution --run -s two-way test
3. now server and client both have one item, run slow sync:
$syncevolution --run -s slow test
4. now server and client still both have one item, delete the item on server
and run two-way sync:
$syncevolution --run -s two-way test
after all these steps, now sever has no item and client remains one item, the
status of server and client is not synchronized.
--
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.