Achim Zirner
2011-01-03 10:21:46 UTC
Hi List,
Here's my setup:
Ubuntu 10.10
Windows Mobile 6.1 prof.
Using Repository LP-PPA-opensync-0.22/maverick
I spent the weekend fiddling with my setup. After deleting everything
synce and opensync related (including partnership on my smartphone which
by the way deleted all data synced using it such as contacts and
events!) I installed everything according to the wiki. I seems that I
didn't have to apply the path to "pyopensync-1.py" because it already
looked patched. (Also, trying to apply the patched failed, so I assume
that it was not necessary). I set up a partnership and the initial sync
worked, sort of: I was missing a number contacts. As far they all
started with "Z".
After this sync, the following syncs fails with:
The sync failed: Unable to read from one of the members
DEBUG:SynCE:finalize() called
All conflicts have been reported
Error while synchronizing: Unable to read from one of the members
I am guessing, that the evo2-plugin that is failing.
Any ideas what I can do? Or do we just have wait until opensync 0.40
becomes stable and available?
best wishes for the new year,
achim
Here's my setup:
Ubuntu 10.10
Windows Mobile 6.1 prof.
Using Repository LP-PPA-opensync-0.22/maverick
I spent the weekend fiddling with my setup. After deleting everything
synce and opensync related (including partnership on my smartphone which
by the way deleted all data synced using it such as contacts and
events!) I installed everything according to the wiki. I seems that I
didn't have to apply the path to "pyopensync-1.py" because it already
looked patched. (Also, trying to apply the patched failed, so I assume
that it was not necessary). I set up a partnership and the initial sync
worked, sort of: I was missing a number contacts. As far they all
started with "Z".
After this sync, the following syncs fails with:
The sync failed: Unable to read from one of the members
DEBUG:SynCE:finalize() called
All conflicts have been reported
Error while synchronizing: Unable to read from one of the members
I am guessing, that the evo2-plugin that is failing.
Any ideas what I can do? Or do we just have wait until opensync 0.40
becomes stable and available?
best wishes for the new year,
achim