On Di, 2010-10-26 at 09:37 +0100, Chris G wrote:
On Mon, Oct 25, 2010 at 08:53:54PM +0200, Patrick Ohly wrote:
> On Mo, 2010-10-25 at 17:27 +0100, Ole Wolf wrote:
> > 2. Inspired by the instructions at:
> >
http://wiki.scheduleworld.com/wiki/Linux_KDE_4_Configuration, I changed type
> > and evolutionsource to:
> >
> > type = file:text/vcard:3.0
> > evolutionsource = /home/wolf/Contacts
> >
> > where /home/wolf/Contacts is an existing (and currently empty) directory.
> >
> > Unfortunately, executing: "syncevolution google"
> >
> > yields an error, complaining that: "First ERROR encountered: addressbook:
: No
> > such file or directory"
>
> How exactly did you make that change? I'm asking because "type" is a
> property which appears in multiple files (for various, mostly historic
> reasons) and sometimes people edit it on the wrong config.ini.
>
> The safe way to make config changes is via the command line:
>
> # verify config
> syncevolution --print-config google
> # change type
> syncevolution --configure \
> --source-property type=file:text/vcard:3.0 \
> --source-property evolutionsource=/home/wolf/Contacts \
> google addressbook
>
This doesn't really seem to work for me:-
chris$ syncevolution
Evolution Address Book = Evolution Contacts = evolution-contacts:
Personal (file:///home/chris/.evolution/addressbook/local/system) <default>
Evolution Calendar = evolution-calendar:
Personal (file:///home/chris/.evolution/calendar/local/system) <default>
Birthdays & Anniversaries (contacts:///)
Evolution Task List = Evolution Tasks = evolution-tasks:
Personal (file:///home/chris/.evolution/tasks/local/system) <default>
Evolution Memos = evolution-memos:
Personal (file:///home/chris/.evolution/memos/local/system) <default>
So then I try:-
chris$ syncevolution --print-config evolution-contacts
"evolution-contacts" is not the name of a configuration, which is needed
in most command line invocations. I thought you had named your config
"google", which is why I suggested "syncevolution --print-config
google"
above.
--
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.