From owner-freebsd-hackers Tue Aug 12 16:21:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA00349 for hackers-outgoing; Tue, 12 Aug 1997 16:21:54 -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 QAA00344 for ; Tue, 12 Aug 1997 16:21:51 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.6/8.8.5) with ESMTP id QAA06247 for ; Tue, 12 Aug 1997 16:21:44 -0700 (PDT) Message-Id: <199708122321.QAA06247@austin.polstra.com> To: hackers@freebsd.org Subject: CVSup problems with the apache-current port Date: Tue, 12 Aug 1997 16:21:44 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It has been brought to my attention that some recent reshuffling of the apache ports in the CVS repository has led to assertion failures in CVSup during checkout-mode updates. Some of the RCS files in the master repository were replaced with completely different files, and this caused the problems. In checkout mode, CVSup assumes that "revision 1.1" of a file means the same thing today as it did yesterday. That assumption got violated. The problem affects at least the apache-current portion of the ports tree, and possibly some of the other apache variations too. As far as I know, it affects only people using checkout mode ("tag=." in the supfile). To recover from the problem, do something like this: cd /usr/ports/www rm -rf apache* and then re-run CVSup to bring back those files from scratch. Sorry for the inconvenience. I'll try to make CVSup deal with this class of repository problems better in a future release. Many thanks to Brian Handy and Alexander Indenbaum for reporting the problem to me. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth