On Mon, 2012-03-26 at 10:26 +0200, Patrick Ohly wrote: > On Mon, 2012-03-26 at 09:57 +0200, Lukas Zeller wrote: > > Hi Patrick, > > > > On Mar 26, 2012, at 9:07 , Patrick Ohly wrote: > > > > > I should add that this X-SYNTHESIS-RESTART was introduced in the 1.3 > > > pre-releases. You can downgrade to the latest stable 1.2.2 without > > > problems for syncing to avoid the 500 internal server error for the time > > > being. > > > > Just to make sure: Am I right that X-SYNTHESIS-RESTART (which now > > causes problems with Funambol) is only included in devInf when the > > datastore config has <canrestart>yes</canrestart>? > > Correct. "X-SYNTHESIS-RESTART not present" means "restarting not > supported", which is the default and thus continues to work fine.
FWIW, this issue was not found earlier because it looked like a network issue caused by the "onemedia" role-out by Funambol [1]. The detailed log shows the same problem [2]. I have an open question pending on the Funambol forum regarding that [2] and meant to investigate later. The Funambol server is the only server in the nightly testing which has an issue with the non-numeric SyncCap. [1] http://syncev.meego.com/2012-03-12-19-36_dist/testing-amd64/nightly.html#funambol [2] http://syncev.meego.com/2012-03-12-19-36_dist/testing-amd64/19-funambol/Client_Sync_eds_contact_testItems.log.html [3] https://core.forge.funambol.org/ds/viewMessage.do?dsForumId=405&dsMessageId=189836 -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
