Bug 19235

Summary: building custom release is busted
Product: Base System Reporter: bonk1138 <bonk1138>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-CURRENT   
Hardware: Any   
OS: Any   

Description bonk1138 2000-06-13 07:20:01 UTC
Attempting to do a make release CHROOTDIR=/cvs BUILDNAME=Test-RELEASE CVSROOT=/usr after cvsuping current CVS distribution fails with missing "osreldate.h".

Fix: 

cd /usr and make

This goes against instructions listed on the Web Page
How-To-Repeat: cvsup with default tag=cvs, cd /usr/src/release, make release BUILDNAME=Test-RELEASE CVSROOT=/usr CHROOTDIR=/cvs (Or equivelant) and watch it fail because /usr/src was not built
Comment 1 k 2000-08-03 20:21:24 UTC
Hi James

In the PR you refer to a Web Page with instructions on how to make a release.
I can not find this page can you please give me a pointer to it.

Thanks
Johan K
Comment 2 bonk1138 2000-08-04 13:10:33 UTC
Its under the "For Serious Hackers Only", "Building a custom Release" in any
HTML version of the FAQ.

Try rebooting, Logging in as root, cd /usr/src/release, make release
BUILDNAME=5.0-CURRENT CHROOTDIR=/usr/home/release CVSROOT=/usr/src



-----Original Message-----
From: Johan Karlsson [mailto:k@numeri.campus.luth.se]
Sent: Thursday, August 03, 2000 12:21 PM
To: bonk1138@msn.com
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: misc/19235: building custom release is busted


Hi James

In the PR you refer to a Web Page with instructions on how to make a
release.
I can not find this page can you please give me a pointer to it.

Thanks
Johan K
Comment 3 k 2000-08-04 19:47:00 UTC
Hi

It turned out James is absolutly right :-)

One need to 

# cd /usr/src
# make buildworld
# cd /usr/src/release
# make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release

for the process to work

This was discussed in -stable the last week
see mesg-id 20000802051948.B8263@dragon.nuxi.com

I think the following patch should be applied to the FAQ

Index: doc/en_US.ISO_8859-1/books/faq/book.sgml
===================================================================
RCS file: /home/ncvs//doc/en_US.ISO_8859-1/books/faq/book.sgml,v
retrieving revision 1.82
diff -u -r1.82 book.sgml
--- doc/en_US.ISO_8859-1/books/faq/book.sgml	2000/07/28 01:19:17	1.82
+++ doc/en_US.ISO_8859-1/books/faq/book.sgml	2000/08/04 18:41:21
@@ -9202,6 +9202,8 @@
 
 <para>
 <literallayout>        setenv CVSROOT /home/ncvs        # or export 
CVSROOT=/home/ncvs
+        cd /usr/src
+        make buildworld
         cd /usr/src/release
         make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/rele
ase
       </literallayout>



Can some kind doc-guru please have a look at this.

Thanks
Johan K
Comment 4 jim 2000-08-04 22:26:48 UTC
On Fri, 04 Aug 2000 at 20:47:00 +0200, Johan Karlsson wrote:
> Hi
> 
> It turned out James is absolutly right :-)
> 
> One need to 
> 
> # cd /usr/src
> # make buildworld
> # cd /usr/src/release
> # make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release
> 
> for the process to work
> 
> This was discussed in -stable the last week
> see mesg-id 20000802051948.B8263@dragon.nuxi.com
> 
> I think the following patch should be applied to the FAQ
> 
> Index: doc/en_US.ISO_8859-1/books/faq/book.sgml
> ===================================================================
> RCS file: /home/ncvs//doc/en_US.ISO_8859-1/books/faq/book.sgml,v
> retrieving revision 1.82
> diff -u -r1.82 book.sgml
> --- doc/en_US.ISO_8859-1/books/faq/book.sgml	2000/07/28 01:19:17	1.82
> +++ doc/en_US.ISO_8859-1/books/faq/book.sgml	2000/08/04 18:41:21
> @@ -9202,6 +9202,8 @@
>  
>  <para>
>  <literallayout>        setenv CVSROOT /home/ncvs        # or export 
> CVSROOT=/home/ncvs
> +        cd /usr/src
> +        make buildworld
>          cd /usr/src/release
>          make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/rele
> ase
>        </literallayout>
> 
> 
> 
> Can some kind doc-guru please have a look at this.

I just committed this.

Thanks,

- jim

-- 
jim mock <jim@jmock.com>        work: jim@osd.bsdi.com | jim@FreeBSD.org
http://soupnazi.org/              BSDi Open Source Div | http://bsdi.com
Comment 5 jedgar 2000-08-04 22:30:01 UTC
On Fri, 4 Aug 2000, Johan Karlsson wrote:

> Index: doc/en_US.ISO_8859-1/books/faq/book.sgml
> ===================================================================
> RCS file: /home/ncvs//doc/en_US.ISO_8859-1/books/faq/book.sgml,v
> retrieving revision 1.82
> diff -u -r1.82 book.sgml
> --- doc/en_US.ISO_8859-1/books/faq/book.sgml	2000/07/28 01:19:17	1.82
> +++ doc/en_US.ISO_8859-1/books/faq/book.sgml	2000/08/04 18:41:21
> @@ -9202,6 +9202,8 @@
>  
>  <para>
>  <literallayout>        setenv CVSROOT /home/ncvs        # or export 
> CVSROOT=/home/ncvs
> +        cd /usr/src
> +        make buildworld
>          cd /usr/src/release
>          make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/rele
> ase
>        </literallayout>
> 

Wouldn't it be more appropriate to simply state that a populated /usr/obj
must exist.  The is an unnecessary step for those who track a branch with
some regularity and keep a populated /usr/obj around.

-----
Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve   -   http://www.FreeBSD.org
Comment 6 jim 2000-08-04 22:33:00 UTC
On Fri, 04 Aug 2000 at 17:30:01 -0400, Chris D. Faulhaber wrote:
> On Fri, 4 Aug 2000, Johan Karlsson wrote:
> 
> > Index: doc/en_US.ISO_8859-1/books/faq/book.sgml
> > ===================================================================
> > RCS file: /home/ncvs//doc/en_US.ISO_8859-1/books/faq/book.sgml,v
> > retrieving revision 1.82
> > diff -u -r1.82 book.sgml
> > --- doc/en_US.ISO_8859-1/books/faq/book.sgml	2000/07/28 01:19:17	1.82
> > +++ doc/en_US.ISO_8859-1/books/faq/book.sgml	2000/08/04 18:41:21
> > @@ -9202,6 +9202,8 @@
> >  
> >  <para>
> >  <literallayout>        setenv CVSROOT /home/ncvs        # or export 
> > CVSROOT=/home/ncvs
> > +        cd /usr/src
> > +        make buildworld
> >          cd /usr/src/release
> >          make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/rele
> > ase
> >        </literallayout>
> > 
> 
> Wouldn't it be more appropriate to simply state that a populated /usr/obj
> must exist.  The is an unnecessary step for those who track a branch with
> some regularity and keep a populated /usr/obj around.

Good point, but at some point you need to build world in order to get a
populated /usr/obj :-)  I'll tweak my commit to include a comment about
that though.

- jim

-- 
jim mock <jim@jmock.com>        work: jim@osd.bsdi.com | jim@FreeBSD.org
http://soupnazi.org/              BSDi Open Source Div | http://bsdi.com
Comment 7 Johan Karlsson freebsd_committer freebsd_triage 2000-08-15 09:49:16 UTC
State Changed
From-To: open->closed

FAQ updated in rev 1.84 and 1.85 to also say that  
a buildworld is required when making a release.