http://bugzilla.moblin.org/show_bug.cgi?id=8048
--- Comment #3 from pohly <[email protected]> 2009-11-25 06:24:59 PST --- Other use cases that we must support: 1. SyncEvolution 1.0 must co-exist with 0.9.1 - set up one configuration with SyncEvolution 0.9.1 - remove all SyncEvolution 1.0 configs which might exist in ~/.config/syncevolution/default - sync with 1.0, using old config - sync with 0.9.1, using same config - sync with 1.0, using old config Expected outcome: - the last two syncs should be normal two-way syncs 2. migrate a single 0.9.x configuration without forcing a slow sync. - do the steps from use case 1 - SyncEvolution 1.0 "--migrate <config name>" - sync with 1.0, using new config (check path in --print-servers) Expected outcome: - a normal two-way sync, config in ~/.config/syncevolution/default *Not* expected: being able to use SyncEvolution 0.9.1 with this config anymore. Going back is possible by renaming the ".old" config, but leads to a slow sync. 3. migrate two 0.9.x configuration, using the same context - create two 0.9.1 configurations as in 1. - migrate both of them - sync config A - sync config B - sync config A Expected outcome: - both configs have the deviceId of config A in ~/.config/syncevolution/default/config.ini and A's shared source properties (in particular, evolutionsource) - syncing A is always done as two-way sync - syncing B is a slow sync due to the changed deviceId 4. migrate two 0.9.x configurations, using different contexts - create two 0.9.1 configurations as in 1 - migrate them with <config 1>@client-1 and <config 2>@client-2 as server names - sync both Expected outcome: - two independent configs in ~/.config/syncevolution/client-[12] - no slow syncs -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
