From owner-freebsd-ports@FreeBSD.ORG Tue Mar 24 05:39:03 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 012869EF for ; Tue, 24 Mar 2015 05:39:02 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C9ADDB9F for ; Tue, 24 Mar 2015 05:39:02 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2O5fQUd053875; Mon, 23 Mar 2015 22:41:33 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: FreeBSD Ports , Dave Horsfall In-Reply-To: References: From: "Chris H" Subject: Re: Fixing a busted ports area Date: Mon, 23 Mar 2015 22:41:33 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <66d2890a12752bb48480766ae2c19596@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2015 05:39:03 -0000 On Tue, 24 Mar 2015 16:26:30 +1100 (EST) Dave Horsfall wrote > FreeBSD 9.3-RELEASE-p10 (GENERIC) #0: Tue Feb 24 21:01:19 UTC 2015 > > The ports area is broken, due to what I guess was a mangled upgrade path > from FreeBSD 8.x. For example, when installing cups-client, I get: > > pkg-static: pkgconf-0.9.7 conflicts with pkg-config-0.25_1 (installs files > into the same place). Problematic file: /usr/local/bin/pkg-config > *** [fake-pkg] Error code 70 > > It's not clear to me how to fix this. Is the simplest way to just remove > (or move) /usr/ports, install it from CD, then upgrade? I have quite a > few ports installed. You haven't been too specific as to your upgrade path. But sometimes it's as easy as changing to the offending ports folder, and issuing a make deinstall. Then attempting whatever upgrade procedure you following at the time of the incident. However, if this same type of error persists unreasonably. You may require more drastic measures, to overcome the issue(s). --Chris > > -- > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will > suffer." http://www.horsfall.org/spam.html (and check the home page whilst > you're there) _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"