From owner-freebsd-stable Thu Feb 24 1: 0:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from csmd2.cs.uni-magdeburg.de (csmd2.CS.Uni-Magdeburg.De [141.44.22.2]) by hub.freebsd.org (Postfix) with ESMTP id 5C6C437BBAF; Thu, 24 Feb 2000 01:00:26 -0800 (PST) (envelope-from jesse@mail.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (jesse@knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.9.3/8.9.3) with ESMTP id KAA12339; Thu, 24 Feb 2000 10:00:24 +0100 (MET) Received: (from jesse@localhost) by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id JAA00161; Thu, 24 Feb 2000 09:59:25 +0100 (MET) Date: Thu, 24 Feb 2000 09:59:25 +0100 From: Roland Jesse To: Kris Kennaway Cc: Oscar Bonilla , freebsd-stable@FreeBSD.org Subject: Re: Error building freshly cvsuped libcrypt Message-ID: <20000224095925.B29660@knecht.cs.uni-magdeburg.de> References: <20000221195356.A68482@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > The original person was probably cvsupping his secure/ sources to > -CURRENT, not -STABLE. That was me, and yes it's true. I cvsupped src-all using tag=RELENG_3 and crypto using RELENG=. That's what happens when one simply copies over the provided cvsup file examples without checking their settings in detail. Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message