http://bugzilla.moblin.org/show_bug.cgi?id=9329 Summary: Manually added sources will affect new configuration unexpectly Classification: Moblin Projects Product: SyncEvolution Version: upstream Platform: Netbook OS/Version: Moblin Linux Status: NEW Severity: normal Priority: Undecided Component: SyncEvolution AssignedTo: patrick.ohly(a)intel.com ReportedBy: yanshuang.zheng(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution(a)lists.intel.com pkg: sync-0.9.99.4 As bug #8424 described, sync will create a new source if user needs it for configured service. Thus, the new added source should only be in the very configured service. But with sync-0.9.99.3(or 4), the behavior is: After this new source is added to service A, it will also be added to all services that change/create configuration. It collects a union set of sources in all service. Steps: 1. setup configurations with scheduleoworld template: $syncevolution -c -y username=<my_account> -y password=<my_password> -l scheduleworld test1 $syncevolution -c -y username=<my_account> -y password=<my_password> -l scheduleworld test2 2. add a new source to test1: $syncevolution -c -z uri=xxx test1 xxx ==> new source 'xxx' in test1, no 'xxx' in test2 3. change configuration of test2: $syncevolution -c -s two-way test2 ==> new source 'xxx' in test2 4. add a new configuration test3: $syncevolution -c -y username=<my_account> -y password=<my_password> -l scheduleworld test3 ==> there is 'xxx' in test3 Assume it a regression brought by fixing bug #8424 -- 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.