On Mo, 2011-07-25 at 11:47 -0400, Ross Vandegrift wrote: > On Mon, 2011-07-25 at 07:37 +0200, Tino Keitel wrote: > > Thanks. This looks more evolution related than bluetooth related. Did you > > try other sync methods on that computer, like HTTP(S)? Did you explicitly > > set the calendar name in your syncevolution config? If not, did you set a > > default calendar in evolution? > > On Mon, 2011-07-25 at 11:53 +0200, Patrick Ohly wrote: > > Which Evolution calendar is this? > > > > Run "syncevolution" (without parameters) and it'll tell you what it uses > > by default. > > Aha - that's the key difference. My desktop default calendar is set to > a CalDAV calendar. My laptop is still set to the local copy. > > I'm guessing (based on the thread about caldav/syncml) that issues here > are expected?
Accessing a CalDAV calendar via Evolution Data Server as you do on the desktop is not tested in SyncEvolution. The other thread was about using SyncEvolution's own CalDAV backend in the context of SyncML. You can get around the error that you experienced by setting the databaseUsername/Password properties for the "calendar" source. Whether it works is a different question. As I said, untested, your mileage may vary. The reason for writing a CalDAV backend in SyncEvolution instead of using/improving the CalDAV backend in Evolution were manifold. The main motivation was to support full offline operations on the calendar data (not supported by Evolution) and efficient syncing (the EDS API is more limited than CalDAV). -- 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
