February 2010 - syncevolution@synevolution.org

Re: [SyncEvolution] Nokia N85 sync status

by Lukas Zeller

Sorry, Jussi, that was my fault. There was a permission for the sync data folder missing in your IOT server account. I have fixed this now. However it seems that auth with the N85 did not work with SyncML 1.2, only with 1.1 (but then also failed because of my misconfiguration). Could you try again? Lukas On Feb 16, 2010, at 19:19 , Jussi Kukkonen wrote: > Lukas Zeller wrote: >> Hi Jussi, >> thanks for the XML, that's fine as well. >> I see no difference in the syntax, so my guess is that the Nokia does >> not like the X-EVOLUTION extra types. >> A quick way to verify that would be a test sync against our IOT >> server with that N85 - it has the same engine but no X-YYYY TYPE >> parameters. > > The phone almost immediately gives me the useless "System error" message it gives in just about any problem situation (it's not a login problem however, that has another message). No logs appear on server. > > My current client settings: > > server version: 1.2 (tried 1.1 as well) > server ID: (none) > Host address: http://www.synthesis.ch/synciot > Port: 80 > User name: jku(a)linux.intel.com > password: (same password as for web interface) > Contacts database: contacts > > -Jussi > Lukas Zeller (luz(a)synthesis.ch) - Synthesis AG, SyncML Solutions & Sustainable Software Concepts info(a)synthesis.ch, http://www.synthesis.ch

11 years, 7 months

2
3
0 / 0

[SyncEvolution] SyncSource API changes in 1.0

by Patrick Ohly

Hello! For 1.0, we hope to add automatic syncing. Part of that effort is to make starting and running a sync cheaper a) by not dumping databases unless the SyncML session really runs b) reducing the amount of calls into the underlying database This is tracked as: http://bugzilla.moblin.org/show_bug.cgi?id=7708 Regardless whether we go ahead with automatic syncing, these optimizations are worthwhile on their own. Point b) is something that Franz explicitly asked about once. But they depend on an API change, so let me bring that up here. Are the proposed changes that I currently have pending in my "pohly" branch in the git repo on moblin.org okay? Ove, Franz, your backends should continue to compile and work, but they don't completely support the new "preventSlowSync" feature. It will always be on, even in the one case where a slow sync is acceptable (empty local database). Instead of repeating myself, let me quote the commit messages here. For diffs (if necessary) consult the repo: commit 33f6e2064c7fc7c376336e86fd9460df3cdbf14c Author: Patrick Ohly <patrick.ohly(a)intel.com> Date: Tue Feb 16 17:43:41 2010 +0100 SyncSourceRevisions: cache result of listAllItems() (MB #7708) When automatic backups are enabled (the default), SyncSourceRevisions and derived classes like TrackingSyncSource called listAllItems() twice, once during backup and once while checking for changes. This patch introduces caching of the result returned by the first call. During a normal session, that will be during backup, with change detection reusing the information. If backups are off, the call will happen during change detection, as before. The advantages of this change are: - more efficient, in particular for sources where listAllItems() is slow - avoids a race condition (backup stores one set of items, changes are made, change detection works with another set) That race condition is both fairly theoretical (short time window) and had no impact on the correctness of the sync, only on the output (data comparison would not show all changes synced later). Now the race condition still exists if changes are made while a sync runs, which is the bigger problem that still needs to be solved (for EDS, see MB #3479). Restoring data also calls listAllItems(). It does not use the cached information, just in case that it is to be called more than once per instance, and because there is no benefit. commit 5f18644fbfc944db1759dbb726f2ea8b7892e0cf Author: Patrick Ohly <patrick.ohly(a)intel.com> Date: Tue Feb 16 20:11:16 2010 +0100 SyncSource API: added m_isEmpty operation (MB #7708) The current solution of checking for empty sources by looking at the "before" database dump is a hack which fails if creating that backup was disabled. It also prevents delaying the dump until after the start of the session, because the information must be available before starting the session, so that the XML config can be created with slow sync check enabled if needed. This patch adds a new operation which backends must implement if they want to provide the "is empty" information for the slow sync detection. This is optional. If the information is not available, slow sync detection is always on, even when not strictly needed. commit fc059f7017f32b9184b5781a875a3ab22ca0c0c5 Author: Patrick Ohly <patrick.ohly(a)intel.com> Date: Tue Feb 16 20:15:50 2010 +0100 SQLite backend: implement m_isEmpty operation (MB #7708) This patch demonstrates how the operation can be implemented by sources implementing the operations themselves. The implementation of SQLiteContactSource::isEmpty() might not be perfect, but it should get the job done. commit 9e45cb0c56e9975637214f0f03add823171b314c Author: Patrick Ohly <patrick.ohly(a)intel.com> Date: Tue Feb 16 20:17:36 2010 +0100 TrackingSyncSource: added isEmpty() pure virtual method (MB #7708) This implements the new m_isEmpty operation with a pure virtual TrackingSyncSource::isEmpty() callback. It follows the philosophy that TrackingSyncSource should a) hide the underlying operation mechanism and b) prevent derived classes from compiling unless they do everything that is expected of them. All of the in-tree backends were adapted so that they provide at least a dummy implementation of the call, to keep them in a usable state. The file backend implementation is okay. The Evolution backends get the job done correctly, but not efficiently. Maemo and XMLRPC backends always return false, which is acceptable but should be changed (disables the "allow slow sync for empty databases" heuristic). commit 4713aa435afa8e51b18780f94595e81eead6008c Author: Patrick Ohly <patrick.ohly(a)intel.com> Date: Tue Feb 16 17:15:46 2010 +0100 database comparison: also delay it in clients (MB #7708) Delaying the database comparison was done initially for servers to limit it to the sources really used by the client. In a client the same delay makes sense for syncs which fail because the peer cannot be reached. It is possible to delay the dump because starting the session no longer depends on it thanks to the m_isEmpty() operation. -- 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.

11 years, 7 months

1
0
0 / 0

[SyncEvolution] status 2010-02-16: open issues?!

by Patrick Ohly

Hello! The discussion we had about Debian and Ubuntu packaging was useful, so let me try something else. In addition to reporting progress, I'll also highlight some gaps. Perhaps someone takes that as an incentive to solve them ;-) Last week several problems were fixed related to "virtual sources", the combination of a calendar and task source. The implementation on the client side was incomplete, affecting synchronization with OVI.com. On the server side the combination with aliases didn't work, which is needed for the Nokia N85. Patches are now pending review before they'll get merged and (hopefully soon) a beta 2 can be released. The issues with libbluetooth compatibility should be solved, so that beta 2 binaries from syncevolution.org can ship with enabled Bluetooth support. Ove fixed all reported issues in the Maemo port and released updated binaries. Details: * Patrick: implemented client-side support for combined events/tasks data stores (needed for Nokia Ovi.com sync), fixed that support on server side (Nokia N85 MB #9664) and in D-Bus CheckSource() (MB #9535), build fixes and improved syncevolution.org packaging (libbluetooth compatibility MB #9289), performance and usability improvements of server (delayed database dumping MB #7710), more efficient database dumping (MB #7708), set up two-way sharing of XML config with Synthesis via scripts * Jussi: finished device sync config UI, Bluetooth panel integration, testing and bug fixing, syncing with N85 * Congwu, Yongsheng: finished their work for the ww07 milestone, on vacation now * Ove (Maemo): synchronize button (MB #9715), notes syncing (MB #9585) Now the gaps: * SSL certificate checking with Google and importing certificates: can someone find out how this works on Maemo? * NetworkManager: the syncevo-dbus-server currently only supports ConnMan to determine whether the user is online and Bluetooth is enabled. This allows the sync-UI and automatic syncing (in development) to prevent a sync when it is known to fail. Without ConnMan, the syncevo-dbus-server will always claim that we are online. Fixing this is currently a low-priority item (MB #7700), volunteers needed to get NetworkManager support into 1.0. * web site: with more and more people hearing about and using 1.0 beta, it's time to give syncevolution.org and overhaul to cover new platforms and new capabilities. Help needed, ideally long-term. * HTTP Auth: needs some fairly simple changes, not currently on anyones task list though (MB #2429) -- 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.

11 years, 7 months

1
0
0 / 0

[SyncEvolution] status 2010-02-09

by Patrick Ohly

Hi! Okay, long time now see, eh, write. Quick recap: * SyncEvolution 1.0 beta 1 released, development keeps us busy. 1.0 beta 1 turned out to be fairly stable, but there were bug fixes (see below). Lots of new features in "master", so consider compiling that if you want to follow what we are doing. * 0.9.2 released. Ove Kaaven made it available for Maemo, including a calendar backend that he wrote. * Went to FOSDEM last weekend and gave two talks. Slides can be viewed on our site, video of the Lightning Talk will be posted by FOSDEM later. See http://syncevolution.org/blogs/pohly/2010/fosdem-2010 Noteworthy new issues potentially affecting users: * The packages provided by Ubuntu and Debian did not contain proper timezone support. Use the packages from syncevolution.org to work around this (Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565720, Ubuntu bug https://bugs.launchpad.net/bugs/509032) * 1.0 beta 1 cannot do Bluetooth sync via GUI because transport is missing in syncevo-dbus-server (MB #9436, patch pending) * 1.0 beta 1 has an issue with unintentionally enabling sources created for one peer in another (MB #9329); when configuring a peer using the "server" shorthand for a "server@other-context", properties from the default context were copied into that other context (MB #9338) * The Horde Groupware server gets confused by our device ID and applies workarounds for old, broken Funambol clients to us, which break calendar sync (MB #9347). Using such device IDs was necessary at one point for Funambol (wouldn't support multiple instances otherwise), but that no longer is the case, so can be fixed by renaming the device ID. Comment for distributors: there's a new README.packagers file. Please, consider compiling and packaging the GNOME Bluetooth Panel plugin that is included in the lastest SyncEvolution source code (not yet in 1.0 beta 1). Development (by week basically, starting end of last year): * Yongsheng: D-Bus implementation of client/server interaction for dialogs in the UIs (MB #6376), used for interactive password requests, database restore (MB #8144), auto-termination of D-Bus server and tracking of clients (MB #7710), added support for X-SKYPE (MB# 8948) * Congwu: finished "super datastore" (= merged calender/todo), force slow sync on server-side when requested, discussed and worked on configuration and pairing of phones (MB #7838/7089), dealt with feedback about phone syncing (Nokia 6600, N900, N85), analysis of sync stack in Maemo 5/N900, fixes for OBEX transport, datastore aliases (MB #7871), don't resend initial message of sync (MB#8758), removed hard dependency on CPPUnit header files * Raji: http_proxy env variable support when using libsoup[-gnome] (MB #8177), recreating full name when lost on server (MB #5664) * Patrick: implemented handling of unexpected slow syncs in the client (MB #2416), Android port, some more Oracle testing * Yongsheng: syncevo-dbus-server automatic termination when idle (MB #7711), fixed IO spinner support in D-Bus server, investigated different sync solutions improved D-Bus testing (MB #9065), fixed handling of normalized config names in logdir code (MB #8350) * Congwu: template handling for SyncML clients, searching for right template via fuzzy LCS string match and custom code, assist QA with Bluetooth testing, GNOME Bluetooth panel plugin, presence detection * Patrick: CPPUnit header file dependencies (MB #9149), code merging and distribution fixes, configuration option and infrastructure for handling unexpected slow syncs (MB #9156, #2416), normalization of config names when saving to disk (MB #8350), documentation update for 1.0 (MB #8497), more flexible support for backend-specific XML configs, avoid exceptions during normal run, fixed reporting of local errors (MB #8757) and partially successful syncs (MB #7755), improved printing of report (MB #2069), added Goosync and Oracle templates, timeouts for unresponsive clients (MB #7710), "syncevolution --status" local item counts empty (MB #9097) * Jussi: fixes for unified configuration dialog, slow sync and emergency handling * Raji: investigated timezone conversion issues with Outlook meeting invitations (MB #4815) * Yongsheng: finished auto-termination of syncevo-dbus-server (MB #7711), updated test-dbus.py (MB #9065, may still overwrite developer's data MB #9332), started to provide more information via D-Bus API (password MB #9169, first sync flag MB #8729) * Congwu: presence detection for HTTP * Patrick: command line screwed up shared properties when using a shorthand notation for peers in the non-default context (MB #9338, already broken in 1.0 alpha, found to late for 1.0 beta), adding sources affects other peers in same context (MB #9329, found by QA in 1.0 beta), fixed --disable-bluetooth (MB #9260), fixed source code compatibility with libbluetooth2 and 3 (MB #9289), * Jussi: several GTK GUI updates, for example restore from backup * Yongsheng: GetConfig() includes real passwords (MB #9169), return first-time sync information via GetReports (MB #8729), fix for test-dbus.py so that it no longer overwrites normal local databases (MB #9332), GetConfig() support for Bluetooth peers (MB #9216, some improvements and debugging left to do, see MB #9576) * Congwu: presence detection via ConnMan for HTTP and Bluetooth, GNOME Bluetooth Panel plugin in SyncEvolution * Patrick: fix for CheckSource() and virtual sources (MB #9535), fixes for logdir naming, database dumps now use less disk space thanks to hard-linking, database comparisons are faster, database comparison is more intelligent about previous dump (all part of MB #7708), included Congwu's GNOME Bluetooth Panel plugin in the SyncEvolution distro (MB #7089), split up XML config into parts which can be extended/replaced by users and synchronized with Synthesis upstream (MB #7712) * Jussi: device configuration, lots of fixes and polishing now that QA is testing the redesigned UI -- 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.

11 years, 7 months

3
11
0 / 0

[SyncEvolution] Sync Dbus Service

by Bommaraju, Rajyalakshmi

Hi, I compiled and installed syncevolution source with -enable-dbus-service option . I fired up d-feet to see if org.moblin.sync dbus service running, but could not find anything with that name. Do I need to set up any configuration file for it to be up and running? Please list the steps. Thanks Raji

11 years, 7 months

3
2
0 / 0

[SyncEvolution] Ovi Sync Status update

by Chen Congwu

I am starting testing with Nokia Ovi service this week, here are the first step updates I have found: (I am only testing against Contacts/vcard3.0 at this time). XML parsing error: some special cases is not properly handled by smltk, this has been fixed (Though more problems might still exist). The server does not accept entries without a valid REV field (therefore break many file backend based test cases) The authentication process meeds 3 retries to success (which means 3 additional roundtrips is needed). 'Delete' in normal sync (including two-way, one-way-from-client) does not effectly delete the data in the server side (The server responds OK but it never deleted it, I cannot verify this by web interface since OVI.com is under maintenence these days but this is what the client get). To delete the data on the server side, we have to use refresh-from-client. The combined datastore (calendar+todo) does not work properly at SyncEvolution (this is a client side problem) and Patrick is working on this. -- Regards, Chen Congwu Moblin China Development

11 years, 7 months

1
0
0 / 0

[SyncEvolution] nokia n900: install failed?

by stephan0h＠gmx.net

Hi, Maybe I'm a complete dummy but I just tried to install syncevolution as described in http://syncevolution.org/documentation/installation in the paragraph about Nokia internet tablets by clicking in the install-file link - but my device tells me syncevolution is not available. What am I doing wrong? What's the second best way to install it? thanks & kind regards, stephan

11 years, 7 months

2
1
0 / 0

[SyncEvolution] Running 0.9 and 1.0 side by side?

by Frederik Elwert

Hi! After the opportunity to meet Partick on Fosdem, I finally wanted to get my hands dirty looking into the new 1.0 D-Bus API. So I just wanted to ask if it is possible to install/run syncevolution 0.9 and 1.0 side by side? Since SE now has to be installed and cannot be run independently from the binary, I wanted to know if there is a way to run both versions, one for everyday use and one for testing. Thanks in advance, cheers, Frederik

11 years, 7 months

2
1
0 / 0

[SyncEvolution] backup-restore changes on the pipeline

by Jussi Kukkonen

I'm thinking I'll do some changes to backup-restore in the UI based on initial testing: First, I was doing a refresh-from-client automatically after restore. Patrick pointed out this is not needed, normal sync should work in "normal" situations and that restoring a backup will not fix a "slow-sync-request" situation Second, Zang Jinke pointed out that automatically syncing at all may be a bad idea, and we agreed (bug 9619). Changes I'm currently testing in mb9619 branch: * don't sync automatically after restoring * add more indication of the type of running operation ("Restoring" and "Restore complete") * explain the choices better in emergency view. In the slow sync request case this means mentioning that a "special" sync is required even after restoring a backup. * Show this info bar after a restore: | You've just restored a backup. The changes [ Sync now ] | have not been synced with $servicename yet The action button is a bit redundant but I think it is in line with the other info bar messages: responding to the infobar message should be possible in the infobar - Jussi

11 years, 7 months

1
0
0 / 0

[SyncEvolution] Iphone AddressBook schema

by Bastl

Hi I'm looking for help with syncing my iphone's AddressBook. It seems SyncEvolution can handle it, so i ask here. I want to migrate my contacts to some other software, and want to understand the db-schema. The closest thing I could find on the net is: SELECT t1.First, t1.Last, t2.value from ABPerson as t1, ABMultiValue as t2 WHERE t2.record_id = t1.ROWID But that doesnt give me postal adresses and omits any labels attached to the "multivalues". Can someone here help me with that? Preferably with a documented db-schema ? Thanks, Bastl.

11 years, 7 months

2
1
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

syncevolution February 2010