Re: [SyncEvolution] syncevolution and a radicale caldev server
On Thu, 2012-02-16 at 19:54 +0800, William Kenworthy wrote:
Thanks Patrick its now working in a usable fashion. I actually have
8
addressbooks for things like family members, work etc. (had! - lost the
lot when experimenting, my fault :(
If you lost that while experimenting with SyncEvolution, then check your
session directories (~/.cache/syncevolution, output of "syncevolution
--print-sessions"). There are automatic backups before and after each
sync. Can be restored manually or via "syncevolution --restore".
I do have to use "--sync refresh-from-client" as any kind
of two way
sync including slow fails with 401 and 409 errors. The radicale log
shows that if I try and send any changed data from the n900 to radicale,
it fails as the path is not attached: a good transaction includes
something like "/zzz/Dan/1291.ics" while one that fails has
syncevolution passing "/1291.ics" to radicale which fails the auth
checks (gets mapped to user noboddy)
This sounds like an issue that came up before (not fixed in the code
yet): do you have a "database" URL that doesn't end in a slash? That
leads to the leading / in the requests which fail.
That is what I meant with the comment in the instructions:
# Configure @radicale context so that provides access to both
# calendars; repeat if you have more than two.
# Mind the trailing slash in the database URL, it is required in > 1.2.x!
--
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.