From owner-freebsd-current Sun Jan 7 8: 8: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 5880037B400 for ; Sun, 7 Jan 2001 08:07:49 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id f07G0Zv14715; Sun, 7 Jan 2001 16:00:36 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id f07G6YR18713; Sun, 7 Jan 2001 16:06:34 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200101071606.f07G6YR18713@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: weird cvs update problem In-Reply-To: Message from Archie Cobbs of "Sat, 06 Jan 2001 17:16:35 PST." <200101070116.f071GZR41032@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Jan 2001 16:06:34 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ISTR Christian Weisgerber was having this problem too. I don't know if there was any fix as such.... > I have a -current system from Dec. 7 on which I'm trying to do > a cvs update in preparation of make world, and am seeing wierd > stuff like this: > > > cvs server: Updating crypto/kerberosIV/appl/afsutil > > U crypto/kerberosIV/appl/afsutil/Makefile.in > > U crypto/kerberosIV/appl/afsutil/aklog.c > > U crypto/kerberosIV/appl/afsutil/kstring2key.c > > U crypto/kerberosIV/appl/afsutil/pagsh.c > > cvs server: Updating crypto/kerberosIV/appl/bsd > > U crypto/kerberosIV/appl/bsd/Makefile.in > > U crypto/kerberosIV/appl/bsd/README.login > > U crypto/kerberosIV/appl/bsd/bsd_locl.h > > U crypto/kerberosIV/appl/bsd/encrypt.c > > U crypto/kerberosIV/appl/bsd/forkpty.c > > U crypto/kerberosIV/appl/bsd/kcmd.c > > U crypto/kerberosIV/appl/bsd/klogin.c > > U crypto/kerberosIV/appl/bsd/krcmd.c > > U crypto/kerberosIV/appl/bsd/login.c > > U crypto/kerberosIV/appl/bsd/login_access.c > > U crypto/kerberosIV/appl/bsd/login_fbtab.c > > U crypto/kerberosIV/appl/bsd/osfc2.c > > U crypto/kerberosIV/appl/bsd/pathnames.h_ > > U crypto/kerberosIV/appl/bsd/rcmd_util.c > > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > > cvs update: warning: unrecognized response ` */' from cvs server > > cvs update: warning: unrecognized response `' from cvs server > > cvs update: warning: unrecognized response `void' from cvs server > > cvs update: warning: unrecognized response `ip_options_and_die (int sock, struct sockaddr_in *fromp)' from cvs server > > cvs update: warning: unrecognized response `{' from cvs server > > cvs update: warning: unrecognized response `#if defined(IP_OPTIONS) && defined(HAVE_GETSOCKOPT)' from cvs server > > cvs update: warning: unrecognized response ` u_char optbuf[BUFSIZ/3], *cp;' from cvs server > > cvs update: warning: unrecognized response ` char lbuf[BUFSIZ], *lp;' from cvs server > > The file data is somehow getting mixed into the "control stream" > or something. The cvs server is a 5.0-20000506-CURRENT machine > that has been working fine for many months (and I don't see the > same problem when cvs updating from other machines). > > I notice that "cvs" was updated to version 1.11 on 10/31/00... > > Has anyone else seen this, and if so, what's the fix?? > > Thanks, > -Archie > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message