On Sat, 2013-02-02 at 15:08 +0530, Khurshid Alam wrote: > HI, > > Thanks for quick reply. > > Some bugs related to path normalization were fixed quite a while ago. > > Perhaps I missed something. Can you send me the output of > > > > SYNCEVOLUTION_DEBUG=1 syncevolution --print-items --daemon=no \ > > loglevel=4 \ > > [email protected] \ > > password=***** \ > > > > database=https://www.google.com:443/calendar/dav/[email protected]/events/ > > \ > > backend=caldav > > > Here is the log. http://paste.ubuntu.com/1600382/ > > "https://www.google.com/calendar/dav/[email protected]/"-This > url(without any modification) js still working fine with syncevolution 1.2 > for "Google_Calendar" template. > But now, after upgrade to 1.3, calendar backend fails with it or without it. > Here is the output: > > $ SYNCEVOLUTION_DEBUG=1 syncevolution --configure --daemon=no --template \ > Google_Calendar [email protected] password=******* > target-config@gcal2 > > [DEBUG 00:00:00] Sat 2013-02-02 07:45:05 UTC = 13:15 +0530 IST > [INFO 00:00:00] calendar: looking for databases... > [DEBUG 00:00:00] calendar: timout 300s, retry 5s => resending allowed > [DEBUG 00:00:00] client cert is missing > [DEBUG 00:00:00] testing /calendar/dav/myusername%40gmail.com/user/ > [DEBUG 00:00:00] debugging: read all WebDAV properties of > /calendar/dav/myusername%40gmail.com/user/ > [DEBUG 00:00:00] starting PROPFIND, credentials unverified, no deadline > [DEBUG 00:00:02] retry request with credentials > [DEBUG 00:00:03] credentials accepted > [DEBUG 00:00:03] read relevant properties of > /calendar/dav/myusername%40gmail.com/user/ > [DEBUG 00:00:03] starting PROPFIND, credentials okay, deadline in 296.7s > [DEBUG 00:00:03] forced sending credentials > [DEBUG 00:00:05] PROPFIND: Neon error code 1: XML parse error at line 55: > undeclared namespace prefix, must not retry > [DEBUG 00:00:05] TransportStatusException: PROPFIND: Neon error code 1: XML > parse error at line 55: undeclared namespace prefix > [INFO 00:00:05] calendar: backend failed > -----------------------------------------------------------------------
That's the same thing that I ran into. Google changed something since December 12th last year (I have a nightly test log which shows a different, correct server response) or later (I don't have newer logs). The reason why it breaks 1.3 and not 1.2 is that it is related to CardDAV support, which was added in 1.3. I have a workaround, but want to wait with doing another release to give Google a chance to responds to my email about the problem and perhaps fix it on the server side. With the workaround, 1.3 works with both @ and %40 in the URL. Did you have the problem with @ in the 1.2 version? Then it's probably already fixed. > > You are raising several good points which should be documented > > somewhere. What is the place where you would have found it? README or > > Wiki, general WebDAV Howto or specific Google entry? > > I have been using syncevolution for quite some time now. I used to sync my > Nokia N9 with it. > I took the idea from old meamo > forum(http://talk.maemo.org/showthread.php?t=75810) for multiple google > calendar sync. > Fortunately, I still have a old laptop running syncevolution 1.2.When I was > about to give up on "syncurl" thing, > I found it out by looking at > ~/.config/syncevolution/<config>/sources/<source>/config.ini & then > used it directly with "webdav" template. It worked. > > But, Yes, it would be great if these are documented on syncevolution wiki. Okay. I'll probably add a dedicated "Google" page. -- 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] http://lists.syncevolution.org/listinfo/syncevolution
