From owner-freebsd-questions@FreeBSD.ORG Sun Jan 23 17:22:31 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 52DAB16A4CE for ; Sun, 23 Jan 2005 17:22:31 +0000 (GMT) Received: from out014.verizon.net (out014pub.verizon.net [206.46.170.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEC4B43D39 for ; Sun, 23 Jan 2005 17:22:30 +0000 (GMT) (envelope-from reso3w83@verizon.net) Received: from ringworm.mechee.com ([4.26.84.7]) by out014.verizon.net ESMTP <20050123172230.VWMX28388.out014.verizon.net@ringworm.mechee.com>; Sun, 23 Jan 2005 11:22:30 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id 080C12CE743; Sun, 23 Jan 2005 09:18:51 -0800 (PST) From: "Michael C. Shultz" To: freebsd-questions@freebsd.org Date: Sun, 23 Jan 2005 09:18:48 -0800 User-Agent: KMail/1.7.2 References: <1106443760.1123.7.camel@localhost> <200501230841.10791.reso3w83@verizon.net> <1106499211.61888.7.camel@localhost> In-Reply-To: <1106499211.61888.7.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501230918.50191.reso3w83@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out014.verizon.net from [4.26.84.7] at Sun, 23 Jan 2005 11:22:30 -0600 cc: Trey Sizemore 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 17:22:31 -0000 On Sunday 23 January 2005 08:53 am, Trey Sizemore wrote: > On Sun, 2005-01-23 at 08:41 -0800, Michael C. Shultz wrote: > > 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. > > So as a general rule, it appears I would just cvsup my ports as usual > and then use 'portmanager -u' rather than 'portupgrade -arR'. No > more need for portsdb -u and pkgdb -F then? Correct. -Mike