Re: unment dependencies - force?

[Jamin W.Collins <jcollins@asgardsrealm.net>]

On Tue, 22 Oct 2002 12:04:25 -0700 Curtis Vaughan <curtis@npc-usa.com>
wrote:

> I believe this is because I have a partial testing/woody environment 
> that I often get errors when trying to configure certain applications 
> like the following.  My question is, what can I do when I get such 
> errors. Is it advisable to force installation?

Nope.  There are better ways.  Let's examine the cited problem:

> Sorry, but the following packages have unmet dependencies:
>   libglib1.2-dev: Depends: libglib1.2 (= 1.2.10-4) but 1.2.10-6 is to be

Looking at the output of "apt-cache policy libglib1.2" on my system I see
the following:

libglib1.2:
  Installed: 1.2.10-6
  Candidate: 1.2.10-6
  Version Table:
 *** 1.2.10-6 0
        990 http://216.37.55.114 testing/main Packages
        500 http://216.37.55.114 unstable/main Packages
        100 /var/lib/dpkg/status
     1.2.10-4 0
        500 http://216.37.55.114 stable/main Packages

This would seem to indicate that something on your system is attempting to
pull libglib1.2 from testing or unstable.  However since the
libglib1.2-dev package you have currently installed requires the current
version of libglib1.2, it's indicating that it will be removed.  You can
stop this by adding "libglib1.2-dev/testing" to your "apt-get install"
line.  This will upgrade libglib1.2-dev to the version compatible with the
version of libglib1.2 being installed.

-- 
Jamin W. Collins