[Pkg-bluetooth-maintainers] Bug#475656: bluez-utils: Please add dbus to Required-Start

Joerg Platte jplatte at jako.ping.de
Sat Apr 12 07:37:57 UTC 2008


Package: bluez-utils
Version: 3.30-1
Severity: normal

I switched to a dependency based boot sequence using insserv and discovered
that hcid is no longer being started, because /etc/init.d/bluetooth does not
depend on it. Therefore, please add dbus to the Required-Start: dependency
information:

# Required-Start:    $local_fs $syslog $remote_fs dbus

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-rc9 (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bluez-utils depends on:
ii  dbus                         1.2.1-1     simple interprocess messaging syst
ii  libbluetooth2                3.30-1      Library to use the BlueZ Linux Blu
ii  libc6                        2.7-10      GNU C Library: Shared libraries
ii  libdbus-1-3                  1.2.1-1     simple interprocess messaging syst
ii  libglib2.0-0                 2.16.3-1    The GLib library of C routines
ii  libusb-0.1-4                 2:0.1.12-10 userspace USB programming library
ii  lsb-base                     3.2-7       Linux Standard Base 3.2 init scrip
ii  makedev                      2.3.1-87    creates device files in /dev
ii  module-init-tools            3.4-1       tools for managing Linux kernel mo
ii  udev                         0.114-2     /dev/ and hotplug management daemo

Versions of packages bluez-utils recommends:
ii  bluez-audio                   3.30-1     Bluetooth audio support
pn  bluez-gnome                   <none>     (no description available)

-- no debconf information





More information about the Pkg-bluetooth-maintainers mailing list