https://bugs.freedesktop.org/show_bug.cgi?id=56263
--- Comment #1 from Patrick Ohly <[email protected]> --- (In reply to comment #0) > holy cow, that was quite tiresome and utterly frustrating. Four quite > complex commands to eventually be able to connect to the calendar, then > another two to eventually make addressbook work. That's not fun. It would have been possible with two more complex commands (by combining the setup of all sources into one invocation), but I guess that wouldn't have made it easier. I'm open for suggestions how this could be made simpler. There's a mail thread about that here: http://comments.gmane.org/gmane.comp.mobile.syncevolution/3992 > And now it doesn't even work and I feel unable to get more useful > information. > > So here is the problem: > $ syncevolution --daemon=no --print-items target-config@radicale cards1 > 342F8BEA-54AC0772-04A3D2F6%2evcf > $ syncevolution --daemon=no target-config@radicale cards1 You are trying to sync with the "target config". Syncing must be triggered via the "sync" config. In other words, do: syncevolution radicale cards1 The reason why you get no useful error output is that the target config looks like a normal SyncML config to SyncEvolution (syncURL set to http:// with username/password available). As I said in the mail thread, I am not happy with the "target-config" aspect. But the discussion did not reach a conclusion on how it can be avoided. > $ syncevolution --daemon=no --status target-config@radicale cards1 > [DEBUG 00:00:00] Sun 2012-10-21 19:40:43 UTC = 21:40 +0200 CEST > [INFO 00:00:00] addressbook: inactive > [INFO 00:00:00] calendar: inactive > [INFO 00:00:00] calendar1: inactive > [INFO 00:00:00] memo: inactive > [INFO 00:00:00] todo: inactive > [DEBUG 00:00:00] cards1: using full item scan to detect changes > syncevolution: /usr/include/boost/smart_ptr/shared_ptr.hpp:424: T* > boost::shared_ptr<T>::operator->() const [with T = SyncEvo::Neon::Session]: > Assertion `px != 0' failed. > Aborted (core dumped) [...] > While I may just have set SyncEvolution up wrongly (very possible), I do > feel that there s a bug somewhere. The crasher ultimately is. > > Anyway, I expected to make it synchronise the via CardDAV, especially since > the calendar part works. Hmm, I thought I had fixed the "--status" problem: commit 3d299422f929a647d33b5dec91d53d77c369bcb6 Author: Patrick Ohly <[email protected]> Date: Fri Jun 29 08:41:31 2012 +0200 WebDAV: --status for WebDAV source aborted The command line --status operation did not complete when applied to a CalDAV/CardDAV source. Instead it aborted because the operation took a code path where the backend was not fully initialized. Oh, I see: the very first time a source is used it goes through yet another code path. The downside of trying to minimize requests - many special cases :-( -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
_______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
