From owner-freebsd-questions@FreeBSD.ORG Thu Mar 25 06:34:27 2004 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 DE7E016A4CE for ; Thu, 25 Mar 2004 06:34:27 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAC3143D2D for ; Thu, 25 Mar 2004 06:34:27 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (rwcrmhc12) with ESMTP id <2004032514342601400j4id8e>; Thu, 25 Mar 2004 14:34:26 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id DAE123A; Thu, 25 Mar 2004 09:34:25 -0500 (EST) Sender: lowell@be-well.ilk.org To: Aeefyu References: <4060F9C0.5080102@aeefyu.net> <441xnhkdpz.fsf@be-well.ilk.org> <40623D7B.50403@aeefyu.net> From: Lowell Gilbert Date: 25 Mar 2004 09:34:25 -0500 In-Reply-To: <40623D7B.50403@aeefyu.net> Message-ID: <44brmlq9la.fsf@be-well.ilk.org> Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Probelms and Inconsistencies with 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: Thu, 25 Mar 2004 14:34:28 -0000 Aeefyu writes: > Have been cvsup-ing for couple of days with the same > results. /usr/ports/INDEX is updated correctly, but will have errors > once I run portsdb -Uu. As of yesterday, I am skipping the "portsdb > -Uu" step after cvsup-ing ports-all. This is NOT a correct behaviour > for using portugrade, right? It's not necessarily that bad. As the portsdb(1) manual says: Note: the ports database file is automatically updated if it is not up-to-date when looked up, so manual updating is not mandatory. > But I would imagine this would be a > better alternative that having a /usr/ports/INDEX that has errors in > it. (/usr/ports/INDEX.db would correspondingly have errors too?) No, the errors wouldn't necessarily correspond; they're built by fairly different methods. I don't recall any operations that require you to have both; the standard ports tools only use INDEX, and the portupgrade-related tools only use INDEX.db. [as far as I remember...] When I'm having trouble building an INDEX, I run "make describe" and see where it fails; that usually gives me the information I need to fix it. Good luck.