Comment 14 for bug 6834

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

Has anyone else been able to repro this on testing? Or is it just me?

--Jayen

On Mon, 26 Jul 2004, Andrew Suffield wrote:

> On Mon, Jul 26, 2004 at 08:56:11AM -0400, Jayen Ashar wrote:
> > Is there anything (like a debian policy or something) to prevent/check
> > this problem in other packages?
>
> No. It's supposed to work, not break. Nobody's figured out why it
> didn't work in this case, AFAIK.
>
> > > 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.
>
> --
> .''`. ** Debian GNU/Linux ** | Andrew Suffield
> : :' : http://www.debian.org/ |
> `. `' |
> `- -><- |
>