From owner-freebsd-current@FreeBSD.ORG  Mon Mar  1 09:34:37 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2E04516A4CE
	for <current@freebsd.org>; Mon,  1 Mar 2004 09:34:37 -0800 (PST)
Received: from root.org (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id D35D543D41
	for <current@freebsd.org>; Mon,  1 Mar 2004 09:34:36 -0800 (PST)
	(envelope-from nate@root.org)
Received: (qmail 6795 invoked by uid 1000); 1 Mar 2004 17:34:37 -0000
Date: Mon, 1 Mar 2004 09:34:37 -0800 (PST)
From: Nate Lawson <nate@root.org>
To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no>
In-Reply-To: <xzpk724tsyw.fsf@dwp.des.no>
Message-ID: <20040301093344.E6760@root.org>
References: <E1AxpXI-0004Pt-00@hetzner.co.za> <xzpk724tsyw.fsf@dwp.des.no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
cc: Ian Freislich <if@hetzner.co.za>
cc: current@freebsd.org
Subject: Re: openssh compile problem in channels.c
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2004 17:34:37 -0000

On Mon, 1 Mar 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote:
> Ian Freislich <if@hetzner.co.za> writes:
> > For my own sake, I'd like to know how file system corruption could
> > account for many occurences of this problem accross many different
> > computers, unless of course there was a filesystem bug that did it,
> > or the curruption was in FreeBSD's repo and not ours and we just
> > happened to sup a bad copy.
>
> There was no file system corruption.  Some files which were off the
> vendor branch but had no actual changes in them were forcibly returned
> to the vendor branch; channels.c was one of them.  For some reason,
> when this was done, the last revision was removed (it was already
> present on the vendor branch), and sometimes cvsup fails to remove it.

Yes, I agree that this was the problem.

> To those of you who have experienced this - it would be useful to know
> which cvsup mirror you are using, and whether you are using the -s
> cvsup option.

I was using cvsup3 and no -s.

-Nate