On Thu, 2013-01-31 at 22:56 +0530, Khurshid Alam wrote:
> Hi,
>
> 1)
>
> I was trying to sync a particular Google calendar (Work) with a
> specific Evolution calendar (Work) with caldav. I am using
> syncevolution 1.3.2 on ubuntu natty.
>
> I did following as described on Radicale wiki:
>
> syncevolution --configure --source-property evolutionsource=Work
> --source-property "type=Evolution Calendar" @default workcal #this
> may not be required.
>
> syncevolution --configure --template webdav
> [email protected] password=***** target-config@gcal
>
> syncevolution --configure
> database=https://www.google.com:443/calendar/dav/GOOGLECALENDARID%
> 40group.calendar.google.com/events/ backend=caldav target-config@gcal
> workcal
>
> syncevolution --configure --template SyncEvolution_Client
> syncURL=local://@gcal username= password= gcal
>
> syncevolution --configure sync=two-way backend=calendar database=Work
> gcal workcal
>
> syncevolution --sync refresh-from-client gcal workcal #for initial
> sync
>
> At this point it syncs, but it took me a whole day to figure out the
> "syncURL" for the specific google calendar.
> I had to replace "@" with "%40" on syncURL to get it work. Without it
> it just doesn't recognise the remote database.
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
This won't affect your data or your configs.
> Is there any easy way to scan for remote google calendars?
>
> I also tried :
> "syncevolution --print-databases \
> backend=caldav \
> [email protected] \
> "password=***********"
> but it didn't return anything. What exactly is it supposed to do?
It starts the CalDAV auto-discovery. The problem is that Google doesn't
support that. They lack the DNS entry that connects gmail.com with their
CalDAV server on www.google.com.
One can scan CalDAV servers without that DNS entry with:
syncevolution --print-databases \
username=... password=... \
syncURL=https://www.google.com
But for Google, that also fails, this time because the server doesn't
know about CalDAV at the root and fails for a PROPFIND with a 503 error.
Scanning https://www.google.com/calendar/dav/ works better, but still
fails, this time because of an XML parser error:
[DEBUG 00:00:01] PROPFIND: Neon error code 1: XML parse error at line 33:
undeclared namespace prefix, must not retry
I think line 33 is this:
<ns1:addressbook-home-set xmlns:ns1="urn:ietf:params:xml:ns:carddav"/>
33=> <ns1:principal-address/>
<ns1:addressbook-description/>
I think Google is sending invalid XML here, because the ns1 namespace
declaration only covers line 32. I've not seen that bug before, probably
it was introduced when Google added CardDAV support.
Hmm, I am *always* getting that error when trying to use Google CalDAV.
Perhaps my libneon is more strict about this than your version. I must
admit that I haven't run the automated regression testing in a while, so
I can't say for sure for how long this has been broken.
I'll try to work around this.
> 2)
> How can I restore events from backup after a sync(caldav)? With Syncml sync I
> can do this
> from gtk-gui. But for caldav/carddav sync it doesn't show any restore point.
Yes, you can do it via the command line. You need to look for sync
sessions involving target-config@gcal and then use those with the
--restore operation.
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?
--
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
