From owner-freebsd-hackers Wed Dec 11 21:46:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA19610 for hackers-outgoing; Wed, 11 Dec 1996 21:46:22 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA19600 for ; Wed, 11 Dec 1996 21:46:16 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id VAA14560; Wed, 11 Dec 1996 21:46:10 -0800 (PST) Message-Id: <199612120546.VAA14560@austin.polstra.com> To: mrcpu@cdsnet.net Subject: Re: CVSUP dying Newsgroups: polstra.freebsd.hackers In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Wed, 11 Dec 1996 21:46:10 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article Jaye Mathisen writes: > > trying to sup -current. > > Edit src/release/sysinstall/nfs.c > Add delta 1.12 96.12.11.09.35.04 jkh > Edit src/release/sysinstall/package.c > Add delta 1.50 96.12.11.09.35.04 jkh > @" > Invalid list > file: Invalid integer "~p U|! > > > (Lots of binary characters after that jkh, somehitng about > /usr/sup/src-lib/checkouts.cvs:. Invalid list file: Invalid Integer. It's best to send (or cc) questions like this to "cvsup-bugs@polstra.com". I can usually help, but I don't always keep up with the mailing lists. Anyway, to answer your question, your list file "/usr/sup/src-lib/checkouts.cvs:." is apparently spammed. You can check the file by looking at it with an editor. It's a plain text file and you'll be able to see that it's damaged, I have a feeling. Assuming the list file is damaged, you can just delete it and then re-run CVSup. (But see below.) It will create a new one for you. It's much more efficient to have a list file, but it's not essential for correct operation. In the next CVSup release, I'll fix the error message so that it doesn't try to print out the invalid thing it got. The other question is, how did the file get damaged? I would be surprised if CVSup itself damaged it. It first writes the information to a temporary file, and only renames it after it's been completely and successfully written. Have you noticed any console messages about disk errors lately? If you find that the file in question contains a bad block, _don't_ remove it. Instead, rename it to something else, then fix your bad blocks, then delete the file after that. Otherwise, you'll just release the bad block back into the free list where it could cause further problems. (Been there, done that.) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth