Re: [Opensync-users] Kitchensync doesn't work (update from 0.20 to 0.34)

[Daniel G. <dg...@su...>]

On Wednesday 02 January 2008 13:02:15 Nicoco wrote:
> I've been using opensync 0.20 with kdepim and syncml plugin for some time
> now.
> Since the recent 0.34 update, nothing works.
> kitchensync now complains :

Which version of Kitchensync do you use?!

OpenSync 0.34 is experimental development and changed all over the place. The 
API changed al lot since 0.2x ... you need a ported Kitchensync version for 
the OpenSync 0.3x API. This is only the case for KDE4 and a special 
work-branch of KDE makes this possible... the default KDE3 is still intended 
for 0.2x..

>
> Error initializing Synchronization Engine for group "Nokia"
> No synchronizable objtype
>
> Clicking OK results in a "This engine was not in state initialized: 0" in
> the terminal

The group got never "discovered", this prodcure got introduced with the 
OpenSync 0.3x API. This got only slightly integrated so far in the 
Kitchensync compatible 0.3x versions... this is NOT (yet) integrated in the 
default KDE3 Kitchensync.... and those implementation are quite experimental 
as well since the discovery process is blocking and makes the UI not usable. 
There are some issues inside OpenSync 0.3x API to make "sane" use of a 
non-blocking osync_engine_discover call (on my todo list).

>
> Has anyone a clue about what's going on ?

Make sure you're using a ported version of Kitchensync for the OpenSync 0.3x 
API ... which tries to run the discovery after configurating the group. 
Currently we don't have any update process from 0.2x to 0.3x ... as i already 
mentioned 0.3x is experimental and intended to be a development branch. There 
are still the plans to change several configuration stored in ~/.opensync. If 
the latest changes about configuration are fixed, then we might provide 
update functionality. This isn't fixed yet, since OpenSync is still in a very 
early stage of development and we might just provide some "update scripts" 
instead of doing a proper update implementation from 0.2x to 0.3x. Since 0.2x 
didn't have any version information about the configuration, which makes 
out-of-the-box updating quite tricky. So for now the best way to got is just 
to drop/move your 0.2x ~/.opensync configuration... and experiment with a 
configuration from scratch.

Btw. did you build this from scratch? Or got this shipped by your distro?

best regards,
Daniel