From owner-freebsd-questions Thu May 24 11:51:37 2001 Delivered-To: freebsd-questions@freebsd.org Received: from relay4.inwind.it (relay4.inwind.it [212.141.53.75]) by hub.freebsd.org (Postfix) with ESMTP id C72A137B422 for ; Thu, 24 May 2001 11:51:29 -0700 (PDT) (envelope-from bartequi@inwind.it) Received: from bartequi.ottodomain.org (62.98.171.110) by relay4.inwind.it (5.5.029) id 3AF9945F004D2F43; Thu, 24 May 2001 20:51:05 +0200 From: Salvo Bartolotta Date: Thu, 24 May 2001 18:53:43 GMT Message-ID: <20010524.18534300@bartequi.ottodomain.org> Subject: Re: cvsup problems? To: Rob Simmons Cc: freebsd-questions@freebsd.org, Wayne Pascoe References: X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ CC-ed to Wayne to kill two birds with one stone ] >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 5/24/01, 6:22:36 PM, Rob Simmons wrote regarding cvsup problems?: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > I've been having problems with cvsup trying to delete > ports/www/jakarta-tomcat/files while it still has files in it. I have= > deleted the entire ports tree, You needn't have done that. Please avoid overloading FreeBSD/FreeBSD-related servers -- unless it is really necessary. The cause of/for the described behavio(u)r is actually quite different. The gory details are found in the -stable archives. > and checked the whole thing out from a > different cvsup server. That works fine. If you later try to cvsup > again, it will stop when it tries to delete that directory, which is n= ot > empty. Exactly. In fact, you didn't attack the real problem. > I have tried this on cvsup11.freebsd.org and cvsup12.freebsd.org. > Any thoughts? In the -stable forum, the issue has been discussed at an **excessive** lenght :-) The finest working solution is probably the following: 1) rm -rf the d****ed jakarta-tomcat port; 2) edit the ports checkouts file removing the few (contiguous) lines containing "jakarta-tomcat"; 3) cvsup your ports tree; 4) [lo and behold] cvsup your ports tree again ;-) It has worked for me (and for others). N.B. If you use cvs to download your repo and checkout your sources, you= should meet with no difficulties at all. Best of luck & best of fun with the ports, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message