From owner-freebsd-stable Mon Jun 25 19:23:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3278D37B405 for ; Mon, 25 Jun 2001 19:23:06 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f5Q2N2235317; Mon, 25 Jun 2001 19:23:02 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f5Q2N2Y88522; Mon, 25 Jun 2001 19:23:02 -0700 (PDT) (envelope-from jdp) Date: Mon, 25 Jun 2001 19:23:02 -0700 (PDT) Message-Id: <200106260223.f5Q2N2Y88522@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: juha@saarinen.org Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , Juha Saarinen wrote: > On Mon, 25 Jun 2001, John Polstra wrote: > > > Good. When it says it will send the whole file, that should clear > > up any kind of problem. Note, however, that these fixups happen at > > the very end of the cvsup run. If you kill it before it finishes, > > you'll get the same thing on the next run. > > Ahh... at the very end, you say? I wonder if this is due to the > jakarta-tomcat thing? Noticed that 'make update' would bomb out because it > couldn't delete that Port of Infamy ;-) Yep, that would explain it. That jakarta-tomcat thing is going to be the death of me. :-( The "checksum mismatch ..." message is a "should not happen" kind of scenario. It only happens if (a) somebody manually dinked around with the repository files [this case], or (b) somebody manually dinked around with the local files in a very devious way without changing the timestamp, or (c) some internal CVSup error happened. I am not aware of any occurrances of (c) for several years. Anyway, by the time it detects the checksum mismatch, the best it can do is make a note to fix things up at the end. If you kill it (or it dies) before then, the offending file will be unchanged on your machine (i.e., your original version before the update run) and the checksum mismatch will happen again next time. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message