On Mo, 2011-04-11 at 22:06 +0100, Frederik Elwert wrote: I started some similar investigations with a Fritz!Box. The problem was that that router/phone system doesn't even have locally unique IDs for each contact, therefore change tracking is a bit difficult. I never wrote any code for SyncEvolution, but it gave me some ideas. Not that I have a lack of those... ;-) It's implemented in 1.1.99.3. Here are some untested instructions: Configure the file backend which will store the vCards: dir=<absolute path to vcard dir> mkdir -p $dir syncevolution --configure \ backend=file \ database=file://$dir \ databaseFormat=text/x-vcard \ @gigaset addressbook Configure one-way synchronization from default system address book: syncevolution --configure \ syncURL=local://@gigaset \ peerIsClient=1 \ sync=one-way-from-server \ gigaset addressbook Run a sync: syncevolution gigaset Yes, that runs into issues with syncevo-dbus-server having to host two sessions at the same time, which isn't supported. Local sync avoids that limitation and doesn't depend on syncevo-http-server. -- 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.

On Di, 2011-04-12 at 13:37 +0200, Patrick Ohly wrote: Frederik tried it and found some issues: 1. uri had to be set in "gigaset" addressbook. Fixed in current code such that the source name is used as fallback. 2. Errors were not propagated, making debugging a bit harder. Fixed. 3. A "source-config" peer in the "@gigaset" was required for local sync. This requirement was originally introduced for CalDAV/CardDAV because they need the syncURL for the web server, but even there username/password from the main config can be enough. So now "source-config" can be created (to set a different loglevel, for example) but doesn't have to be. 4. A password issue prevented running in syncevo-dbus-server. I wasn't able to reproduce the last issue. After fixing the first three points, synchronization succeeded for me. Frederik, I'll tag and compile 1.1.99.4 now. Let's retest with that. Oh, and here's a much simpler way of achieving what you want to do ;-) Sorry, should have thought of that earlier: rm -rf $dir mkdir $dir syncevolution --export $dir @default addressbook In contrast to true file syncing, it is limited to a full dump on each call. I still appreciate that you brought up and tried local syncing! -- 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.

Thanks for the effort and the information! Am Dienstag, den 26.04.2011, 10:20 +0200 schrieb Patrick Ohly: I’d be happy to test them, but currently I get an error with that sources: $ sudo aptitude update Ign http://downloads.syncevolution.org experimental/main Packages Treffer http://downloads.syncevolution.org stable/main Packages Treffer http://downloads.syncevolution.org experimental/main Packages 2B wurden in 2s heruntergeladen (1B/s) Paketlisten werden gelesen... E: Problem parsing dependency Depends E: Ein Fehler trat beim Bearbeiten von syncevolution-evolution auf (NewVersion1) E: Problem with MergeList /var/lib/apt/lists/downloads.syncevolution.org_apt_dists_experimental_main_binary-i386_Packages E: Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet werden. E: Konnte den Paketcache nicht neu erzeugen Anything wrong with the repository? Regards, Frederik

On Di, 2011-04-26 at 17:36 +0100, Patrick Ohly wrote: Repo was updated with a fixed .deb. The new Ubuntu Lucid build chroot didn't have the necessary tools for calculating the dependencies. -- 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.

On Do, 2011-04-28 at 21:16 +0100, Frederik Elwert wrote: Don't say that - it makes your emails drop in my priority list ;-) I can't reproduce that. For me, changes made in the directory (editing files, adding files) are ignored during a sync and never make it back to Evolution, as intended. Such things are possible, but not easily. Basically you would have to: * Define your own, specialized file backend (the existing one is not configurable enough). * Define your own Synthesis vCard profile which does not define PHOTO. Use it instead of the default vCard profile. * Add filtering scripts which only accept contacts on the Evolution side which have at least one TEL. That's probably easier. -- 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.