August 2012 - syncevolution@synevolution.org

Re: [SyncEvolution] syncevolution and a radicale caldev server

by Patrick Ohly

On Fri, 2012-02-17 at 15:14 +0100, Gregor Horvath wrote: > Am Fri, 17 Feb 2012 11:12:52 +0100 > schrieb Patrick Ohly <patrick.ohly(a)intel.com>: > > > On Tue, 2012-02-14 at 15:57 +0100, Patrick Ohly wrote: > > > But as Radicale is an example where multiple databases are possible > > > (in > > > contrast to Google), it's worth spelling out explicitly how such a > > > config can be created: > > > > [...] > > > > William, did this work? > > > > Perhaps you (or someone else) has the time to turn the instructions > > into a proper HOWTO? I created a place holder Wiki page for it here: > > http://syncevolution.org/wiki/synchronizing-radicale > > > > William sent me some debug logs, but then ran out of time. So I've installed Radicale myself and found an issue that'll break SyncEvolution: items reported by the server include double slashes in the path. <multistatus xmlns="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"> <response> <href>/public_user/calendar/calendar_1//1234567890(a)dummy.ics</href> ^^ SyncEvolution will then use /1234567890(a)dummy.ics as path in future requests, which Radicale rejects with either 404 or 401 errors. I'll work around that in SyncEvolution. I'm not sure whether there is a solution with 1.2.2. Have you considered Calypso (http://keithp.com/blogs/calypso/)? I don't know yet whether it works with SyncEvolution; if there is interest, then I will try it. > I am trying to do the same thing (with one calender to start with) > N900 <-> radicale but it did not work, because it seems the Maemo > calendar is not found: > > http://pastebin.com/huMXDsEx > > What I am doing wrong? You have additional spaces after your \ character. The slash must be at the end of each line. -- 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.

6 years

2
5
0 / 0

[SyncEvolution] PBAP status + next steps

by Patrick Ohly

Hello! I've picked up work on the PBAP backend [1] again. The "pbap" branch can be merged with current master without problems and works as it did before with obexd < 0.47 (see the src/backends/pbap/README): * "refresh-from-remote" works. * The entire phone address book, including PHOTOs, is downloaded in each sync. There are several todos for the code: 1. Adapt to obexd >= 0.47 and the new D-Bus API in it; the current code no longer works. 2. Support incremental sync - somehow. 3. Remove overhead for syncing: don't write anything to disc if nothing changed. 4. First copy contacts without PHOTO data, then add PHOTO data. I'd like to tackle points 2 and 3 first. For incremental syncing, there are three options: A. The PBAP source could create a key for each contact based on some property (currently done based on N) and a revision string by hashing the vcard content (not done at the moment). Change tracking would be done by the TrackingSyncSource. The downside of this is that the TrackingSyncSource will get confused when sending contacts sometimes with and sometimes without PHOTO data. B. Assemble a custom sync source which does its own change tracking instead of relying on TrackingSyncSource, and use hashing to detect changes. C. Don't try to do change detection in the source at all. Instead do a slow sync that doesn't write to the phone, let the Synthesis engine do its normal matching in the first cycle (without PHOTOs), remove local contacts which were not matched, then do a second cycle to add PHOTO data. These options are not mutually exclusive. Option C is needed if syncing failed, because without it, a "refresh-from-remote" would be needed to recover. Such a "refresh-from-remote" would wipe out all local data, even those contacts which were not changed, which is undesirable (want to reduce disk writes). A normal slow sync would leave deleted contacts around. Therefore I'll investigate that option first. About obexd: compatibility with old obexd needs to be preserved for a while, because Tizen uses obexd 0.44 and I don't know if or when it can be updated. It's also convenient (some distros like Debian Testing do not have 0.47 yet). Note that the new obexd API uses a temporary file to transfer. Those files should be created in the system temp dir where they can be garbage collected. Reliably detecting transfer completion depends on listening to signals in advance - see [2]. In SyncEvolution, listening to D-Bus signals is done with the custom GDBusCXX::SignalWatch template class. Documentation of that C++ D-Bus binding is admittedly weak. Grep the source to find examples how it is used and/or let me know if you want better documentation of the C++ wrapper and I'll add it. [1] Previous discussions: http://www.mail-archive.com/syncevolution@syncevolution.org/msg03148.html http://www.mail-archive.com/syncevolution@syncevolution.org/msg03167.html [2] http://thread.gmane.org/gmane.linux.bluez.kernel/28481 -- 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.

