Your message dated Tue, 14 Nov 2006 10:32:10 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#392260: fixed in bluemon 1.4-1
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: bluemon
Version: 1.3-1.2
Severity: serious
In its default install, bluemon hooks into the bluetooth stack with a
fake macaddress, causing at least kbluetoothd to stop working at all.
One could argue it's either of the two, and that by installing bluemon
you want it as a service, but... in the default install, it doesn't work
anyway (needs configuration), also, I do happen to believe that if
bluemon is conflicting with the proper working of kdebluetooth, it
should either conflict, or probably better, just not be enabled by
default and list appropriate warnings in /etc/default/bluemon on what
enabling would entail.
--Jeroen
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages bluemon depends on:
ii bluez-utils 3.5-1 Bluetooth tools and daemons
ii libbluetooth2 3.5-1 Library to use the BlueZ Linux Blu
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libdbus-1-3 0.92-2 simple interprocess messaging syst
bluemon recommends no packages.
-- no debconf information
--
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
--- End Message ---
--- Begin Message ---
Source: bluemon
Source-Version: 1.4-1
We believe that the bug you reported is fixed in the latest version of
bluemon, which is due to be installed in the Debian FTP archive:
bluemon_1.4-1.diff.gz
to pool/main/b/bluemon/bluemon_1.4-1.diff.gz
bluemon_1.4-1.dsc
to pool/main/b/bluemon/bluemon_1.4-1.dsc
bluemon_1.4-1_i386.deb
to pool/main/b/bluemon/bluemon_1.4-1_i386.deb
bluemon_1.4.orig.tar.gz
to pool/main/b/bluemon/bluemon_1.4.orig.tar.gz
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.
Matthew Johnson <[EMAIL PROTECTED]> (supplier of updated bluemon 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, 14 Nov 2006 13:36:50 +0000
Source: bluemon
Binary: bluemon
Architecture: source i386
Version: 1.4-1
Distribution: unstable
Urgency: low
Maintainer: Matthew Johnson <[EMAIL PROTECTED]>
Changed-By: Matthew Johnson <[EMAIL PROTECTED]>
Description:
bluemon - Activate or deactivate programs based on Bluetooth link quality
Closes: 359240 392260
Changes:
bluemon (1.4-1) unstable; urgency=low
.
* New Upstream Release
* Don't enable by default. (Closes: #392260)
Patch from Jeroen van Wolffelaar <[EMAIL PROTECTED]>
* Starting with default config file confirmed working
(Closes: #359240)
Files:
95a4974f947b2ea6c2af37fe534c697e 632 net optional bluemon_1.4-1.dsc
0a81c0abdae492c211be0fe6cda69ab4 25987 net optional bluemon_1.4.orig.tar.gz
70424eaaa3980ce5768db713fbafe1e5 6203 net optional bluemon_1.4-1.diff.gz
0b6da8cd93aec5d4302a8cfc9a716296 24408 net optional bluemon_1.4-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFWgcVCw8pKd+B7oMRAuelAKCA0GmJ/hbY+Wq8oRxzrkwkog4lLwCgusii
duiDVVD/IuSJ4YwlNqz4st4=
=e3nE
-----END PGP SIGNATURE-----
--- End Message ---
