From owner-freebsd-security Tue Mar 18 08:13:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA01231 for security-outgoing; Tue, 18 Mar 1997 08:13:48 -0800 (PST) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA01223; Tue, 18 Mar 1997 08:13:43 -0800 (PST) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.5/8.8.4) with SMTP id LAA17087; Tue, 18 Mar 1997 11:13:38 -0500 (EST) Date: Tue, 18 Mar 1997 11:13:37 -0500 (EST) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net To: Eivind Eklund cc: jpd@freebsd.org, freebsd-security@freebsd.org Subject: Re: libtermcap fix? In-Reply-To: <3.0.32.19970318163505.00cb37a0@dimaga.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I figured out the problem. What happened is I missed the update come through CVSup and the patch at http://freebsd.org/cgi/cvsweb.cgi/src/lib/libtermcap/tgoto.c?r1=1.4&r2=1.4.2.1 is wrong. It is from a diff -u -r1.4.2.1 -r1.4 when it should be from a diff -u -r1.4 -r1.4.2.1 So apparently this is a bug in the CVS web interface. pbd On Tue, 18 Mar 1997, Eivind Eklund wrote: > That sound like a bug in CVSup. > John? > > I just ran CVSup against cvsup.no.freebsd.org with the original > (non-patched) sources in place (I wrote patch in another directory) - it > picked up the changes just fine.