> Hi, > I'm failing to see why the bug has been cloned, isn't the fix enough? > bluez-gnome has been rebuilt in sid and uploaded as 0.13-1+b1. > > thanks,
The fix for bluez-gnome is enough, yes, but precisely the same problem affects bluez-utils. I meant to close 435730 (done with this email) but I've been away for a couple of days. $ apt-cache policy bluez-utils bluez-utils: Installed: 3.12-1 Candidate: 3.13-1 Version table: 3.13-1 0 500 ftp://ftp.uk.debian.org unstable/main Packages *** 3.12-1 0 100 /var/lib/dpkg/status $ sudo apt-get install bluez-utils Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies. bluez-utils: Depends: libglib2.0-0 (>= 2.13.5) but 2.12.13-1 is to be installed E: Broken packages Actually, the clone didn't turn out as I expected. Sorry about that. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
pgpISGm3kU6Ay.pgp
Description: PGP signature