On Tue, 2012-06-05 at 21:21 +0200, Patrick Ohly wrote:
> On Sun, 2012-06-03 at 02:01 +1200, Jane Atkinson wrote:
> > In any case, in the past I've used the Start from Scratch options
> > successfully in Sync-UI, which I thought were the same as the
> > command-line refresh options. If that's correct, then it seems that
> > something else is going on.
> 
> Your log file pointed me in the right direction: the recently expanded
> DevInf confuses the phone. Basically syncing with Nokia (?) phones is
> broken in the development version of SyncEvolution. Other libsynthesis
> users are not affected.
> 
> I can reproduce the issue here with a Nokia N97 mini. There's nothing
> wrong in SyncEvolution's usage of SyncML, it's the implementation in the
> phone which is broken. But that doesn't help.
> 
> I'm not sure yet how to deal with the issue. The offending data is
> generated before the SyncML engine has a chance to identify the peer.

It turns out that I just wasn't looking right. The Put is processed
before the Get, and thus my code worked as intended. I was looking at
the wrong part of the generated DevInf: a virtual datastore doesn't have
any of the special SyncCaps, while normal ones do.

One can argue that a virtual datastore should perhaps inherit some of
these flags from the underlying datastores, but that is not needed (yet)
because these flags are only used for SyncEvolution<->SyncEvolution
syncing where virtual datastores are not used.

Anyway, I think I have a solution. Jane, stay tuned for updated
binaries... and thanks for testing!

-- 
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.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to