From owner-freebsd-current Mon Mar 10 18:02:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA18103 for current-outgoing; Mon, 10 Mar 1997 18:02:21 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA18086; Mon, 10 Mar 1997 18:02:11 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA07571; Mon, 10 Mar 1997 18:00:45 -0800 Date: Mon, 10 Mar 1997 18:00:45 -0800 (PST) From: "Brian N. Handy" To: Chris Timmons Cc: Larry Marso , current@freebsd.org, hubs@freebsd.org Subject: Re: gdb.1proposed solutions. No dice. In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 10 Mar 1997, Chris Timmons wrote: >You know, this may have something to do with the CVS repository fixup >Peter Wemm has done in the last several weeks and the fact that some >people may not have the most recent version of CVSup. John Polstra >mentioned that this could be a problem due to bugs in releases prior to >14.1.1 of CVSup. # ./cvsup -v CVSup client Software version: REL_14_1_1 Protocol version: 14.0 # Actually as I had recalled it the cvsup changes were mostly to the server, not the client. At any rate, I still get the same error with gdb.1 not being found. (Again I just blasted away all the gdb stuff in my tree, re-cvsupped it and ... bleah.) Brian