Bug#378850: [Pkg-bluetooth-maintainers] Bug#378850: bluez-utils: README.Debian contradicts NEWS.Debian

[Marcel Holtmann]

Hi Filippo,

> > > > > > I've updated README.Debian accordingly to your input, it is available at
> > > > > > http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/README.Debian?op=file&rev=0&sc=0
> > > > > > do you mind having a look and see if it answers your question and/or it is
> > > > > > lacking something? I think it should fix #37885{0,1,2,4,6}.
> > > > > 
> > > > > Looks good. Are there any "real" bugs left that keep the procedures
> > > > > described in the new docs from working on bluez-utils 3.1-2? Or am I
> > > > > safe to try my bluetooth mouse again with 3.1-2?
> > > > 
> > > > should be fine IMO
> > > 
> > > Yes, works fine with the passkey in
> > > /etc/bluetooth/passkeys/<mac-address-of-remote-device>.
> > > 
> > > /etc/bluetooth/passkeys should be created on package install, and
> > > README.Debian mentions "/etc/default/passkeys" once in the PIN
> > > management paragraph, which should probably be /etc/bluetooth/passkeys.
> > 
> > I have no idea what you are cooking up here, but again, why don't you
> > ask upstream for what is possible and what not.
> 
> err, yes, be sure I'll ask more often in the future :)
> 
> > 
> > Seems like you are duplicating /var/lib/bluetooth/<bdaddr>/pincodes with
> > this work.
> 
> indeed, I was not aware of that feature, reading the code it is clear that
> simpler method is available.
> What about default outgoing pincode? from a quick look it will be asked to dbus
> nevertheless.

start with this one. Post a problem description on bluez-devel and how
you gonna like to see it working. Especially what behavior you expect
for the default passkey agent compared to the pincodes file. We can
discuss it then and fix up the code.

Regards

Marcel