Re: [Barry-devel] plugin compilation

[Chris F. <cd...@fo...>]

On Mon, May 28, 2007 at 01:12:58PM +0100, Jacek Nykis wrote:
> Thanks for answer.
> I have just tried with SVN version of opensync and I get:

[compiler errors]

Yes, OpenSync went through some significant API changes between
0.2x and 0.30, and CVS is not fully ported to that yet.
Sorry if I was unclear on that earlier.  The CVS plugin does not compile.


> I also tried to compile opensync-plugin from tarball with success. 
> Unfortunately only CVS version of btool works on my system, so I had to use 
> cvs btool and tarball plugin. I configured msynctool and I get:
> 
> Member 2 of type kdepim-sync just connected
> Member 1 of type barry-sync just connected
> All clients connected or error
> Member 1 of type barry-sync just sent all changes
> Received an entry 0mtl5cJfj9 with data of size 4 from member 2. Changetype 
> ADDED
> Received an entry 17WlyngmP8 with data of size 4 from member 2. Changetype 
> ADDED
> .......
> Received an entry y1nLRG5yve with data of size 4 from member 2. Changetype 
> ADDED
> Member 2 of type kdepim-sync just sent all changes
> All clients sent changes or error
> All conflicts have been reported
> Pipe closed! Exiting.
> Pipe closed! Exiting.
> 
> 
> Which looks fine, but nothing is stored on my blackberry.

Hmmm, interesting.  If you look at the barry-sync trace logs, is there
any mention of writing to the device?

It is good to remember that you are playing with experimental software
when you're working with the plugin.  It is cool that you're so eager
to help test it, but I'm afraid it's not quite ready for prime time.
I'm really happy you are trying it with the SVN OpenSync, so I'll try
to get the plugin fully ported, and have something better for you to
test soon.  That would be very helpful.


> It can by connected with another problem. After I try multisync 
> synchronization I cannot list blackberry databases:
> 
> 
> root@jack-desktop:/home/jack# btool -t
> Blackberry devices found:
> Device ID: 0xxxxxxxx. PIN: xxxxxxxx
> Bad packet size. Packet: 26. DataSize(): 26. Required size: 44
>     00000000: 00 00 1a 00 09 ff 00 06 52 49 4d 20 44 65 73 6b  ........RIM 
> Desk
>     00000010: 74 6f 70 00 00 00 00 00 02 00                    top.......
> 
> Barry::Error caught: Bad packet size. Packet: 26. DataSize(): 26. Required 
> size: 44

This is normal after a crash, which is what the Broken Pipe suggests.
Likely the plugin is crashing, and leaving the device in the Desktop state.
When btool then tries to open the Desktop mode, it gets an error, or
an unexpected response.

There are 2 ways to deal with this:

	1) Simplest way is to reset the device.  Use the "breset" command
		to reset all the connected Blackberries.

	2) Reverse engineer the protocol to find out what the error packet
		really means.  Some of those opening packets are not
		fully understood, otherwise, there might be a way to
		close and reopen the Desktop without a reset.
		Doing a USB reset on the device is so quick and painless,
		though, that this has not been a priority.

Hope that helps,
- Chris