This is a copy of the message I replied to Patrick, with the difference
that the attached log file is not included in this mail, because it is
too big. If anybody is interested in the log file, please let me know
and I'll send it to private mail.
Hello Patrick,
Thanks for your quick response and help. Really appreciated.
>> I'm trying to use syncevolution http server to sync may Android phone
>> (Nexus S) to my Evolution backend. On the Nexus I use the Funambol
>> SyncML client for Android.
>
> Beware that previous attempts to sync with that client failed because of
> SyncML protocol violations in the client. It seemed to be written
> specifically for the Funambol server. It might be better now.
Ok. The version of the Funambol Client I'm using is 10.0.8, which is the
latest one as far as I can tell. I've used a local Funambol server in
the past, and I really don't want to go there again if at all possible,
it's no fun.
>
> 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. 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...
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
jpahka@laptop:~$ syncevo-http-server http://127.0.0.1:9000
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] sync: creating complete data backup after sync (enabled with
dumpData and needed for printChanges)
[INFO] sync:
[INFO] sync: Synchronization failed, see
/home/jpahka/.cache/syncevolution/nexus-2012-02-15-12-52/syncevolution-log.html
for details.
[INFO] sync:
Changes applied during synchronization:
[INFO] sync:
+---------------|-----------------------|-----------------------|-CON-+
[INFO] sync: | | LOCAL |
REMOTE | FLI |
[INFO] sync: | Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL |
ERR | CTS |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | memo | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | todo | 0 | 0 | 0 | 0 | 0 | 0 | 0
| 0 | 0 |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync: | start Wed Feb 15 12:52:58 2012, duration
0:09min |
[INFO] sync: | aborted on behalf of user (local, status
20017) |
[INFO] sync:
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
[INFO] sync:
I've attached the log file to thi mail, compressed.
Is it so, that the Client still doesn't play ball?
br, juhis
On 02/15/2012 12:16 PM, Patrick Ohly wrote:
On Wed, 2012-02-15 at 11:47 +0200, Juha Pahkala wrote:
I'm trying to use syncevolution http server to sync may Android phone
(Nexus S) to my Evolution backend. On the Nexus I use the Funambol
SyncML client for Android.
Beware that previous attempts to sync with that client failed because of
SyncML protocol violations in the client. It seemed to be written
specifically for the Funambol server. It might be better now.
Your problem however is something else.
I'm using Ubuntu 11.10 distribution and I've
compiled version 1.2.2 of syncevolution using configuration:
./configure --prefix=/usr --enable-gui --enable-dbus-service
--disable-ecal --disable-ebook --disable-shared
I've tried following various HOWTO:s to no avail. From the mailing list
archives I've gatherd, that this one:
http://syncevolution.org/wiki/synchronizing-evolution-http-howto
should be the up-to-date one. Is this correct?
No. It's the one "to keep a phone in sync with Evolution". It's based on
the assumption that you are using Evolution Data Server, which you
explicitly disabled.
I know that this can be confusing, so the HOWTO above explicitly says
"Setting up SyncEvolution as such an intermediary on an Internet server
is explained in another HOWTO":
http://syncevolution.org/wiki/http-server-howto
Do you have a suggestion how such a misunderstanding can be avoid in the
future?
Anyhow, when I try to sync my phone, using a minimal config from the
HOWTO, I get the following:
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
The key difference in the HOWTOs is that the configuration you are
quoting here implicitly uses the backend=addressbook, which doesn't work
without the EDS backend. Please have a look at the other HOWTO, it shows
how to set up the file backend instead.
jpahka@laptop:~$
jpahka@laptop:~$ syncevo-http-server http://127.0.0.1:9000
[INFO] syncevo-http: new SyncML session for 192.168.10.52
[INFO] sync: matched deviceID fac-355031040909281 against config nexus
(/home/jpahka/.config/syncevolution/default/peers/nexus)
[INFO] sync: todo: inactive
[INFO] sync: memo: inactive
[INFO] sync: addressbook: inactive
[INFO] sync: calendar: inactive
[...]
And indeed, there seems to be no sources active in the configuration.
I think that's a side effect of not having a functional backend for
these sources. They are not activated unless that check succeeds.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
