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 

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 

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

Reply via email to