From owner-freebsd-stable Thu Jan 18 19: 2:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kline-station.ckdhr.com (kline-station.ckdhr.com [209.192.160.22]) by hub.freebsd.org (Postfix) with SMTP id 6633D37B402 for ; Thu, 18 Jan 2001 19:02:35 -0800 (PST) Received: (qmail 9977 invoked by uid 139); 19 Jan 2001 03:02:23 -0000 To: freebsd-stable@FreeBSD.ORG Subject: Re: ports References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> X-Face: I8Alb*-ZdjN\/8k_QR,^l^m6GQB'S-B:}DVP].1HOw#tx:TX$k;Wl;4zqjWR|-jheM#? &beRf(!|0b0m=M~=%.Am>"QEY.(#Ys.%"s?z,hmwp&y0%p>9+T X-Attribution: ckd Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Christopher K Davis Date: 18 Jan 2001 22:02:23 -0500 In-Reply-To: W Gerald Hicks's message of "Thu, 18 Jan 2001 22:48:20 +0000" Message-ID: Lines: 14 X-Mailer: Gnus v5.6.44/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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