On Thu, 2012-10-25 at 18:19 +0200, Sebastian Heinlein wrote:
> Am Donnerstag, den 25.10.2012, 17:50 +0200 schrieb Patrick Ohly:
> > On Thu, 2012-10-25 at 17:30 +0200, Sebastian Heinlein wrote:
> > > But I get another problem: syncevolution complains about missing rights
> > > to sync my addressbook.
> > This is a side effect of the earlier failed sync. Please try
> > "--refresh-from-remote/local/slow webdav@dpool addressbook".
> > Use -remote when the CardDAV side has all your data, -local when the
> > local side is up-to-date, -slow if both have changes.
> I did a "syncevolution --sync slow webdav@dpool". It didn't report any
> problems but deleted my whole calendar and the todos on the local side.
> The items still exist on the server :/
I'd like to have a look at the sync logs of that session. You'll find it
via "syncevolution --print-sessions webdav@dpool" and "syncevolution
Can you send me the syncevolution-log.html files?
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.
I finally got SyncEvolution 18.104.22.168 as part of the bunch of updates
which Linux Mint Debian (XFCE, in my case) has undergone recently.
The syncing (with a Funambol server) works well if I start it manually,
though I haven't applied the release notes for 1.3.x (not sure they were
relevant for 1.2.99).
But automatic syncing seems somehow broken: it never happens. Yet, the
syncevo-dbus-server does start, but remains idle: even stranger.
Before the updates, I used to start it by adding it to
System > Session and startup
When I noticed that it no longer worked, I tried and put
an /etc/xdg/autostart/syncevo-dbus-server.desktop file, pointing
But it didn't help; the result was the same.
TIA for any help - best regards,
I've taken a peek at Google's API for tasks synchronization, which is
https://developers.google.com/google-apps/tasks/v1/reference/ (at the
bottom of the page). The methods are used via REST which is quite easy
using libcurl if my experience in writing an REST interface for an
Amazon service is any indication.
Unless I'm missing something, this would indicate that it would be
relatively straight-forward to write a Google Tasks backend backend for
SyncEvolution, although I suspect the Google authentication procedure
might pose some problems for a non-web interface.
Has anyone taken a crack at that?
Otherwise, where do I find documentation on how to write a backend that
fits snugly into the SyncEvolution code?
Rødhættevej 4 • 9400 Nørresundby
Telefon: 9632-0108 • Mobil: 2467-5526 • Skype: ole.wolf
I've a simple "BACKUP" configuration (one of them):
$ syncevolution --configure syncURL= username=$email
backend=eas-contacts dumpData=0 printChanges=0 target-config@google-eas
$ syncevolution --configure --template SyncEvolution_Client
syncURL=local://@google-eas username= sync=one-way-from-server
I thought that `sync=one-way-from-server` guarantee that the remote
would keep untouched...
1st time it was true: contacts were pulled to local files. Great.
2nd time after reboot and /tmp/Google_Contacts_backup_eas cleaned up I
got most (131 of 135) of my contacts deleted. Sucks.
The root reason for that must be the sync=two-way in target-config. Or
maybe evolution-activesync misbehaved, I don't know.
I'm lucky Google has a tiny time-machine behind the "Restore contacts"
Ildar Mulyukov, free SW designer/programmer
ALT Linux Sisyphus
I am currently running Syncevolution 1.2.2-1 (to a Funambol account)
under Linux Mint Debian, a "semi-rolling" distribution. A load of
updates have been released recently as an "update pack" (1300+ packages!
Among them is Syncevolution 22.214.171.124-1.
I am cautious with such a huge update and I tested it on a "draft"
install. When I launched the new Syncevolution, it complained about a
problem during the last sync -- it was not the case!
So I did not do the slow sync that was offered, and stopped there. When
restarting my main system, the syncing resumed flawlessly.
So, is there any steps I should take before updating? Should I go ahead
with the slow sync, or rather not transfer the Syncevolution settings
and re-create them from scratch?
TIA for your advice - best regards,