On Tue, 2010-05-04 at 22:14 +0100, Frederik Elwert wrote: > Am Dienstag, den 04.05.2010, 19:46 +0200 schrieb Patrick Ohly: > > On which distro does the problem occur? You mentioned two different > > Ubuntu releases. Which Evolution version do you use on the affected > > platform? > > > > I'm asking because it works for me here (Debian Testing with > > self-compiled Evolution 2.28.x). > > I upgraded both machines to Ubuntu Lucid with Evolution 2.28.3. > > $ syncevolution --version > SyncEvolution 1.0beta2a > using libedataserver-1.2.so.11 > using libebook-1.2.so.9 > using libecal-1.2.so.7 > using libecal-1.2.so.7 > using libbluetooth.so.3 > > On the other machine (which originally sent the items to Scheduleworld), > I’m still using SyncEvolution 0.9.x. Could that cause the trouble?
No, the problem is on the receiving end. I have added more debug logging to the code. Would you mind trying out 1.0beta3+20100505+SE+913db88+SYSYNC+0328b9e from http://downloads.syncevolution.org/tmp/ ? I'll need a log file again which contains such an event being sent by the server. Editing it on ScheduleWorld before the sync should do the trick. The amd64 version is available, i386 is still being compiled. I'll upload it later. -- 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
