[SyncEvolution] binfile: beware when moving home directory between machines

Hello! I just had a very weird problem: SyncEvolution consistently sent all items to the server in a normal sync, although they were not recognized as updated or new. The DB CreateContext method was called twice for the same datastore. Consider myself totally confused at that point. To cut a long story (several hours) short, the underlying reason was that I had copied my home directory from an older 32 bit Linux installation to a newer installation in 64 bit. The binfile implementation does not seem to cope with that well. I'm not sure how it caused the effects above, but after removing the entire .synthesis directory (the place where SyncEvolution keeps the Synthesis binfiles) syncs started to work normally again. It is not guaranteed that migrating from 32 bit to 64 bit by simply copying files works. However, my expectation was (and still is) that software should detect this, warn the user and the abort. Thoughts? Of course this happened while testing the final 0.9 release binaries, which is why I was close to despair and they are not announced yet ;-) -- 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.