On Fri, 2012-09-28 at 15:39 +0200, Daniel CLEMENT wrote: It would be nice to get 1.3 instead, which has been released. What was the exact problem? Did you use the UI or command line? Getting a copy of your ~/.cache/syncevolution directory would be useful, with information about which session in it was the one that showed the error described above. It should be fine to just upgrade. The release notes sometimes mention steps that need to be made manually. Have a look at the NEWS file. For example, for 1.2.2 -> 1.3, the manual steps are: ---------------------------------- Upgrading from release 1.2.x: The sync format of existing configurations for Mobical (aka Everdroid) must be updated manually, because the server has encoding problems when using vCard 3.0 (now the default for Evolution contacts): syncevolution --configure \ syncFormat=text/x-vcard \ mobical addressbook The Funambol template explicitly enables usage of the "refresh-from-server" sync mode to avoid getting throttled with 417 'retry later' errors. The same must be added to existing configs manually: syncevolution --configure \ enableRefreshSync=TRUE \ funambol Upgrading from releases before 1.2: Old configurations can still be read. But writing, as it happens during a sync, must migrate the configuration first. Releases >= 1.2 automatically migrates configurations. The old configurations will still be available (see "syncevolution --print-configs") but must be renamed manually to use them again under their original names with older SyncEvolution releases. ----------------------------------------- -- 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.