Comment 12 for bug 6834

Message-ID: <email address hidden>
Date: Mon, 26 Jul 2004 08:56:11 -0400 (EDT)
From: Jayen Ashar <email address hidden>
To: Frank Lichtenheld <email address hidden>
cc: <email address hidden>
Subject: Re: Bug#256314: Found the cause

Is there anything (like a debian policy or something) to prevent/check
this problem in other packages? Like maybe multiple versions of libdb
shouldn't be allowed on a system? Or libdb<4.1 should conflict with
libdb>=4.1? Or perl/DB_File should be linked against a specific
version of libdb? Can this be generalized to other packages/libraries?

Just curious.

--Jayen

On Sun, 11 Jul 2004, Frank Lichtenheld wrote:

> On Sun, Jul 11, 2004 at 12:54:23PM -0400, Jayen Ashar wrote:
> > Okay, I got it. Though perl depends on libdb4.0, other packages (apache
> > apache-common apache-ssl apache-utils apt-build apt-utils bittorrent
> > libdb4.2 libdb4.2-dev libwxgtk2.4-python python python2.3
> > reportbug) depend on libdb4.2, so even though perl was built with the 4.0
> > headers & libs, it's linking against the 4.2 libs at runtime, causing the
> > open command to fail since an argument was removed from the db->open
> > function call.
> >
> > Now my question is, how do I fix this?
>
> Perl in sid is compiled with 4.2. Sit and wait...
>
> Gruesse,
> --
> Frank Lichtenheld <email address hidden>
> www: http://www.djpig.de/
>