On Wed, 2012-02-15 at 14:17 +0200, Juha Pahkala wrote:
> > Do you have a suggestion how such a misunderstanding can be avoid in the
> > future?
> >
>
> Well, not really. Reading only the two wiki pages, it's relatively
> clear what they mean.
It might be worth mentioning in the "prerequisites" part which features
the SyncEvolution binary has to support.
BTW, why did you decide to compile your own binaries instead of using
the apt repos? Those should work on your Ubuntu installation.
> I guess I got confused with all the different HOWTOS I was reading.
> The thing I'm after is just syncing my phon with a local EDS. What I
> did is, I compiled syncevolution again with the following configure:
>
> ./configure --prefix=/usr --enable-gui --enable-dbus-service
>
> And after that did as below, and now perhaps hitting the problems you
> mentioned earlier...
No, there's still a configuration problem.
The server log shows that the phone is trying to sync against "card",
which is not a know source on the server.
[2012-02-15 12:56:09.545] - Processing Alert Item (code=200),
Source='contacts', Target='card'
[2012-02-15 12:56:09.545] Determined relative, identifying URI (w/o CGI): card
–
[2012-02-15 12:56:09.545] 'issue' - issuing command,
Cmd=Status [--][++] [->end] [->enclosing]
* [2012-02-15 12:56:09.545] Command 'Status': is 0-th counted cmd,
cmdsize(+tags needed to end msg)=179, available=64809
(maxfree=295267, freeaftersend=295088,
notUsableBufferBytes()=230458)
* [2012-02-15 12:56:09.545] WARNING: Non-OK Status 404 returned to
remote!
You can add "card" as an alias for "addressbook".
> jpahka@laptop:~$ rm -fr .config/syncevolution
> jpahka@laptop:~$ syncevolution --configure --template
> SyncEvolution_Client \
> > --sync-property remoteDeviceId=fac-355031040909281 \
> > --sync-property username= \
> > --sync-property password= \
> > --source-property addressbook/uri=contacts \
> > nexus
Use "card" instead of "contacts " above, or update your existing config:
syncevolution --configure uri=card nexus addressbook
--
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
