Bug#599247: Syncing with horde3 - always only slow-sync possible
Hi! I have tested the default syncevolution shipped by Squeeze. Til now no more problems. I think, you can mark the bug as solved. Thomas Am Sonntag, den 12.12.2010, 15:58 +0100 schrieb Patrick Ohly: On So, 2010-12-12 at 14:02 +, Thomas Maass wrote: Sorry, I forgot: I checked out from http://www.synthesis.ch/indefero/index.php/p/libsynthesis/ Which branch did you use? Lukas has pushed several changes to his luz branch which are not yet used in the libsynthesis bundled with SyncEvolution. I decided against switching to the very latest version because that version introduced a backwards-incompatible change of on-disk files. Once you upgrade, you cannot go back. I wanted to combine that change with another such change in SyncEvolution itself, probably in 1.2 or 1.3. If you can pin the solution to a specific change in libsynthesis, then I would back-port it to the version of libsynthesis in SyncEvolution 1.1.x. I looked through the changes, but saw nothing relevant. -- GPG-ID: D31AAEEA http://www.setho.org/people signature.asc Description: This is a digitally signed message part
Bug#599247: Syncing with horde3 - always only slow-sync possible
On So, 2010-12-12 at 14:02 +, Thomas Maass wrote: Sorry, I forgot: I checked out from http://www.synthesis.ch/indefero/index.php/p/libsynthesis/ Which branch did you use? Lukas has pushed several changes to his luz branch which are not yet used in the libsynthesis bundled with SyncEvolution. I decided against switching to the very latest version because that version introduced a backwards-incompatible change of on-disk files. Once you upgrade, you cannot go back. I wanted to combine that change with another such change in SyncEvolution itself, probably in 1.2 or 1.3. If you can pin the solution to a specific change in libsynthesis, then I would back-port it to the version of libsynthesis in SyncEvolution 1.1.x. I looked through the changes, but saw nothing relevant. -- 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
