From owner-freebsd-stable@FreeBSD.ORG Thu Aug 23 16:13:37 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBB36106564A for ; Thu, 23 Aug 2012 16:13:37 +0000 (UTC) (envelope-from dg@pki2.com) Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2]) by mx1.freebsd.org (Postfix) with ESMTP id 85CCE8FC48 for ; Thu, 23 Aug 2012 16:13:37 +0000 (UTC) Received: from btw.pki2.com (btw.pki2.com [192.168.23.1]) by btw.pki2.com (8.14.5/8.14.5) with ESMTP id q7NGDXh3097616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Aug 2012 09:13:33 -0700 (PDT) (envelope-from dg@pki2.com) Date: Thu, 23 Aug 2012 09:13:33 -0700 (PDT) From: Dennis Glatting X-X-Sender: dennisg@btw.pki2.com To: kmenzel@whisolutions.com In-Reply-To: <5036497F.7020501@icarz.com> Message-ID: References: <1345697446.84337.11.camel@neo.cse.buffalo.edu> <20120823225855.U33776@sola.nimnet.asn.au> <1345729674.52121.4.camel@bauer.cse.buffalo.edu> <5036497F.7020501@icarz.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-yoursite-MailScanner-Information: Dennis Glatting X-yoursite-MailScanner-ID: q7NGDXh3097616 X-yoursite-MailScanner: Found to be clean X-MailScanner-From: dg@pki2.com Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.1-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2012 16:13:37 -0000 On Thu, 23 Aug 2012, Ken Menzel wrote: > On 8/23/2012 9:47 AM, Ken Smith wrote: >> On Thu, 2012-08-23 at 23:12 +1000, Ian Smith wrote: >>> On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote: >>> >>> > With both the doc and ports repositories now moved to SVN it has been >>> > decided to not export the 9.1 release branch activity to CVS. So >>> > csup/cvsup update mechanisms are not available for updating to 9.1-RC1. >>> > If you would like to use SVN the branch to use is releng/9.1. >>> >>> Assuming the stupid question is the one you didn't ask, just to clarify: >>> does this mean that c*sup won't work with these RCs in particular, or >>> that CVS is dead and SVN becomes mandatory from 9.1-RELEASE? >>> >>> cheers, Ian >>> >> >> The latter. If you are not using FreeBSD-Update to handle the updates >> of a machine you'll need to update your source tree using SVN for >> release branches (releng/*) from now on. Updates of the CVS repository >> will continue for the existing stable/* and head for now. I don't think >> anything has been decided on when that will stop. >> > I missed this announcement as well. > > Should we all use the primary URL or is there a list of mirrors? > > Is anyone going to be updating the Handbook to reflect this? > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html > > However I can see this does not even reflect the more recent use of csup > instead of cvsup. > > I found two good primers: > http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html > http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER > > The second primer in the committer handbook seems to indicate that it is > difficult to run an SVN mirror. This appears to me to be the biggest > drawback. I have been using CVS and perforce for years, but subversion > is new to me. > Thanks. I have several cases where I cannot have machines going to the Internet to update for various reasons, including WAN loading and policies, but I can have them hit local mirrors. I have three sites: #1, Static with less than ten servers. Strong maintenance policies. #2, Mostly static with twenty servers, virtual instances, laptops, and sticks. Loose maintenance policies #3, Largely dynamic but three servers and instances are static. Regulated environment with associated maintenance policies. If CVS is fading then I need to move my CVS mirrors to SVN mirrors.