I have been experimenting with several combinations of syncevolution and libsynthesis, and unfortunately I found that syncevolution 0.9.1+ds1-1 currently doesn't work in combination with _any_ libsynthesis version, triggering the bug described at 2) in my first comment: evolution-data- server at 100% of CPU, and nothing happens. The bug had disappeared in some upgrade of evolution-data-server, but later was reintroduced, and now happens _always_. That's why I wasn't able so far to test the specific compatibility of the new libsynthesis with the current syncevolution.
Instead, syncevolution 1.0+ds1~beta2a, which is in sid since 15 days (stopped from migrating to testing only by architectures not supported by Ubuntu and dependencies already present in Lucid) works perfectly in my (massive) tests. Now: 1.0 _does_ introduce new features - namely, the ability of syncing without a third-party server - but I think it is still by far the best way to solve the current problem. Obviously, it _may_ be that at some point before the release of Lucid I upgrade evolution-data-server again and everything works again... but I have no clue on that. That said: assuming that the request to sync 1.0+ds1~beta2a is _not_ accepted, and assuming that the 100% CPU bug is somehow solved, the upstream developers (who don't use lucid and _don't see_ the 100% CPU bug) have said that the current syncevolution and libsynthesis are _probably_ compatible apart from one particular problem - in brief, after one applies the patch at http://lists.syncevolution.org/pipermail/syncevolution/attachments/20100309/11670673/attachment.bin -- Sync libsynthesis 3.2.0.35+ds2-2 from debian sid https://bugs.launchpad.net/bugs/528326 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
