On Sun, 2011-10-16 at 23:11 +0200, [email protected] wrote: > Am 2011-10-16 21:36, schrieb Patrick Ohly: > > On Sun, 2011-10-16 at 14:11 +0200, [email protected] wrote: > >> Hello, > >> > >> I use syncevolution to sync my local evolution client to a funambol > >> server. This worked fine until today. > >> > >> I've added a new calendar of type CalDAV to evolution. When I run > >> syncevolution now it tells me: "Synchronization failed" and "calendar: > >> opening calendar: Authentication required". > >> > >> I understand that it's not possible to sync this new calendar without > >> authentication but I don't know how to set things up: > >> > >> Either I could disable the respective calendar: how can I do that? > > > > You want to continue syncing your traditional, local calendar, right? > > yes of course. > > > > > In that case set "evolutionsource" (in SyncEvolution< 1.2) or > > "database" (in SyncEvolution 1.2 or one of its prereleases) to the name > > of the local calendar. See "syncevolution" (without parameters) for > > database names/uris. > > > > I guess this will bite more people with CalDAV calendars. Should > > SyncEvolution prefer local calendars when trying to determine the > > default calendar? > > Actually I set the local calendar as default in evolution. Nevertheless > syncevolution listed the CalDAV calendar as default.
This "Evolution default calendar" must be an Evolution-internal setting. I don't think it is exposed to apps like SyncEvolution via the EDS API. > >> Or i could supply username/password to syncevoltion: how to do that? > > > > "evolutionuser/password" or (in latest version) "databaseuser/password". > > > > I'm sorry but I would need an example on how to do this. I think it's > something like: > > syncevolution --configure ... > > But the exact usage of syncevolution's parameters and options is not > quite clear to me. (Setting it up once was sufficient so I didn't care > too much ;-) > > The same goes for the question on how to omit the CalDAV calendar from > the sync process. > > So examples or hints to adequate documentation would be very appreciated! How about "man syncevolution", online at http://syncevolution.org/documentation/syncevolution-usage ? The question is meant seriously. If that isn't written well enough, how could it be improved? There is no explicit example for setting "database", but there is one for setting "sync": syncevolution --configure \ sync=two-way \ memotoo@other addressbook Substitute "sync" with "database", "two-way" with your database name and replace the config/source name with the ones matching your existing config and you are done. -- 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
