Re: [Opensync-users] msynctool hangs after successful sync

[Arno K. <ar...@ak...>]

I have the same problem with v0.22: sync works fine (evolution and
syncml/obex) but after the message "All conflicts have been reported"
msynctool won't shut down. I've looked into the sources but there seems to
be no trivial way to backport your changes of r3185 into v0.22. Is there a
way to further track this problem down?

/Arno


Michael Bell wrote:
> 
> Michael Bell schrieb:
>> Simon Josefsson schrieb:
>> 
>>> Running msynctool appears to works fine, but it doesn't seem to shut
>>> down properly.  So it will always flag the sync as unclean, and the next
>>> sync will be a slow-sync.  (That's why I can't test your patch: all my
>>> sync are slow-syncs!)
>> 
>> I have a similar problem actually but this is a very special bug:
>> 
>> 1. I need at minimum one objtype which only sends DELETEs or nothing
>> 2. I need at minimum one objtype which sends ADD or REPLACE
>> 
>> The result is that the plugin expects two maps but receives only one 
>> map. I will prepare a fix today but I don't know if this fixes your 
>> problem.
> 
> I commited two patches.
> 
> 1. I fixed libsyncml. The COMMITEDCHANGES event is now sent more 
> reliable. (rev 385)
> 
> 2. I replaced the commit code which depends on maps by more clean code 
> relies on COMMITEDCHANGES event. (rev 3185)
> 
> It works for me. This does not mean that your problem is fixed too :(
> 

-- 
View this message in context: http://www.nabble.com/opensync%2Bisync-breaks-fast-syncing%2C-generates-dupes-tp15340473p15790551.html
Sent from the Opensync - User mailing list archive at Nabble.com.