Date: Fri, 19 Jan 2001 10:16:50 +0000 From: Dominic Mitchell <dom@semantico.com> To: Christopher K Davis <ckd@ckdhr.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ports Message-ID: <20010119101650.A27757@semantico.com> In-Reply-To: <w4ae8os0qo.fsf@kline-station.ckdhr.com> References: <F186yAphwFutJLtosJ3000026e1@hotmail.com> <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> <w4ae8os0qo.fsf@kline-station.ckdhr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 18, 2001 at 10:02:23PM -0500, Christopher K Davis wrote: > W Gerald Hicks <gehicks@cisco.com> 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?) Even better would be to use the cvsupchk tool that comes with cvsup (in the contrib directory) to get a list of files that shouldn't be there anyway. Then you can just pass a list to "xargs rm -f". It isn't installed by default, but if you still have a copy of the cvsup tarball in /usr/ports/distfiles, it will be in there. Even the "binary" distributions. -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010119101650.A27757>