From owner-freebsd-ports Tue Jan 16 3:19:35 2001 Delivered-To: freebsd-ports@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 4A52B37B402; Tue, 16 Jan 2001 03:19:18 -0800 (PST) Received: from localhost (trevor@localhost) by blues.jpj.net (8.11.1/8.10.0) with ESMTP id f0GBJ7a17641; Tue, 16 Jan 2001 06:19:07 -0500 (EST) Date: Tue, 16 Jan 2001 06:19:07 -0500 (EST) From: Trevor Johnson To: Peter Pentchev Cc: Peter Wemm , Satoshi - Ports Wraith - Asami , Will Andrews , Subject: Re: overzealous cleaning of Attics in ports tree In-Reply-To: <20010116124608.A364@ringworld.oblivion.bg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've had several friends run to me for help with exactly this situation - > cvsup'ping yesterday from a 4.1-R ports tree, and winding up with several > unapplicable yet undeleted patches - the CVS and cvsup servers no longer know > anything about these patches, and the cvsup client refuses to delete files > it does not recognize. Thanks for clearing up the mystery of the old > patches lying around; any ideas as to how they can resolve that, short of > rm -rf /usr/ports and pulling in a bright-and-shiny fresh new ports tree? :( > [not always a perfect solution for people on slow modem links.. not too > much good publicity either, I think :(( ] If your friends have access to a place with a better connection, they could check out a copy of the ports tree at that place, then run rsync (ports/net/rsync/) with the --delete option to synchronize their own tree with the remote one. Just downloading a fresh copy would be simpler though, and it's only about 11 MB (I understand that local telephone calls are expensive in some places). -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message