Re: [SyncEvolution] syncevolution and a radicale caldev server
On Tue, 2012-02-14 at 09:56 +0800, William Kenworthy wrote:
My initial script now does not create an error, but an attempt at
sync
generates a host lookup error (on both the desktop and the n900) so I
am missing something else ...
The user docs dont show using a syncURL in the caldav example but it
looks like it must have one, or is there another property that should
be used?
wdk@moriah ~ $ SYNCEVOLUTION_DEBUG=1 syncevolution --daemon=no
loglevel=4 --print-items @Test calendar
HTTP session to ://:0 begins.
[DEBUG 00:00:00] Tue 2012-02-14 01:25:13 UTC = 09:25 +0800 WST
[DEBUG 00:00:00] calendar: slow sync or testing, do full item scan to
detect changes
[DEBUG 00:00:00] starting REPORT 'meta data', credentials unverified,
deadline in 300.0s
ah_create, for WWW-Authenticate
Running pre_send hooks
[DEBUG 00:00:00] forced sending credentials
Sending request headers:
REPORT Test HTTP/1.1
Keep-Alive:
Connection: TE, Keep-Alive
TE: trailers
Host: :0
Content-Length: 305
Depth: 1
Content-Type: application/xml; charset="utf-8"
Authorization: xxxxxxxxxx
Sending request-line and headers:
Doing DNS lookup on ...
[DEBUG 00:00:00] REPORT 'meta data': Neon error code 2, no HTTP
status: Could not resolve hostname `': Host not found, might retry
^^^
That's an empty hostname. The reason is the use of @Test instead of
target-config@Test: the syncURL is defined in the "target-config" peer
config inside the @Test context, not in @Test itself.
You are running into an inconsistency in SyncEvolution here: in the
local:// syncURL, the "target-config" part is implicit, while on the
command line it has to be specified explicitly.
The command line usage is right and should stay as it is, because there
are valid cases when no peer needs to be selected in --print-items
("--print-items @default addressbook", for example).
Would it help to allow syncURL=local://target-config@Test and use that
in the documentation?
Right now, that triggers an error about "invalid local sync URL:
'target-config@Test' references a peer config, should point to a context
like @Test instead".
That error is meant to catch invalid settings like
syncURL=local://foobar.
--
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.