On Tue, 2014-10-07 at 15:51 -0700, Todd Wilson wrote: > >> > Anyway, removing it in the "google" config should allow you to run syncs > >> > again: syncevolution --configure username= google > >> > >> Yes, authentication is successful now, but I'm still having some > >> problems with the sync. Perhaps we'll have to go into details off-list > >> about the contents of the events, > > > > That would be good. A target-config@google log file at loglevel=4 would > > be useful. > > Coming soon by private email.
I've looked at the logs and it seems that it affects only meetings. I could reproduce the problem. IMHO it is a problem in the Google Calendar server: once a meeting got created, the server remembers it forever. A DELETE via CalDAV merely removes the event from the user's calendar. Then later the PUT fails because it conflicts with the copy that Google still has somewhere. I've opened a StackOverflow entry for this: http://stackoverflow.com/questions/26253250/google-caldav-recreate-meeting -- 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. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
