From owner-freebsd-questions Tue May 29 8:35:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.wlcg.com (mail.wlcg.com [207.226.17.4]) by hub.freebsd.org (Postfix) with ESMTP id 3C4A937B422 for ; Tue, 29 May 2001 08:35:52 -0700 (PDT) (envelope-from rsimmons@wlcg.com) Received: from localhost (rsimmons@localhost) by mail.wlcg.com (8.11.3/8.11.3) with ESMTP id f4TFaTX33798 for ; Tue, 29 May 2001 11:36:34 -0400 (EDT) (envelope-from rsimmons@wlcg.com) Date: Tue, 29 May 2001 11:36:24 -0400 (EDT) From: Rob Simmons To: freebsd-questions@freebsd.org Subject: cvsup problems continue Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I am still having problems with cvsup bombing when it tries to update ports/www/jakarta-tomcat I have tried the fix that was recommended. To remove the directory for the port, and remove the lines in sup/ports-all/checkouts that refer to this port. After doing this, I have re-run cvsup and everything was successful. I ran it again as was recommended, and it was successful again. Now, my nightly cvsup run still fails in the same port, and I have to go through the process of deleting that port and its lines in the checkouts file etc, etc. Is there a different problem on the cvsup server side that needs to be fixed? Is there another workaround other than adding a line to my refuse file? BTW: I'm not subscribed to this list, please respond to my address in addition to the list. Robert Simmons Systems Administrator http://www.wlcg.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7E8H9v8Bofna59hYRA+4hAKCj+zl1B8lWAulW1q7MsxKElmJiwgCgsa8A 4oMIFcUf02Wn1CAILY0MX7s= =hxbt -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message