On Wed, Oct 8, 2014 at 2:20 AM, Patrick Ohly <[email protected]> wrote: > > > >> 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
Thanks for troubleshooting the problem, which makes sense. In the calendar from which these events are coming (Zimbra), they have a status that is different from other events: because they are organized by someone else, I can't modify them unless I first make a local copy and then modify the copy. Perhaps the logic on Google's server is attempting to keep the same distinction. I'll follow your StackOverflow question and see what they come up with. --Todd
_______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
