http://bugzilla.moblin.org/show_bug.cgi?id=2416
--- Comment #8 from pohly <[email protected]> 2009-12-17 04:59:26 PST --- (In reply to comment #7) > The other option, which also works with other servers, is to erase the > server's > anchor in the client's .synthesis/sysynclib_targ.bfi file. I'm attaching a > Perl > script which does that. It is based on the assumption that certain strings > must > be the anchors. It replaces the first anchor found. To "break" more sources, > run the script multiple times. Wait, that didn't work as intended. I forgot to test a real sync. When the script is used as proposed, it will erase the *server's* anchor locally, leading to the situation that the Synthesis library itself asks for a slow sync after running the <alertscript> (Alert for two-way received, <alertscript> runs okay, engine compares anchors, replies with 508 status to Alert => slow sync). This is similar to the problem in the server. Need to think about this a bit more... To properly trigger the "unexpected slow sync" from the client side, one has to erase the client's anchor. Because this is done as an integer in the sysynclib_targ.bfi file (presumably), I don't know how to do that selectively. Removing the whole file works (tested!). -- 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. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
