Coinciding with the new BB 8300 came my upgrade to the -release version
of Jaunty on my primary laptop. While in the midst of this I discovered
Barry in the repository and took a look. Unfortunately I came up empty
with error messages that look like they have already been covered on
this list.
I pulled the latest version of Barry from the git/cvs repository and
built it on my existing Intrepid box (64 bit) and all went well.
* Version of Barry
* How you installed Barry
But my primary laptop runs into the same errors with either the version
from the Ubuntu repository (looks to be version 0.14) or the latest from
the repository (0.15). Barry installed in both cases in /usr
breset -- works ok. Detects device and appears to perform reset.
bidentify -- works ok. Detects device and shows PIN
bcharge -- appears to read and configure voltage correctly
btool -- detects device but does not allow reading databases
(btool -t)
* The exact error message you get, if any, when you encounter the
problem
* Any sample data that may help in reproducing the problem
poke...@pokeefe-laptop:~/blackberry/barry/tools$ btool -t
Blackberry devices found:
Device ID: 0x8e56810. PIN: 3039712f, Description: RIM BlackBerry Device
Using device (PIN): 3039712f
Bad packet size. Packet: 26. DataSize(): 26. Required size: 44
00000000: 00 00 1a 00 09 ff 00 07 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
* Name and version of your operating system
Ubuntu jaunty (development branch)
* Architecture of your system (32 bit? 64 bit? Intel? iMac?)
Linux pokeefe-laptop 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:43:21
UTC 2009 i686 GNU/Linux
The BB8300 does correctly sync/backup using version 0.15 from the
repository on my x86_64/Intrepid box, and also correctly works with the
BB supplied PocketMac software on an Intel based Macbook. There are no
MSFT boxes around here to test the BB Supplied sync software but I
imagine it will work fine since both Barry and PocketMac have
demonstrated an ability to communicate to the BB device.
Barry 0.15 also appears to have a circular dependency on libbarry. It
does not complete the compile until it can find it in /usr/lib. My
compile cycle looks like this:
c/o
buildgen.sh
configure (boost, gui, opensync)
make (fails with circular ref to libbarry and pkg-config note)
sudo make install (puts libbarry in correct place)
wipe barry directory (can't do configure a second time due to file
cleanup issue previously discussed on mailing list0
buildgen.sh
configure (boost, gui, opensync)
make (succeeds)
sudo make install
Let me know where I can dig in to help. I feel it's probably an upstream
dependency problem introduced by Jaunty, just a question of tracking it
down.
--
Paul O'Keefe <p...@megabelle.net>
VOIP: 1-770-250-5165
FindMe: 1-678-967-4103
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
