From owner-freebsd-bugs@FreeBSD.ORG Thu May 15 18:20:21 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 223CB37B401 for ; Thu, 15 May 2003 18:20:21 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB69E43FBD for ; Thu, 15 May 2003 18:20:20 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4G1KKUp048223 for ; Thu, 15 May 2003 18:20:20 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4G1KKex048222; Thu, 15 May 2003 18:20:20 -0700 (PDT) Date: Thu, 15 May 2003 18:20:20 -0700 (PDT) Message-Id: <200305160120.h4G1KKex048222@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "David O'Brien" Subject: Re: misc/52122: make release does not use proper binar X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David O'Brien List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2003 01:20:21 -0000 The following reply was made to PR misc/52122; it has been noted by GNATS. From: "David O'Brien" To: Ruslan Ermilov Cc: John Hay , bug-followup@freebsd.org Subject: Re: misc/52122: make release does not use proper binar Date: Thu, 15 May 2003 18:12:27 -0700 On Fri, May 16, 2003 at 12:01:06AM +0300, Ruslan Ermilov wrote: > > > > In this case the release died near the end (release.9 target). It was > > > > easy to update the running kernel and reboot. Now we wanted to restart > > > > the release w/o starting from scratch. This release build included ports > > > > README's and Docs, and thus takes a very long time to build. To not have > > > > to start from scratch, I did "chroot ${CHROOT} /bin/sh" and then ran "rm > > > > /tmp/.world_done ; /mk" which should have restarted the release build and > > > > done the mimimum work to finish the release. It didn't because of the > > > > cross-release commit that removed the installworld w/in the ${CHROOT}. > > > > This bit not only me, but another person also building an Alpha snapshot. > > > > > > Maybe the issue is more of documentation? I know hindsight makes it easy, > > > but an installworld inside the chroot area or "world DESTDIR=/chrootarea" > > > should have been enough to get the binaries updated. > > > > It is, and was. The problem is restarting with /mk used to do this for > > you. It stopped and the only documentation was hidding in the commit > > log. > > > It used to, but only "if [ ! -f /tmp/.world_done ]", and you were > way beyond that point, was it release.9? Yes as stated clearly above, it was release.9 -- the very last release target. > In older days, it was necessary to ALWAYS upgrade to a recent > before attempting to "make release". So? JKH and msmith at WCCDROM liked it that way. Such issues as this came up in discussions when I worked there.