8 years, 5 months

3
33
0 / 0

[SyncEvolution] Sync failure due to large addressbook entires.

by Ross Vandegrift

Hello, Yesterday I used syncevolution to push my my address book out to Google Contacts via SyncML. In a subsequent run, some contacts had photos auto-added by Google. This has partially broken sync with my S40 phone. It imposes a max message size of 3k, and the images push those contacts over the limit. Syncevolution notices this: WARNING: outgoing item is larger (5334) than MaxObjSize (3000) of remote -> suppress now/mark for resend The sync mostly works, but takes around 15 minutes to finish. The first time, my phone's progress indicator stuck at 95% complete. On subsequent syncs, the phone finishes quickly but syncevo still waits for 15 minutes. Oddly, the times in the log do not reflect this. I don't care about having the photos associated with the contacts. Can they be stripped out before contacts are sent to the phone? The only config option on the phone side is to require a username/password. Thanks, Ross

8 years, 5 months

2
6
0 / 0

[SyncEvolution] SyncEvolution 1.3 release preparations + ActiveSync

by Patrick Ohly

Hello! I have finished packaging SyncEvolution 1.2.99.3. It is in the "unstable" apt repo and downloads.syncevolution.org. However, I am going to delay sending out the official announcement for a few more days because I want to include some words about the migration of bug tracking and git repo to freedesktop.org, which should happen this weekend. The biggest change is that using ActiveSync is now possible without compiling from source. See the attached release announcement and https://syncevolution.org/wiki/google-contacts-activesync for details. Feedback from early adopters would be very welcome to improve the Wiki page. -- 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.

8 years, 5 months

4
9
0 / 0

[SyncEvolution] SyncEvolution 1.2.99.4 for Maemo and Harmattan

by Ove Kåven

I've finally managed to get everything to work, I think. Patrick, if you want to see my changes, you can download a tarball from http://people.debian.org/~ovek/harmattan/syncevolution_1.2.99.4-1.tar.gz It contains the git tree I work from. Most of the build system patches are probably in the FREMANTLE-1-2-99-3 branch. I could perhaps make a list if you want, but perhaps you want to look for yourself. --- Notes for Maemo Fremantle: The package should be available from extras-devel, or from http://people.debian.org/~ovek/maemo/ The changelog is: * Fixes to Maemo calendar backend. - Updated to use SyncEvolution's new support for automatically detecting whether to sync notes in text/calendar or in text/plain format. (Previously, the default was to always sync as text/plain, which would lose any metadata.) - Return ITEM_REPLACED instead of ITEM_MERGED if the calendar-backend detects conflicts. - Implemented SyncSourceLogging::getDescription(), to make it easier for users to find out which entry is the problem if something goes wrong. - In listAllItems(), read entries from database one by one, instead of loading everything into RAM all at once. This may be a little slower, but it would also reduce resident memory requirements for large calendars. Since RAM is a precious resource on the N900, this is hopefully a net win. * Updated packaging for new SyncEvolution build system. Build-Depend on automake 1.10, libtool, libboost1.42-dev, and libcppunit-dev. * Although I've tried to use the newest tools available in the Fremantle repositories, they're still a bit old for the SyncEvolution build system, and I had to patch the build system a fair bit for it to work. * Also patched the SyncEvolution code itself to work with the fairly old compiler (gcc 4.2). If people wish, the backend could be sped up by moving away from TrackingSyncSource and use a timestamp-based approach (like KCalExtended does) instead. A drawback of such an approach would be that you should not change the calendar while a sync is in progress. I already wrote some code for this, but didn't finish it since I wasn't sure it was worth it. --- Notes for MeeGo Harmattan: The package should be available from http://people.debian.org/~ovek/harmattan/ The changelog is: * Embed libneon and host into the SyncEvolution packages, so that DAV support can finally be enabled. * Various fixes and enhancements to KCalExtended backend. - Support synchronizing tasks and notes. - In --print-databases, list UIDs instead of file name (all listed calendars have the same file name anyway). Allow selecting database by UID in addition to name. - Only load one copy of the whole calendar into RAM when starting the sync. It shouldn't be necessary to load two. - Fixed failures when refreshing from remote peer and the local database wasn't empty, and other bugs. * Patches and updates from Fremantle merged into Harmattan tree. The tasks and notes support is untested. Please report on how it works. I also tried two other ways to improve the KCalExtended backend: 1. Convert it to TrackingSyncSource, for better reliability. This proved infeasible because insertItem() needs to return a new revision, but the new revision is not generated before calling save(), which is only done in endSync(). And, of course, calling save() for every single item is abysmally slow (and I couldn't even get it to work properly). However, it might still be possible to rewrite the backend to be TrackingSyncSource-*like*, with the difference of loading the new revisions in endSync() instead of in insertItem(), which would not be as slow. But probably still slower than the current approach. 2. Use partial loading of the calendar, to reduce memory requirements. It turns out that the bug that caused this feature to be disabled, bugs.meego.com/6061, is not actually fixed. It's fixed if a save() is done between step 3 and 4 in Patrick's recipe, but it still fails if there's no save(). And again, doing a save() in every single deleteItem or insertItem is not desirable.

