From owner-freebsd-current Sun Apr 19 18:37:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03316 for freebsd-current-outgoing; Sun, 19 Apr 1998 18:37:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03310 for ; Mon, 20 Apr 1998 01:37:37 GMT (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id SAA10103; Sun, 19 Apr 1998 18:37:28 -0700 (PDT) (envelope-from jdp) Message-Id: <199804200137.SAA10103@austin.polstra.com> To: root@bmccane.maxbaud.net Subject: Re: cvsup messages In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Sun, 19 Apr 1998 18:37:28 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Wm Brian McCane wrote: > I am getting the following errors on various files in -current > when I cvsup them: > > Checksum mismatch -- will transfer entire file Right. Freefall was recently (and temporarily) upgraded to a newer version of CVS. It turned out that this version produced some gratuitous changes to the white space in RCS files that it generated. When CVSup recreated RCS files on client machines during updates, the white space no longer matched the original file on the server. So, even though the files were logically identical, their checksums didn't match. We have reverted freefall to the previous version of CVS while we decide what to do about this. Probably the right solution is to make CVSup ignore white space differences when comparing checksums for RCS files. But to avoid forcing everybody to upgrade to a new version of CVSup, I'm going to try to fix CVS to generate the traditional white space. I had hoped to have that done already, but I haven't had much spare time lately. The important thing to understand is that the RCS file was perfectly OK both before and after CVSup performed the fixup (transferring the entire file.) So there's no need to worry about this. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message