From owner-freebsd-questions@FreeBSD.ORG Sun Nov 2 05:34:30 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A4E3F9B for ; Sun, 2 Nov 2014 05:34:30 +0000 (UTC) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id 8514C98A for ; Sun, 2 Nov 2014 05:34:27 +0000 (UTC) Received: from ppp118-210-8-90.lns20.adl2.internode.on.net (HELO leader.local) ([118.210.8.90]) by ipmail05.adl6.internode.on.net with ESMTP; 02 Nov 2014 15:59:16 +1030 Message-ID: <5455C12B.10000@ShaneWare.Biz> Date: Sun, 02 Nov 2014 15:59:15 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Mason Loring Bliss , freebsd-questions@freebsd.org Subject: Re: Whence RC4? References: <20141031150107.GY17150@blisses.org> In-Reply-To: <20141031150107.GY17150@blisses.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 05:34:30 -0000 On 01/11/2014 01:31, Mason Loring Bliss wrote: > I've been watching the update servers eagerly since the day RC4 was to begin > building, based on the schedule here: > > https://www.freebsd.org/releases/10.1R/schedule.html > > And yet, http://update.freebsd.org/10.1-RC4/ continues not to exist. 10.1-RC4 exists in svn - https://svnweb.freebsd.org/base?view=revision&revision=273874 It can take a few days before all the binaries are compiled to be ready for release - all arches and ports that are included in iso's need to finish compiling, at which stage iso images will exist on ftp sites and an email will announce the release. A weekend can extend that wait. > I haven't found a public releng coordination mailing list or any real > explanation of the process. Can someone enlighten me? The article > > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html > > talks about binary patchkits existing to match releng/x.y branches, but it > doesn't describe their creation or how such a process might differ for > release candidates. I think this would be explained in - https://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-update-server/index.html > While I'm interested in this, I've also got the secondary goal of exploring > how to move back to using binary patches and freebsd-update after having > built from source for a while. My home desktop is my test case, and it's > currently identifying itself as being 10.1-RC3, built from this at the right > time: > > https://svn0.us-east.freebsd.org/base/releng/10.1 see 'man freebsd-update' - the upgrade command is used to change release versions - RC to release needs an upgrade not just an update > Something I'm not clear on is the possibility of finding a particular point > in time along a branch with Subversion, be it a tag or a date. I still think > in terms of CVS and that seems not to be valid when applied to SVN. It seems > like Subversion has 'svn up -r' to update to a particular revision number, or > a rough date specifier to update to "revision at start of the date". > > How does FreeBSD deal with the lack of CVS-style tags? If one wanted to > recreate a 10.1-RC2 build, for instance, is there a sane way to do it, or > would it involve grovelling through commit logs for clues? Not sure what is officially used - sys/conf/newvers.sh is most likely the file to look at, it's commit log is mostly RC/Beta tags. -- FreeBSD - the place to B...Scaring Daemons Shane Ambler