8 years, 5 months

3
29
0 / 0

[SyncEvolution] PBAP: one-way sync modes

by Patrick Ohly

Hello! For the PBAP caching mechanism in SyncEvolution I'd like to use the Synthesis engine. I think that makes sense because the engine does a few things which would have to be done manually otherwise (translate between formats, finding pairs). The improvements below would also make sense in other use cases. At the moment the engine (or rather, SyncML) lacks a few things which I need to change. I'm focusing on one-way-from-client syncing because the server has a bit more control over what it does and because it matches the SyncEvolution use case. In SyncML, incremental one-way syncs fall back to a two-way slow sync after a failure. If the server has an item which the client no longer has, then the item will be recreated on the client, despite the intention to only transfer data in one direction. Right? This is undesirable in general (IMHO), and an absolute no-no for PBAP as the client, because it cannot write the changes. As a first step I would disable sending changes to the client if the client asked for a one-way-from-client sync. The server's datastore can already be marked read-only (<readonly> config option, SETREADONLY()); something similar for the peer's datastore would make sense. Then I could leave the default behavior as it is and use a script function to trigger the desired behavior. Actually, there is SETREFRESHONLY(). According to the docs, it is meant to be used for turning a two-way sync requested by the client into a refresh-from-remote. I need to check whether I can use that or still need to add/modify something. Suppose a slow sync was done in that modified refresh-only mode. Any item that the server has which are not on the client need to be removed if the server's storage is meant to mirror the client. At the moment, the engine cannot know whether it is meant to mirror the data and thus it will leave the extra items on the server unchanged. I intend to add a "<mirror>" config option similar to "<readonly>". If set, the engine will not only avoid sending changes to the client, it will also remove those extra local items. Finally, during a slow sync where a match was found, extra properties in the server's copy of an item must be removed to avoid keeping stale data. This can already be done by configuring the merging of items accordingly (instead of preserving as much data as possible, ensure that the client's item is always considered the "winning" one and that its version completely overwrites the server's). -- 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.

8 years, 5 months

2
2
0 / 0

[SyncEvolution] DBUS timeout when syncing contacts N9 <-> owncloud

by Toke Høiland-Jørgensen

