On Sat, 2012-05-19 at 20:44 +0200, Tom Kazimiers wrote:
> Hi all,
>
> I try to have two different databases in sync: abook [1] and a SyncML
> server. Abook is a small address book program that integrates well with
> the mail client mutt. It is able to export and import its data in
> various formats, amongst them VCard. Since syncevolution is able to
> handle this, it seems to be the perfect tool for the job. Using abook's
> VCard export/import functionality, it will create/read one VCard file
> for its whole data base. This can be split into single files for the
> use with syncevolution.
>
> I hope the actual syncing will work like this: export current abook
> data to VCard, split it into one file per item, use this as the file
> backend data for syncevolution, sync, combine single updated VCard files
> into single files and import them back into abook.
Do you aim for two-way synchronization? In that case you'll have to be
more careful when exporting from abook (don't rewrite files
unnecessarily, to avoid turning every sync into a "refresh from abook")
and when importing into abook (don't overwrite data which is more
recent; can be done by always syncing abook->file->SyncML->file->abook,
as you said).
> However, after a lot of reading and fiddling with syncevolution I
> couldn't manage to get it to work. I would appreciate it very much if
> you could show me the right direction. This is what I did:
>
> I added a peer (I think) for the SyncML server which seems to
> synchronize fine, called funambol@default. Then I added another
> context (that's what I think it is) for the local VCard file backend:
>
> syncevolution --configure backend=file \
> database=/home/tom/tmp/sync/vcard-dir \
> databaseformat=text/vcard @local addressbook
>
> Based on this I created another peer, local@default:
>
> syncevolution --configure syncURL=local://@local \
> peerIsClient=1 sync=two-way local addressbook
What you seem to be trying here is the configuration of a local sync
config between @default addressbook(= usually EDS) and @local
addressbook (= file). This should work, but is unnecessarily complex -
see below for a simpler way.
> Now it seems I can update my local VCard data with the help of these
> two commands:
>
> syncevolution funambol@default
> syncevolution local@default
>
> With this I am able to update the VCard folder (here:
> /home/tom/tmp/sync/vcard-dir). But I don't seem to be able to get changes
> from the VCard files back to the SyncML server. All the changes I make to
> the VCard files are not recognized by syncevolution (I try to sync with
> the last two commands as well).
What changes do you make to the vCard files? It should be possible to
modify them (which must touch the last modified time stamp), add new
files (file name doesn't matter) and delete some.
It will be easier to test this when syncing Funambol directly against
your @local file source:
syncevolution --configure \
--template funambol \
funambol@local \
addressbook
Strictly speaking, the "--template" parameter is redundant because
SyncEvolution would guess the right template based on the config name.
Now you can synchronize with "syncevolution funambol@local" and check
for changes with "syncevolution --status funambol@local". The latter
command will tell you which changes in the file address book
SyncEvolution sees, without changing anything.
> Based on this I have two questions:
>
> 1. Does my approach make sense at all?
> 2. Why isn't my modified VCard data synced back?
It should be possible to do this, either as you planned or directly. I'm
not sure yet why it fails.
--
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.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
