Package: bluez Version: 4.60-1 Severity: normal Filippo,
as already said in IRC, current documentation is largely suboptimal. I finally managed to pair devices by blueman, but I would expect to obtain pairing using hcitool and rfcomm. Command line workflow is completely undocumented. Maybe upstream would expect people write their own python snippets of code to obtain that? I have to use those crap applets only seriously? But for that, I also find the pairing quite weak, I can easily break the connection permanently (i.e. until next reboot). Too bad. I will try to report issues about that, but this a warn about the status of the package. IMHO as it is currently, it is not at release quality. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.2.16-2 simple interprocess messaging syst ii libbluetooth3 4.60-1 Library to use the BlueZ Linux Blu ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst ii libglib2.0-0 2.22.4-1 The GLib library of C routines ii libnl1 1.1-5 library for dealing with netlink s ii libusb-0.1-4 2:0.1.12-14 userspace USB programming library ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-89 creates device files in /dev ii module-init-tools 3.12~pre1-1 tools for managing Linux kernel mo hi udev 150-2 /dev/ and hotplug management daemo bluez recommends no packages. Versions of packages bluez suggests: ii python-dbus 0.83.0-1+b1 simple interprocess messaging syst ii python-gobject 2.20.0-1+b1 Python bindings for the GObject li -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org