Re: [SyncEvolution] one-way-sync not respected

I realize I didn't explain myself properly: Google requires authentication for accessing the caldav api. On public calendars, any authentication credentials are accepted for reading public calendars. Trying to write on remote without ownership of the calendar produces the 403 error. Why does syncevolution try to access writing functions, if one-way sync was selected? Log attached. syncevolution was called with $>syncevolution --sync local-cache-incremental feriados 2013/7/22 Patrick Ohly <patrick.ohly(a)intel.com&gt;: > On Mon, 2013-07-22 at 00:15 -0300, Juan Antonio Zuloaga Mellino wrote: >> Found this when I tried to sync google public calendars with >> syncevolution (as an ics subscription replacement). >> >> It seems that google still requires authentication even for accessing >> public calendars. ie: >> https://www.google.com/calendar/dav/vi6voh10oa187gg9nvs8pkqt7s@group.cale... >> >> Even with one-way-from-remote it exits with 403 (Auth required). The >> synchronization is successful. >> >> If required, I could attach the log. > > I'm not exactly sure what the problem is. If Google requires > authentication, then there is little that SyncEvolution can do about > that, can't it? > > Or is the problem that reading the data fails, and then it skips over > that error and doesn't report a sync failure? In that case a log would > indeed be useful. > > -- > 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. > >