Your message dated Sun, 23 Aug 2009 23:02:06 +0000
with message-id <[email protected]>
and subject line Bug#534319: fixed in blueproximity 1.2.5-4
has caused the Debian Bug report #534319,
regarding blueproximity: bluez-utils is now a transitional package
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
534319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534319
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: blueproximity
Version: 1.2.5-3
Severity: minor
User: [email protected]
Usertags: bluez-utils-transition
Hi,
it seems that blueproximity depends on bluez-utils which is now a
transitional package, please depend on bluez instead (or the
bluetooth metapackage for the whole stack)
--- End Message ---
--- Begin Message ---
Source: blueproximity
Source-Version: 1.2.5-4
We believe that the bug you reported is fixed in the latest version of
blueproximity, which is due to be installed in the Debian FTP archive:
blueproximity_1.2.5-4.diff.gz
to pool/main/b/blueproximity/blueproximity_1.2.5-4.diff.gz
blueproximity_1.2.5-4.dsc
to pool/main/b/blueproximity/blueproximity_1.2.5-4.dsc
blueproximity_1.2.5-4_all.deb
to pool/main/b/blueproximity/blueproximity_1.2.5-4_all.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.
Francesco Namuri <[email protected]> (supplier of updated blueproximity
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.8
Date: Mon, 24 Aug 2009 00:10:35 +0200
Source: blueproximity
Binary: blueproximity
Architecture: source all
Version: 1.2.5-4
Distribution: unstable
Urgency: low
Maintainer: Leo costela Antunes <[email protected]>
Changed-By: Francesco Namuri <[email protected]>
Description:
blueproximity - locks/unlocks your desktop tracking a bluetooth device
Closes: 530454 534319 537551
Changes:
blueproximity (1.2.5-4) unstable; urgency=low
.
* Enhanced the manpage, thanks to Nick Ellery. (Closes: #530454)
* debian/control: added Recommend on librsvg2-common.
(Closes: #537551)
* debian/control: replaced dependency on transitional package bluez-utils
with the dependency on bluetooth package. (Closes: #534319)
* debian/control: Standards-Version bumped to 3.8.3, no changes needed.
* debian/control: added ${misc:Depends} to dependencies to avoid a lintian
warning.
Checksums-Sha1:
718fc7f28f9ca57a5c1aff178fd3a2987fea1595 1377 blueproximity_1.2.5-4.dsc
3ce685ca78379dd0477015f3a2fb91442e08399d 6857 blueproximity_1.2.5-4.diff.gz
13c1fb09f9378d693b056f0b29e8cc986ff015d8 304776 blueproximity_1.2.5-4_all.deb
Checksums-Sha256:
19f3eb19201584e75ff84ebeaf40ed95720704df939a45db3b9a4e168eb9c0fc 1377
blueproximity_1.2.5-4.dsc
c703ba2d027d288839c61a87b510a5386df07b5b0ca1285db98ce8a1794e2b07 6857
blueproximity_1.2.5-4.diff.gz
6c50fd9373d81e43479875f3d8e301b90fbbf789d5df681e75f3ebd2fd5ca13e 304776
blueproximity_1.2.5-4_all.deb
Files:
b530c2eedf720006e7b20be2e1fb471e 1377 admin extra blueproximity_1.2.5-4.dsc
9281b2bd678c5e666abadddfb80e1140 6857 admin extra blueproximity_1.2.5-4.diff.gz
d57dd267597f3fd5b2454695dd1d9939 304776 admin extra
blueproximity_1.2.5-4_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqRyBcACgkQImLTb3rflGYk7gCfVpJtTbU3xQhFbKCiusYshmNC
/k0AnjY0xWg//XhMMhPcnhZ5SdGUw1Qj
=TNd/
-----END PGP SIGNATURE-----
--- End Message ---
