From owner-freebsd-current Tue Aug 12 18:47:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA08181 for current-outgoing; Tue, 12 Aug 1997 18:47:16 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA08172 for ; Tue, 12 Aug 1997 18:47:11 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.6/8.8.5) with ESMTP id SAA06915; Tue, 12 Aug 1997 18:47:07 -0700 (PDT) Message-Id: <199708130147.SAA06915@austin.polstra.com> To: dmaddox@scsn.net Subject: Re: CVSup Suddenly Coredumping In-Reply-To: <19970812191314.21220@scsn.net> References: <19970812191314.21220@scsn.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Tue, 12 Aug 1997 18:47:07 -0700 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <19970812191314.21220@scsn.net>, Donald J. Maddox wrote: > I've been using CVSup to keep this machine -current for quite a while, > and never saw this one before: If I run a CVSup now, it gets through > the whole procedure up to the Apache changes, then I get this: > > ---------------------------------------------------------------------- > > *** > *** runtime error: > *** ASSERT failed > *** file "../src/RCSDelta.m3", line 182 > *** Yes, see my recent posting to -hackers for the full explanation. Briefly, the RCS files in the repository were fiddled in unorthodox ways that confuse CVSup in checkout mode. To recover, you'll need to "rm -rf /usr/ports/www/apache-current" and then run CVSup again. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth