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 <[EMAIL PROTECTED]> <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 [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
Charles Anderson [EMAIL PROTECTED]
No quote, no nothin'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
