From owner-freebsd-current Wed Jul 12 7:23: 5 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 613DA37BB7A; Wed, 12 Jul 2000 07:22:56 -0700 (PDT) (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 PAA11870; Wed, 12 Jul 2000 15:05:25 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200007121405.PAA11870@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@FreeBSD.org Cc: Brian Somers , John Polstra , Mark Murray , Warner Losh Subject: **HEADS UP** if you used to cvsup the crypto repo from internat ! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Jul 2000 15:05:25 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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