On Tue, 2012-02-14 at 08:27 +0100, Patrick Ohly wrote:
> 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
...
> ^^^
> 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.
>
>
Now partly working! I deleted the contents of .config/syncevolution/
and got a different error. I then re-edited the file with the config
lines to remove tabs and just leave spaces and also deleted the database
entry as its in the config files ... and its now working. Its possible
that all the cutting and pasting from web pages and documents allowed
some non-printing characters in somewhere - perhaps config file
sanitation needs improving?
But I have 4 calendars on the radical server and the config below placed
them all in the one n900 set as default - is it possible to get them
into the proper calendar on the n900? Replacing the word "Test" with
another Calendar name such as "Bill" doesnt work - still went to
default. The database entry in the config files suggests it should have
worked :( I have seen this commented on in other posts but the fix
(copying/deleting files was for an older revision of syncevolution and
it didnt seem to apply here.)
For the documentation I suggest examples tagged (comment) with the
version of syncevolution they apply to. Much of my initial confusion
stemmed from seeing examples on the web that people are supposedly using
that didn't work for me. I think the best approach would be to extend
you have done with the google examples - complete, working examples. My
final one here could be suggested for "Radicale"
Lastly there is the problem with tabs and spaces in the config file - I
am not sure if this is real and a bug or not. I have also noticed that
the config files created by syncevolution for "Test" are
in .config/syncevolution/test (lower case "T") - another source of
confusion for me.
Whats working (!):
#!/bin/sh -x
syncevolution --configure \
--template webdav \
username=zzz \
password=zz \
syncURL="http://moriah.lan.localdomain:5232/zzz/Test/"; \
target-config@Test
syncevolution --configure \
--template SyncEvolution_Client \
syncURL=local://@Test \
username= \
password= \
Test \
calendar
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
