From owner-freebsd-questions@FreeBSD.ORG Sun Jan 23 16:44:52 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74DB916A4CE for ; Sun, 23 Jan 2005 16:44:52 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE76D43D39 for ; Sun, 23 Jan 2005 16:44:51 +0000 (GMT) (envelope-from reso3w83@verizon.net) Received: from ringworm.mechee.com ([4.26.84.7]) by out001.verizon.net ESMTP <20050123164450.QIRM28025.out001.verizon.net@ringworm.mechee.com>; Sun, 23 Jan 2005 10:44:50 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id 3C92B2CE743; Sun, 23 Jan 2005 08:41:11 -0800 (PST) From: "Michael C. Shultz" To: Trey Sizemore Date: Sun, 23 Jan 2005 08:41:09 -0800 User-Agent: KMail/1.7.2 References: <1106443760.1123.7.camel@localhost> <200501230830.51867.reso3w83@verizon.net> <1106498400.61888.3.camel@localhost> In-Reply-To: <1106498400.61888.3.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501230841.10791.reso3w83@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [4.26.84.7] at Sun, 23 Jan 2005 10:44:50 -0600 cc: freebsd-questions@freebsd.org Subject: Re: KDE issues after recent portupgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 16:44:52 -0000 On Sunday 23 January 2005 08:40 am, you wrote: > On Sun, 2005-01-23 at 08:30 -0800, Michael C. Shultz wrote: > > To not uninstall them, but to properly upgrade your installed ports > > with > > sysutils/portmanager. > > I'd tried with portupgrade, but it seems that is what caused the most > recent issues. I've not used portmanager before. Would that be a > better alternative to portupgrade? Yes. portupgrade screws up the port registration files when you run pkgdb -F. These are the files in /var/db/pkg/{portname}/+CONTENTS Portmanager does not mess with the registration files and can usually straighten out the damage caused by pkgdb -F. As portmanager runs it gives you good feedback on what it is doing and why, and if you disagree or just question something it is perfectly safe to ctrl-C out of it. When start again and it will just pick up from when you left off. -Mike