misc/52122: make release does not use proper binar

David O'Brien obrien at freebsd.org
Thu May 15 18:20:21 PDT 2003

The following reply was made to PR misc/52122; it has been noted by GNATS.

From: "David O'Brien" <obrien at freebsd.org>
To: Ruslan Ermilov <ru at freebsd.org>
Cc: John Hay <jhay at icomtek.csir.co.za>, bug-followup at 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
 > 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.

More information about the freebsd-bugs mailing list