[Opensync-devel] vnote11 reported unexpected

[Emanoil K. <del...@ya...>]

Another question for you that we may discuss until the weekend.

As I mentioned I'm using evo2-sync as a pair for testing akonadi-sync and I've noticed that evo2-sync is reporting notes in vnote11 format and not journal (which is breaking the sync as akonadi-sync expects vjournal), which makes me think it is picking up the first available format from the opposite member. It is either the plugin or (what I think) the libopensync itself, selecting the first available path for the "note" sync. How can I tell opensync (from akonadi POV) I can and I want vjournal. I've tried setting preferred format in discover but it does not help much. The odd thing is that evolution does not report vnote11 as supported at all.

Do I need to file bugs ... in normal life I would.

here a portion to give you an idea

akonadi_opensync(29750) DataSink::commit: change uid: "20100910T224808Z-11504-1010-1-0@lisa"
akonadi_opensync(29750) DataSink::commit: objform: vnote11
akonadi_opensync(29750) DataSink::commit:
akonadi_opensync(29750) DataSink::commit: data "BEGIN:VNOTE
VERSION:1.1
CATEGORIES:first
CREATED:20100910T224808Z
LAST-MODIFIED:20100910T224808Z
SUMMARY:asdfasdf
UID:20100910T224808Z-11504-1010-1-0@lisa
END:VNOTE
"
akonadi_opensync(29750) DataSink::collection:
akonadi_opensync(29750) DataSink::setPayload:
akonadi_opensync(29750) DataSink::setPayload: notes
ERROR: Broken Pipe
ERROR: Broken Pipe
ERROR: Broken Pipe
ERROR: Trying to send to a queue thats not connected
ERROR: Broken Pipe

OK! Completing synchronization!
ERROR: Broken Pipe
ERROR: Broken Pipe
ERROR: Broken Pipe
Error for entry 20100910T224808Z-11504-1010-1-0@lisa (vnote11) and member 2 (akonadi-sync): Broken Pipe
Mapping Error: Broken Pipe
EXIT_ERROR: osync_obj_engine_commit_change_callback: Broken Pipe

and this data is coming from evo2. and evo2 is reporting vjournal.
Hm ... from the way I see how evolution works I don't think I'll upgrade my current debian system soon.
Perhaps it would be better to get the syncing with kde3 done for now.
However I would like to work on this plugin to get it stable until I move to kde4.

I'm also not sure if I have to try fixing evo2-sync the way I think it should work and proposing a patch. It would be very nice if someone knowing evo api gets involved.

regards

--- On Wed, 10/13/10, Daniel Gollub <go...@b1...> wrote:

> From: Daniel Gollub <go...@b1...>
> Subject: Re: [Opensync-devel] syncml-ds-tool
> To: ope...@li..., del...@ya...
> Date: Wednesday, October 13, 2010, 1:41 AM
> On Wednesday, October 13, 2010
> 08:59:11 am deloptes wrote:
> > developer@lisa:~/kde-testdir$ gdb syncml-ds-tool
> > GNU gdb (GDB) 7.2-debian
> > Copyright (C) 2010 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later
> > <http://gnu.org/licenses/gpl.html>
> > ...
> > Starting program:
> /opt/testing/opensync/bin/syncml-ds-tool -b
> > xx:xx:xx:xx:xx:xx 7
> > [Thread debugging using libthread_db enabled]
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x00007ffff5e23d8a in _IO_vfprintf_internal
> (s=0x7fffffffddc0,
> > format=<value optimized out>,
> ap=0x7fffffffdf70)
> >     at vfprintf.c:1614
> > 1614    vfprintf.c: No such file or
> directory.
> >         in vfprintf.c
> > (gdb)             
>                 
> 
> Could you send the full backtrace?
> 
> Run: bt .. in gdb commandline.
> 
> And make sure libsyncml and syncml-ds-tool are build with
> debuginfo - gcc flag 
> -g ...
> 
> Best Regards,
> Daniel
> 
> -- 
> Daniel Gollub           
>             Geschaeftsfuehrer:
> Ralph Dehner
> Linux Consultant & Developer     
>    Unternehmenssitz:  Vohburg
> B1 Systems GmbH           
>           Amtsgericht:   
>    Ingolstadt
> Mobil: +49-(0)-160 47 73 970     
>    Handelsregister:   HRB
> 3537
> EMail: go...@b1... 
>         http://www.b1-systems.de
> 
> Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088
> Vohburg
> http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D
>