From owner-freebsd-current Fri Dec 26 15:31:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA12812 for current-outgoing; Fri, 26 Dec 1997 15:31:10 -0800 (PST) (envelope-from owner-freebsd-current) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA12807 for ; Fri, 26 Dec 1997 15:31:02 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id PAA16283; Fri, 26 Dec 1997 15:30:45 -0800 (PST) (envelope-from jdp) Message-Id: <199712262330.PAA16283@austin.polstra.com> To: pechter@lakewood.com Subject: Re: anyone ever see this from cvsup? In-Reply-To: <199712261743.MAA00657@i4got.lakewood.com> References: <199712261743.MAA00657@i4got.lakewood.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Fri, 26 Dec 1997 15:30:44 -0800 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199712261743.MAA00657@i4got.lakewood.com>, Bill Pechter wrote: > Anyone ever get this one? > > *** runtime error: > *** Exception "RCSError.E" not in RAISES list > *** > > I just picked up this error after CVSUP crashed on my machine. Well, reports like this have little value unless you include details such as the version of CVSup you were using, the version of FreeBSD it was running under, what command line you used to invoke the program, and the contents of your cvsupfile. Also, please report CVSup problems to cvsup-bugs@polstra.com. This particular problem is always caused by a corrupted RCS file. However, recent versions of CVSup handle such problems more robustly than older versions. If "cvsup -v" doesn't say it's version REL_15_2, then you're running an old version. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth