[199] in athena10
Re: /svn/athena r22957 - trunk/debathena
daemon@ATHENA.MIT.EDU (Timothy G Abbott)
Fri May 2 15:50:21 2008
Date: Fri, 2 May 2008 15:49:36 -0400 (EDT)
From: Timothy G Abbott <tabbott@MIT.EDU>
To: ghudson@mit.edu
cc: athena10@mit.edu
In-Reply-To: <200805021939.PAA08583@drugstore.mit.edu>
Message-ID: <Pine.LNX.4.64L.0805021545090.12351@mega-man.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On note 10, rather than restarting the build, typically we were using
"make -k -j4", so you'd just hit enter in that particular screen window to
acknowledge that we were working on that debathenify package and let it
continue using that one of your 4 build processes (ideally, we'd do make
-k -j, but that requires many more processers than we have). The system
was very much designed under the assumption that one is using "make -k"
and thus the build is not interrupted by a single build failure of some
package, and is the only reason the current behavior with packages under
third/ is acceptable. Sorry I didn't make this clear earlier.
Also, I think you may want to have a step 0 of creating the new
distribution's build chroot and adding the new distribution to
debian-versions.sh.
-Tim Abbott
On Fri, 2 May 2008, ghudson@MIT.EDU wrote:
> Author: ghudson
> Date: 2008-05-02 15:39:52 -0400 (Fri, 02 May 2008)
> New Revision: 22957
>
> Modified:
> trunk/debathena/NOTES
> Log:
> Document current infrastructure for adding a suite.
>
>
> Modified: trunk/debathena/NOTES
> ===================================================================
> --- trunk/debathena/NOTES 2008-05-02 18:46:11 UTC (rev 22956)
> +++ trunk/debathena/NOTES 2008-05-02 19:39:52 UTC (rev 22957)
> @@ -267,3 +267,50 @@
> (A couple of subdirectories of debathena/meta are normal Debian
> packages, so this will create redundant copies of those. Ignore
> them; they won't be used.)
> +
> +Release engineer: Adding a new suite
> +------------------------------------
> +
> +This process is rarely performed and the infrastructure for it is
> +imperfect. Substitute the name of the new suite for "newdist" in all
> +steps below.
> +
> + 1. Create the new distribution in the apt repository's configuration
> + file. Create the skeleton of the dist by installing at least one
> + equivs package from meta/ with "reprepro -Vb $DEBATHENA_APT
> + include newdistname file.changes".
> +
> + 2. On the build server, create a chroot for the new distribution as
> + documented above. This may require downloading and installing a
> + more recent version of the debootstrap package from the
> + -backports dist corresponding to the build server's OS.
> +
> + 3. Set the DEBATHENA_BUILD_AREA environment variable to point to the
> + build area.
> +
> + 4. Fire up screen.
> +
> + 5. mkdir $DEBATHENA_BUILD_AREA/stamps.newdist.
> +
> + 6. cd into a checkout of debathena/scripts/build-server/build-all.
> +
> + 7. Edit Makefile (and check in the edit) so that suite is the new
> + distribution and psuite is the previously most recent Debian or
> + Ubuntu distribution.
> +
> + 8. Run "make deps.mk".
> +
> + 9. Run "make all STAMPS=$DEBATHENA_BUILD_AREA/stamps.newdist". 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.
> +
> + 10. debathenify packages will fail out; they must be built by hand.
> + When the build fails on one, cd into third/packagename in the
> + build area and run "./debathenify newdist-amd64 -A source binary
> + upload" and "./debathenify newdist-i386 binary upload". Then
> + touch $DEBATHENA_BUILD_AREA/stamps.newdist/packagename.done" and
> + restart the build.
> +
> + 11. Go into third/openafs in the build area and build AFS modules
> + for the new suite's kernels. (Instructions pending.)
>
>
