Date: Fri, 14 Jul 2000 09:09:32 +0000 From: Charles Anderson <caa@columbus.rr.com> To: Brian Somers <brian@Awfulhak.org> Cc: current@FreeBSD.ORG, John Polstra <jdp@polstra.com>, Mark Murray <mark@grondar.za>, Warner Losh <imp@FreeBSD.ORG> Subject: Re: **HEADS UP** if you used to cvsup the crypto repo from internat ! Message-ID: <20000714090932.B2219@midgard.dhs.org> In-Reply-To: <200007121405.PAA11870@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Wed, Jul 12, 2000 at 03:05:25PM %2B0100 References: <200007121405.PAA11870@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org> > <http://www.Awfulhak.org>; <brian@[uk.]OpenBSD.org> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000714090932.B2219>