From owner-freebsd-stable@FreeBSD.ORG Mon Sep 20 01:14:42 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB73616A4CE for ; Mon, 20 Sep 2004 01:14:42 +0000 (GMT) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id B86D443D39 for ; Mon, 20 Sep 2004 01:14:42 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.1] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id C2C1E82 for ; Sun, 19 Sep 2004 21:14:41 -0400 (EDT) From: "Brandon S. Allbery KF8NH" To: freebsd-stable@freebsd.org In-Reply-To: <414E2AA5.3060100@yahoo.com> References: <414E2AA5.3060100@yahoo.com> Content-Type: text/plain Message-Id: <1095642880.24031.20.camel@rushlight.kf8nh.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 19 Sep 2004 21:14:41 -0400 Content-Transfer-Encoding: 7bit Subject: Re: library clash: system vs. ports. What to do? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 01:14:43 -0000 On Sun, 2004-09-19 at 20:56, Rob wrote: > ** /usr/local/lib/libcrypto.so.3 is shadowed by /usr/lib/libcrypto.so.3 > /usr/lib/libcrypto.so.3 <- ? > /usr/local/lib/libcrypto.so.3 <- openssl-0.9.7d_1 You got that because you installed/upgraded ports depending on the openssl libraries during the period when the base system's openssl libraries were an older insecure version so the ports system installed the one from ports instead. You can just stay with ports and not have problems unless you use mpd, which as of my last cvsup set a BROKEN="doesn't build against ports openssl" if you had ports openssl installed. I ended up extracting a list of dependent ports with "pkg_info -r openssl\*", "pkg_deinstall -f openssl", then "portupgrade -f" the ports listed by the first command. (However I'm still seeing this with libreadline; haven't yet gone in to see what screwy dependency brought it in or whether I can go back to the system one, or if maybe someone thinks this kind of thing is a *good* idea for some reason. Feh.) -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH