[25986] in Source-Commits

home help back first fref pref prev next nref lref last post

Re: /svn/athena r25325 - trunk/debathena

daemon@ATHENA.MIT.EDU (Benjamin Kaduk)
Sat Jul 30 21:38:06 2011

Date: Sat, 30 Jul 2011 21:37:58 -0400 (EDT)
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: Jonathan D Reed <jdreed@MIT.EDU>
cc: source-commits@MIT.EDU
In-Reply-To: <201107300027.p6U0RtJM013144@drugstore.mit.edu>
Message-ID: <alpine.GSO.1.10.1107302137400.7526@multics.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Thanks for updating this.  ACK. (Does that even make sense?)
-Ben

On Fri, 29 Jul 2011, Jonathan D Reed wrote:

> Author: jdreed
> Date: 2011-07-29 20:27:55 -0400 (Fri, 29 Jul 2011)
> New Revision: 25325
>
> Modified:
>   trunk/debathena/NOTES
> Log:
> Clarify some stuff about deleting/staging a chroot
>
> Modified: trunk/debathena/NOTES
> ===================================================================
> --- trunk/debathena/NOTES	2011-07-30 00:22:19 UTC (rev 25324)
> +++ trunk/debathena/NOTES	2011-07-30 00:27:55 UTC (rev 25325)
> @@ -424,7 +424,7 @@
>      the build chroot is not mounted, substituting the name of the
>      volume group for blah.
>
> -  2. Edit /etc/schroot/schroot.conf and delete the section
> +  2. Look in /etc/schroot/chroot.d/ and delete the file
>      corresponding to the chroot.
>
>   3. Run lvchange -an blah/chrootname
> @@ -476,32 +476,38 @@
>      sure there is nothing in svn that isn't built. (An easy way to do
>      this is running the check-unbuilt-packages script.)
>
> -  2. Add the new dist to scripts/debian-versions.sh.  (It is not
> -     necessary to add the new dist to codes at this point, but it must
> -     be present in the gettag conditional.)  If you are building an
> -     unreleased distribution, add an additional ~0.1 tag; if you're
> -     rebilding, bump that tag.
> +  2. Add the new dist to scripts/debian-versions.sh (and svn up into
> +     the locker).  (It is not necessary to add the new dist to codes
> +     at this point, but it must be present in the gettag conditional.)
> +     If you are building an unreleased distribution, add an additional
> +     ~0.1 tag; if you're rebilding, bump that tag.
>
>   3. Create the new distribution in the apt repository's configuration
>      file by editing /mit/debathena/apt/conf/gen-distributions and
>      running it with output to the 'distributions' file in the same
> -     directory.  Create the skeleton of the dist by running "dareprepro
> -     export". (You don't need to do this if you're rebuilding.)
> +     directory.  Create the skeleton of the dist by running
> +     "dareprepro export" on the build server. (You don't need to do
> +     this if you're rebuilding.)
>
>   4. Add an appropriate sources.list.d/*/$suite.list entry in
>      scripts/build-server. Commit and update
>      /mit/debathena/bin/build-server.
>
> -  5. On the build server, create a chroot for the new distribution:
> +  5. On the build server (as root), create a chroot for the new distribution:
>
> -        /mit/debathena/bin/build-server/make-chroot $suite i386
> -        /mit/debathena/bin/build-server/make-chroot $suite amd64
> -
> -     This may require downloading and installing a
> +     First, check if /usr/share/debootstrap/scripts/$suite exists.
> +     If not, it may require downloading and installing a
>      more recent version of the debootstrap package from the
>      -backports dist corresponding to the build server's OS. (You
>      presumably don't need to do this if you're rebuilding.)
>
> +     You could also just go into that directory and do
> +     "ln -s gutsy $suite" since it apparently hasn't changed in years.
> +
> +        /mit/debathena/bin/build-server/make-chroot $suite i386
> +        /mit/debathena/bin/build-server/make-chroot $suite amd64
> +
> +
>   6. Fire up screen.
>
>   7. mkdir /mit/debathena/machines/awesome-build-server/stamps.$suite.
> @@ -519,7 +525,7 @@
>   11. Run "make -k all".
>       You can watch the builds happen in the other windows of the
>       screen session.  It's possible to do several builds at once with
> -      make -j N.
> +      make -j N (except as of 7/2011 this is a bad idea)
>
> Release engineer: Maintaining autodebathenify
> ---------------------------------------------
>
>

home help back first fref pref prev next nref lref last post