From owner-freebsd-qa Tue Mar 27 14:48:45 2001 Delivered-To: freebsd-qa@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5B94537B71A for ; Tue, 27 Mar 2001 14:48:42 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2RMmfh97428 for ; Tue, 27 Mar 2001 17:48:41 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 27 Mar 2001 17:48:41 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-qa@FreeBSD.org Subject: cvsupit? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know much/anything about cvsupit, but I've seen two comments in the past 48 hours that users who installed 4.2-RELEASE ended up with problems in cvsup-files generated by cvsupit not including the required crypto lines to pull down a buildable source tree. It's quite possible there was operator error in these situations, on the other hand, it's easy to imagine that tools dealing with cvsup files might get out of sync with our changing notion of the required/available cvs repository modules. Probably, someone who has cvsup clue should check to make sure that all the sample cvsup files in /usr/share/examples/cvsup, the cvsupit tool, and the reality on cvsup servers, all match up. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message