From owner-freebsd-current Fri Jul 14 6: 9: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id 0592237C31D; Fri, 14 Jul 2000 06:08:58 -0700 (PDT) (envelope-from caa@columbus.rr.com) Received: from blizzard.columbus.rr.com ([204.210.252.252]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Fri, 14 Jul 2000 09:09:21 -0400 Received: from columbus.rr.com (dhcp9559163.columbus.rr.com [24.95.59.163]) by blizzard.columbus.rr.com (8.9.3/8.9.3) with ESMTP id JAA05371; Fri, 14 Jul 2000 09:08:02 -0400 (EDT) Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id JAA02414; Fri, 14 Jul 2000 09:09:32 GMT (envelope-from caa) Date: Fri, 14 Jul 2000 09:09:32 +0000 From: Charles Anderson To: Brian Somers Cc: current@FreeBSD.ORG, John Polstra , Mark Murray , Warner Losh Subject: Re: **HEADS UP** if you used to cvsup the crypto repo from internat ! Message-ID: <20000714090932.B2219@midgard.dhs.org> References: <200007121405.PAA11870@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200007121405.PAA11870@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Wed, Jul 12, 2000 at 03:05:25PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. > -- > 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 -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message