Re: [SyncEvolution] merging "server-config" branch?

On Wed, 2009-11-25 at 08:35 +0000, Patrick Ohly wrote: Yongsheng mentioned a patch for 7981, but it seems to be a bit uncertain why and when exactly it is required. Most of tonight's tests ran fine. Done, no problems. Done. Note that I had to make one more change related to client-test: when it creates the two test configs anew, it will use @client-test-1 and @client-test-2 as contexts, to ensure that both simulated clients have their own deviceId and evolutionsource properties. Old configs are used as they are, so no immediate action is needed when upgrading to master. In the nightly testing, configs are created anew each night. I have updated the script which does that so that it works with old and new SyncEvolution. At least that was the plan. It doesn't seem to be working and because of choir rehearsals tonight I won't be able to fix it before the night starts. Please ignore nightly test failures... Found a problem with the code: when creating a new peer inside an existing context, the peer-specific properties like "uri" were not set. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.