From owner-freebsd-current Fri Jul 14 10:15: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 5B83D37B8A8; Fri, 14 Jul 2000 10:14:52 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id SAA93001; Fri, 14 Jul 2000 18:14:47 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id SAA07158; Fri, 14 Jul 2000 18:14:44 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007141714.SAA07158@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Charles Anderson Cc: Brian Somers , current@FreeBSD.ORG, John Polstra , Mark Murray , Warner Losh , brian@Awfulhak.org Subject: Re: **HEADS UP** if you used to cvsup the crypto repo from internat ! In-Reply-To: Message from Charles Anderson of "Fri, 14 Jul 2000 09:09:32 -0000." <20000714090932.B2219@midgard.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jul 2000 18:14:44 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cd /usr/src/whereever && cvs diff or just check your ``cvs checkout'' output for lines beginning with M. > How can I tell if I need to nuke my crypto files? Sounds like I should > have this problem but it doen't look like I do. I looked through the > commits for the past few days searching for crypto, and I have all of the > files that were commited. (secure/lib/libcrypto/Makefile & Makefile.inc from > earlier today & crypto/openssh/ readconf.c, servconf.c, ssh_config, sshd.8, > & /telnet/libtelnet/auth.c from 7/11/00) > > thanks, > -Charlie > On Wed, Jul 12, 2000 at 03:05:25PM +0100, Brian Somers wrote: > > I haven't looked into it too deeply yet because of other source tree > > problems, but if you used to get your crypto ,v files from internat, > > you will suffer some funny problems unless you nuke the old checked-out > > files. > > > > My apologies if this is old news, but I see nothing in UPDATING. > > > > The problem occurs when you cvsup the new crypto-in-src-all sources > > and replace RCS files with different contents and the same version > > number. cvs update/checkout compares the repo version number against > > the checked out version number and considers the file an ``M'' > > (modified source). The file isn't updated and your world gets > > corrupted. > > > > This is probably a candidate for UPDATING. [.....] > -- > Charles Anderson caa@columbus.rr.com > > No quote, no nothin' > -- 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