On Wed, May 30, 2007 at 08:52:16PM -0700, Russ Allbery wrote: > This conflict makes no sense to me either, now. libbind-dev and bind-dev > don't include any shared libraries, only static libraries and *.so links > like other well-behaved library packages, and I don't see how they could > possibly cause the resolver used by the system to change.
> Maybe something strange was going on with those packages three years ago > when this was first reported, or even longer ago when Bug#166777 was > reported? > I'm inclined to remove this conflict and see if anything actually breaks. I have a recollection of this conflict actually making sense to me at one point, but I have no record of it in my mail history and can't find anything in bug logs to explain why. There's a good chance that whatever the issue was, something has been fixed in the meantime to be less pathological, making the conflict irrelevant. So I agree with removing it and looking for breakage. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
