From owner-freebsd-stable Thu Jan 18 19:48:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 764A337B400 for ; Thu, 18 Jan 2001 19:48:13 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 32A33177E44; Thu, 18 Jan 2001 21:48:16 -0600 (CST) Message-ID: <020d01c081ca$a4e19d00$931576d8@inethouston.net> From: "David W. Chapman Jr." To: , "Christopher K Davis" References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> Subject: Re: ports Date: Thu, 18 Jan 2001 21:48:11 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes, that has to be done sometimes and should fix the problem. ----- Original Message ----- From: "Christopher K Davis" To: Sent: Thursday, January 18, 2001 9:02 PM Subject: Re: ports > W Gerald Hicks writes: > > > This syndrome is often caused when one uses CVSup to update their ports > > tree a long time after installing from a release. CVSup will not > > normally delete any file it didn't create. Sometimes this will cause a > > stale patch file to be left in a port. > > Would a reasonable test/fix for this be deleting the entire port directory > in question and re-cvsupping? (This should make cvsup recreate everything > and update its file lists, right?) > > -- > Christopher Davis * * > Put location information in your DNS! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message