Bug#350591: Let's identify which dependency is problematic

2006-01-31 Thread Steve Langasek
reopen 350591 thanks On Tue, Jan 31, 2006 at 02:10:16PM +0100, Max wrote: > this is the output of the above commands: > max# LANG=C apt-cache policy bluez-utils; LANG=C apt-cache policy > bluez-utils: > Installed: (none) > Candidate: 2.24-1 > Version table: > 2.24-1 0 > 500 htt

Processed: Re: Bug#350591: Let's identify which dependency is problematic

2006-01-31 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reopen 350591 Bug#350591: bluetooth-desktop: fails to install Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs data

Bug#350591: Let's identify which dependency is problematic

2006-01-31 Thread Max
Steve Langasek wrote: > It sounds like you either have something pinned wrong, or you have > an out-of-date package file, that's causing unexpected behavior due > to the dbus library transition i absolutely sure i haven't pinned any package at all, and i update my system on daily basis. so may be

Bug#350591: Let's identify which dependency is problematic

2006-01-30 Thread Filipus Klutiero
Hi, could you please check whether the problem persists after a package lists update (aka apt-get update). If this is the case, please paste the output of the following command: # LANG=C apt-cache policy bluez-utils; LANG=C apt-cache policy libdbus-1-2; It may also be interesting to have the o