Hi Filippo, > > the 3.5 is coming really soon and fixes another couple of rare race > > conditions that can lead to segmentation faults of hcid. The 3.1 version > > is not really suited for daily use. > > allright, I'm going to wait for bluez 3.5 and then package it.
should be out this week. If I am not going to be to distracted at the Linux-Kongress. > > > bluez-libs compiled out of the box by just unpacking and moving the > > > debian directory over, but bluez-utils needs some work: > > > > > > * remove bluez-bcm203x package (bcm203x firmware loader removed upstream) > > > > Not needed at all. You don't wanna support a 2.4 kernel and even if you > > really want to, you won't find any of these devices anymore. For all 2.6 > > kernels the bcm203x kernel module takes care of loading the firmware. > > I'm going to drop it after etch release when we'll discontinue support for 2.4 > kernels. You can drop it now actually. A Liunx 2.4 kernel user and owner of this device is a really really unlikely combination. I mean it. It would take me at least a couple of hours to find my dongle. > > This package has to die and from an USB and udev perspective it was a > > really nasty hack. > > > > > * remove 000_rfcomm_conf_example.patch: the example is already commented > > > * remove 004_rfcomm_usage.patch: applied upstream > > > > Sometimes it is a good idea to feed patches back to upstream so I don't > > have to extract them from the packages. > > yep, I'm used to do it, I must have overlooked these patches. Do you have any other patches that are not upstream? > > They are a fully replacement for the ones in the Debian package. That is > > another thing that always needs to be discussed with upstream. > > indeed, this has been discussed extensively in > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378839 and on bluez-devel > > > > > To install them --enable-pcmciarules is needed and the correct configure > > call. Example is in the README. Otherwise the wrong directory will be > > picked for them. > > okay, thanks. Please test the installation. The current version contains a nasty hack to get them into the right place. And please drop your passkey agent think completely. This will be distribution specific and can't be a solution. It is better to put the passkey-agent.c example in the docs directory as an example and mention it in a README.Debian. That said. I am missing a package for bluez-gnome which contains the graphical passkey agent. New version is coming up also this week. It will fix a small glitch with the status icon. Regards Marcel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]