>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/19/01, 11:16:50 AM, Dominic Mitchell <[EMAIL PROTECTED]> wrote regarding Re: ports: > On Thu, Jan 18, 2001 at 10:02:23PM -0500, Christopher K Davis wrote: > > W Gerald Hicks <[EMAIL PROTECTED]> 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. You may wish to take a look at the cvsup FAQ found on http://www.polstra.com, and pay attention to the discussion in Q12, Q13. Mutatis mutandis, the same holds for the ports tree. Since ports are tagged "." (ie -CURRENT), one can correctly "sync" them for the first time by adding the *date* keyword (cf cvsup(1) for the exact format): one should specify a date as close as possible to that of "shipping" of one's ports tree. After cvsup has correctly created the ports checkouts file, which is precisely the goal of this first special synch operation, the date field must be removed; all subsequent updates will (ahem, should :-) be performed smoothly. Both approaches (the tool and the correct synching procedure) have been discussed countless times on these lists but, as the saying goes, few people read man pages, and fewer still the mailing list archives... :-) Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message