Date: Thu, 18 Jan 2001 21:48:11 -0600 From: "David W. Chapman Jr." <dwcjr@inethouston.net> To: <freebsd-stable@FreeBSD.ORG>, "Christopher K Davis" <ckd@ckdhr.com> Subject: Re: ports Message-ID: <020d01c081ca$a4e19d00$931576d8@inethouston.net> 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
yes, that has to be done sometimes and should fix the problem. ----- Original Message ----- From: "Christopher K Davis" <ckd@ckdhr.com> To: <freebsd-stable@FreeBSD.ORG> Sent: Thursday, January 18, 2001 9:02 PM Subject: Re: ports > 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?) > > -- > Christopher Davis * <ckd-sig@ckdhr.com> * <URL:http://www.ckdhr.com/ckd/>; > Put location information in your DNS! <URL:http://www.ckdhr.com/dns-loc/>; > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?020d01c081ca$a4e19d00$931576d8>