http://bugzilla.moblin.org/show_bug.cgi?id=8048 --- Comment #1 from pohly <patrick.ohly(a)intel.com&gt; 2009-11-21 09:34:19 PST --- The command line is partly broken right now: - --print-template ignores existing shared properties - new configs created with it do not preserve existing shared properties - client-test SyncEvolution breaks for most of the config creation tests (move those into test-dbus.py?!) -- 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.

http://bugzilla.moblin.org/show_bug.cgi?id=8048 --- Comment #3 from pohly <patrick.ohly(a)intel.com&gt; 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.

http://bugzilla.moblin.org/show_bug.cgi?id=8048 pohly <patrick.ohly(a)intel.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|syncevolution(a)lists.intel.c |patrick.ohly(a)intel.com |om | --- Comment #5 from pohly <patrick.ohly(a)intel.com&gt; 2009-11-25 07:59:49 PST --- Yongsheng, can you review my changes? See the new "config-server" branch. -- 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.

http://bugzilla.moblin.org/show_bug.cgi?id=8048 Bug 8048 depends on bug 7707, which changed state. Bug 7707 Summary: revised configuration layout: multiple peers per config http://bugzilla.moblin.org/show_bug.cgi?id=7707 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED -- 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.

http://bugzilla.moblin.org/show_bug.cgi?id=8048 --- Comment #8 from pohly <patrick.ohly(a)intel.com&gt; 2010-03-03 07:27:56 PST --- (In reply to comment #0) Code is in mb8048 branch. Yongsheng, can you review? Do you agree with the goal of the patch? One could argue that just like "configure" accepts unsupported --enable arguments, unsupported properties should be accepted silently or at most with a warning. It might make calling the command line easier in some (rare?) cases. -- 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.

http://bugzilla.moblin.org/show_bug.cgi?id=8048 --- Comment #10 from pohly <patrick.ohly(a)intel.com&gt; 2010-03-03 23:36:25 PST --- (In reply to comment #9) Right. It's pushed now. -- 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.

http://bugzilla.moblin.org/show_bug.cgi?id=8048 --- Comment #12 from pohly <patrick.ohly(a)intel.com&gt; 2010-03-05 03:16:10 PST --- (In reply to comment #11) So you are saying that for "--print-config --source-property sync=none @default" the error should not be printed because the "sync" property is not shown? I think the same argument for not allowing per-peer properties for --configure also applies here, although in a less severe way: the user did something which has no effect, perhaps because he expected it to have an effect, so we should tell him that there is something fishy about his command line. -- 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.

http://bugzilla.moblin.org/show_bug.cgi?id=8048 pohly <patrick.ohly(a)intel.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INTEGRATED --- Comment #14 from pohly <patrick.ohly(a)intel.com&gt; 2010-03-22 06:36:10 PST --- Included in 0.9.99.13. -- 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.