Hi I've been trying to set up syncevolution to sync the PIM data on my N9 to an owncloud instance (i.e. using caldav/carddav). I have set things up following this guide: http://tanghus.net/2012/07/syncing-your-n900-with-owncloud-an-update/ But changing the phone database names to match the output of `syncevolution --print-databases`. Sync seems to work; that is, the calendar (which is mostly empty) syncs correctly, and I've managed to sync the first ~80 contacts (out of ~400). However, after those first contacts (on the first sync), I got a timeout, and subsequent syncs times out without transferring any contacts, even after I've imported the same contact database on both ends of the sync (so there are not that many differences). I've tried disabling dumpData and printChanges (as per an earlier post on this list), but the error still occurs. I believe the relevant output is this: [INFO @owncloud] @owncloud/contacts: starting first time sync, two-way (peer is server) [ERROR] sending message to child failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [INFO] Transport giving up after 0 retries and 0:25min [ERROR] transport problem: transport failed, retry period exceeded [INFO] @default/contacts: inactive [ERROR] @default/contacts: aborted on behalf of user (local, status 20017) The complete log file is available here: https://owncloud.toke.dk/public.php?service=files&token=b5f7b1669c2db8309... I'm using syncevolution 1.2.99.4 from http://people.debian.org/~ovek/harmattan/. Any help would be greatly appreciated; I would really like to be able to sync my phone data. I'll be happy to provide any extra data needed and/or investigate other options. Thanks in advance :) -Toke -- Toke Høiland-Jørgensen toke(a)toke.dk

8 years, 6 months

3
12
0 / 0

[SyncEvolution] Bridging Owncloud

by Guillaume Lanquepin-Chesnais

Hello, I'm trying to set up syncevolution as a bridge between an Owncloud server (carddav/caldav) and a nokia n8. The syncevolution is installed as an standalone HTTP server (BTW it would be nice if you can add a "server" version, i.e without UI, evolution, or BT, of syncevolution in your repo). |n8|== SYNCML(HTTP) == > |syncevolution| == caldav ==> |owncloud| Up to now, I tried to follow indications from the README but I must said that the way SyncEvolution bridge caldav/syncml remains unclear to me. So, I success to setup a "target", meaming that "syncevolution --print-items target-config@webdav calendar" gives me what I was expected. I also configured a "client" as follow: syncevolution --configure \ --template SyncEvolution_Client \ syncURL=local://@webdav \ username= \ password= \ webdav But it seems that I wasn't not able to set up a "source" since I get [ERROR] error code from SyncEvolution fatal error (local, status 10500): no sources active, check configuration When I do a slow sync (syncevolution --sync slow webdav)... I embedded my script and its error log. So How to set up a bridge with caldav? Regards, Guillaume Lanquepin

8 years, 6 months

2
2
0 / 0

[SyncEvolution] Events sync growing at the rate of +1

by Onyeibo Oku

Okay, so I lost my laptop and had to reconfigure syncevo for desktop. I also rooted my Android device so I wanted to try more things with Synthesis SyncML PRO. It works as before except for one tiny problem, The (birthday) events data duplicates and i get multiple entries on the corresponding contact record on my phone Let me explain: I like to be reminded of my contact's events e.g. birthdays. So i had synthesis show those as events on the calendar (there is a switch for that). I get those info synced as an event to the file database (I don't use EDS). On syncing again, syncevo doesn't realize they are birthday events from contacts so they get pulled again, and again and the corresponding entry on my device grows at same rate. How do i get a desirable sync in this case? Regards Onyeibo

8 years, 6 months

2
1
0 / 0

[SyncEvolution] SSL negotiation errors when accessing syncevolution.org using IPv6

by Toke Høiland-Jørgensen

I'm having trouble accessing the web site at syncevolution.org. I get ssl negotiation errors with every browser I've tried (firefox, chromium, opera, konqueror, rekonq, links, lynx, w3m). They all report no matching SSL cyphers. Disabling ipv6 fixes the issue (in Firefox at least). Is it possible that there might be a server misconfiguration on the ipv6 end, or should I go poking some more in my own system? :) -Toke -- Toke Høiland-Jørgensen toke(a)toke.dk

8 years, 6 months

2
1
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

syncevolution August 2012