> On Thu, Sep 30, 1999 at 06:18:04PM -0000, Debian Bug Tracking System wrote:
> It's the other way around - wmaker won't accept that version of wmsound, > (it Conflicts: with it). APT's message *is* incorrect, because wmaker > version 0.60.0-4 (which is >= 0.20.2-2) *is* installed. You could understand But you are not operating on wmaker! You asked APT to install wmsound and it told you it couldn't because it could not find a compatible version of wmaker - plain, simple and direct. dpkg tells you that it cannot install wmsound because wmaker prevents it, but that doesn't tell you that there is no newer version of wmaker that can solve the problem. APT always presents the problem viewpoint from the packages that you are manipulating, not from the packages that will be effected by the installation. What it says, is that under ideal conditions with all problems resolved to their fullest extent you cannot install the set of packages because they need XXXX things to be satisified. In this case wmsounds needs wmaker which for some unmentioned reason cannot be installed. The unmentioned reason could be very complicated [a huge conflicts/depends loop, missing versions, whatever] or very simple [a direct conflicts]. > Sorry, but the following packages have unmet dependencies or cause conflicts: > wmsound: Depends: wmaker (>= 0.20.2-2) but it is not going to be installed > > That is avoiding the lie - it is still ambigous, but at least gives a > clearer clue on what could be going on. It is not a lie, your modification makes it a lie. wmsound doesn't cause a conflict it just happens to have one in its relationship to wmaker. The Depends/Conflicts form a loop, you can present the problem from any point in the loop. Jason
