Bug#218605: apt: misleading dependency problem message
On Sat, 01 Nov 2003 15:21:42 +0000 Henning Makholm <henning@makholm.net>
wrote:
The following packages have unmet dependencies:
autoconf2.13: Depends: autoconf (>= 2.50) but it is not going to be installed
Depends: perl but it is not going to be installed
Depends: libfile-temp-perl
E: Broken packages
$
The message from apt about unmet dependencies is grossly misleading;
I do have all of autoconf (>=2.50), perl and libfile-temp-perl.
I concur.
I've met this annoying, misleading error message. Today I wanted to
check why the wine-development package could not upgrade:
The following packages have unmet dependencies:
wine-development : Depends: wine64-development (>= 6.18~repack-1) but
6.0+repack-4 is to be installed or
wine32-development (>= 6.18~repack-1)
E: Broken packages
wine-development depends on both wine..-developement in the new
6.18~repack-1 version. "But 6.0+repack-4 is to be installed" ? WTF,
The 6.0+repack-4 version is _already_ installed.
$ dpkg -l | grep wine..-deve
ii wine32-development:i386 6.0+repack-4
i386 Windows API implementation - 32-bit binary loader
ii wine64-development 6.0+repack-4
amd64 Windows API implementation - 64-bit binary loader
It would be more useful to tell us what's blocking the upgrade (I
imagine it might be hard to know at the moment the error message
is displayed).
Something as "package xxx not found (not yet in the yyy repository)"
or "package xxx conflicts with installed package yyy". And actions
to take to fix the problem.
Aptitude may have the solution but really the apt error message
isn't helping at all.
Reply to: