Your message dated Wed, 26 Jul 2006 04:17:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#378446: fixed in bluez-utils 3.1-3
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: bluez-utils
Version: 3.1-1
Severity: important

There is no way to react on PIN code requests for outgoing connetions without 
"passkey-agent" running.  Binary can be built from "bluez-utils" source but it 
needs to be included in binary package and running when PIN code request is 
received.

"sudo pand --autozap --role PANU --connect 00:04:61:85:D5:F0"
while "passkey-agent" not running:

---
Jul 16 05:49:51 kiara pand[32393]: Bluetooth PAN daemon version 3.1
Jul 16 05:49:51 kiara pand[32393]: Connecting to 00:04:61:85:D5:F0
Jul 16 05:49:55 kiara hcid[32355]: pin_code_request (sba=00:0D:93:14:A3:73, 
dba=00:04:61:85:D5:F0)
Jul 16 05:49:55 kiara hcid[32355]: call_passkey_agent(): no agent registered
Jul 16 05:49:55 kiara pand[32393]: Connect to 00:04:61:85:D5:F0 failed. 
Permission denied(13)
---

"sudo pand --autozap --role PANU --connect 00:04:61:85:D5:F0"
while "passkey-agent" running:

---
Jul 16 05:50:13 kiara pand[32396]: Bluetooth PAN daemon version 3.1
Jul 16 05:50:13 kiara pand[32396]: Connecting to 00:04:61:85:D5:F0
Jul 16 05:50:17 kiara hcid[32355]: pin_code_request (sba=00:0D:93:14:A3:73, 
dba=00:04:61:85:D5:F0)
Jul 16 05:50:17 kiara hcid[32355]: Calling PasskeyAgent.Request: name=:1.24, 
path=/org/bluez/passkey_agent_32394
Jul 16 05:50:17 kiara hcid[32355]: link_key_notify (sba=00:0D:93:14:A3:73, 
dba=00:04:61:85:D5:F0)
Jul 16 05:50:18 kiara pand[32396]: bnep0 connected
---

-- System Information:
Debian Release: 3.1
  APT prefers stable
  APT policy: (1001, 'stable'), (101, 'testing'), (99, 'unstable'), (9, 
'experimental')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages bluez-utils depends on:
ii  libbluetooth2              3.1-1         Library to use the BlueZ Linux Blu
ii  libc6                      2.3.6-15      GNU C Library: Shared libraries
ii  libdbus-1-2                0.62-4        simple interprocess messaging syst
ii  libdbus-glib-1-2           0.62-4        simple interprocess messaging syst
ii  libglib2.0-0               2.10.2-1      The GLib library of C routines
ii  libusb-0.1-4               2:0.1.12-2    userspace USB programming library
ii  lsb-base                   3.1-10        Linux Standard Base 3.1 init scrip
ii  makedev                    2.3.1-81      creates device files in /dev
ii  module-init-tools          3.2.2-3       tools for managing Linux kernel mo
ii  modutils                   2.4.26-1.2    Linux module utilities
ii  sysvinit                   2.86.ds1-14.1 System-V-like init utilities
ii  udev                       0.093-1       /dev/ and hotplug management daemo

bluez-utils recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: bluez-utils
Source-Version: 3.1-3

We believe that the bug you reported is fixed in the latest version of
bluez-utils, which is due to be installed in the Debian FTP archive:

bluetooth_3.1-3_all.deb
  to pool/main/b/bluez-utils/bluetooth_3.1-3_all.deb
bluez-bcm203x_3.1-3_powerpc.deb
  to pool/contrib/b/bluez-utils/bluez-bcm203x_3.1-3_powerpc.deb
bluez-cups_3.1-3_powerpc.deb
  to pool/main/b/bluez-utils/bluez-cups_3.1-3_powerpc.deb
bluez-pcmcia-support_3.1-3_powerpc.deb
  to pool/main/b/bluez-utils/bluez-pcmcia-support_3.1-3_powerpc.deb
bluez-utils_3.1-3.diff.gz
  to pool/main/b/bluez-utils/bluez-utils_3.1-3.diff.gz
bluez-utils_3.1-3.dsc
  to pool/main/b/bluez-utils/bluez-utils_3.1-3.dsc
bluez-utils_3.1-3_powerpc.deb
  to pool/main/b/bluez-utils/bluez-utils_3.1-3_powerpc.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Filippo Giunchedi <[EMAIL PROTECTED]> (supplier of updated bluez-utils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 25 Jul 2006 12:05:58 +0200
Source: bluez-utils
Binary: bluez-pcmcia-support bluetooth bluez-bcm203x bluez-cups bluez-utils
Architecture: source powerpc all
Version: 3.1-3
Distribution: unstable
Urgency: low
Maintainer: Debian Bluetooth Maintainers <[EMAIL PROTECTED]>
Changed-By: Filippo Giunchedi <[EMAIL PROTECTED]>
Description: 
 bluetooth  - Bluetooth stack utilities
 bluez-bcm203x - Firmware loader for Broadcom 203x based Bluetooth devices
 bluez-cups - Bluetooth printer driver for CUPS
 bluez-pcmcia-support - PCMCIA support files for BlueZ 2.0 Bluetooth tools
 bluez-utils - Bluetooth tools and daemons
Closes: 378446 378836 379200
Changes: 
 bluez-utils (3.1-3) unstable; urgency=low
 .
   * s/PWD/CURDIR/ to avoid sudo FTBFSage, thanks Dato! (Closes: #379200)
   * new handling of outgoing PIN requests: there's a
     /usr/lib/bluetooth/register-passkey script that is invoked by the init
     script, it registers every passkey found in /etc/bluetooth/passkeys via
     the /usr/lib/bluetooth/add-passkey (a modified version of upstream's
     passkey-agent). /etc/bluetooth/pin is converted to
     /etc/bluetooth/passkeys/default if found.
     I hope this Closes: #378446 . README.Debian updated accordingly.
   * fix postinst for bluez-pcmcia-support as we don't ship
     /etc/pcmcia/bluetooth anymore (Closes: #378836)
Files: 
 940773f42fca6dff1737775c9a3e049a 878 admin optional bluez-utils_3.1-3.dsc
 2528046705fac7e27caff816d778254f 27491 admin optional bluez-utils_3.1-3.diff.gz
 32a84d6a7a13b10d186558d36025c371 15690 admin optional bluetooth_3.1-3_all.deb
 9301886b4dd4d05765adb90dc4266e21 257978 admin optional 
bluez-utils_3.1-3_powerpc.deb
 3d24d08d48dda4fb17c75678229bd542 17428 admin extra 
bluez-pcmcia-support_3.1-3_powerpc.deb
 c655b537486d6cd11307f8e1358b5998 22872 admin optional 
bluez-cups_3.1-3_powerpc.deb
 0376fd75bf75e8cc9da3636dcc943da5 21356 contrib/admin optional 
bluez-bcm203x_3.1-3_powerpc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEx0ujABzeamt51AERApWcAJ45ZkKNiEG8qiD49aLgxcFCsMW7LwCgkJJf
9nBgw9Aaaux4cbarlD9vygo=
=cL4H
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to