Bug#186281: libc6 and libdb1-compat mutual dependency

[GOTO Masanori <gotom@debian.or.jp>]

At Tue, 25 Mar 2003 22:06:28 +0100,
Tom Peters wrote:
> Version: 2.3.1-14
> ii  libdb1-compat                 2.1.3-7    The Berkeley database routines [gl

> I came from libc-2.2.4 , and tried to install mysql.  I first did an 
> apt-get upgrade of debian-testing.  Dependencies required installation of 
> libdb1-compat, which happens to be version 2.1.3-7 in debian-testing as of 
> yesterday.
> Although it is for compatibility with programs linked against glibc 2.0 or 2.1,
> apparently it depends on a newer version of libc6 ...
> So that one got partially installed, but could not be configured because
> itself depends on libdb1-compat .  So deadlock, and nothing worked
> anymore...
> 
> After using a rescue disk and some manual copying and symlinking for 
> the newer libc6, configuration was still impossible because of a
> dependency conflict:
> 
> # dpkg --configure libc6
> dpkg: dependency problems prevent configuration of libc6:
> libc6 depends on libdb1-compat; however:
> Package libdb1-compat is not configured yet.
> dpkg: error processing libc6 (--configure):
> dependency problems - leaving unconfigured
> Errors were encountered while processing:
> libc6
> # dpkg --configure libdb1-compat
> dpkg: dependency problems prevent configuration of libdb1-compat:
> libdb1-compat depends on libc6 (>= 2.2.5-13); however:
> Package libc6 is not configured yet.
> dpkg: error processing libdb1-compat (--configure):
> dependency problems - leaving unconfigured
> Errors were encountered while processing:
> libdb1-compat

Hmm, it's bad.  Circular dependency is happened here.

Colin, should we remove "depends: libc6" from libdb1-compat?
libc6 and libdb1-compat are "priority: required" files, so 
removal of depends libc6 does not cause problem, I think...

> Solution: --force-depends for libc6

or "dpkg --configure libdb1-compat libc6"?

Regards,
-- gotom