From owner-freebsd-questions@FreeBSD.ORG Mon Aug 11 23:19:07 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FEC1106567D for ; Mon, 11 Aug 2008 23:19:07 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout019.mac.com (asmtpout019.mac.com [17.148.16.94]) by mx1.freebsd.org (Postfix) with ESMTP id 7C4C08FC1A for ; Mon, 11 Aug 2008 23:19:07 +0000 (UTC) (envelope-from cswiger@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from cswiger1.apple.com ([17.227.140.124]) by asmtp019.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K5G004OUM3UV040@asmtp019.mac.com> for freebsd-questions@freebsd.org; Mon, 11 Aug 2008 16:19:07 -0700 (PDT) Message-id: From: Chuck Swiger To: Warren Liddell In-reply-to: <200808120857.16732.shinjii@maydias.com> Date: Mon, 11 Aug 2008 16:19:06 -0700 References: <200808120857.16732.shinjii@maydias.com> X-Mailer: Apple Mail (2.928.1) Cc: kde-freebsd@kde.org, freebsd-questions@freebsd.org Subject: Re: KDE4 libssl conflicts X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2008 23:19:07 -0000 Hi-- On Aug 11, 2008, at 3:57 PM, Warren Liddell wrote: > How do i avoid//overturn this conflict ? You've got a mix of older and newer library versions, which makes me think that you are trying to do a partial upgrade of your ports after upgrading the FreeBSD base system to a newer version. You really need to rebuild all ports when doing that, or else you'll run into issues. However, the specific problem you mention should have been resolved by this change here: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126410 ...so please double-check that your ports tree has been updated to get this fix. Regards, -- -Chuck