[26487] in Source-Commits

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

Re: /svn/athena r25588 - trunk/debathena/scripts/build-server/build-all

daemon@ATHENA.MIT.EDU (Jonathan Reed)
Thu Jun 28 21:28:41 2012

Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <alpine.GSO.1.10.1206282005130.18441@multics.mit.edu>
Date: Thu, 28 Jun 2012 21:28:38 -0400
Cc: source-commits@MIT.EDU
Message-Id: <EFE57305-1D76-4CF9-84D7-DF46CA0184C7@MIT.EDU>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Content-Transfer-Encoding: 8bit


On Jun 28, 2012, at 8:07 PM, Benjamin Kaduk wrote:

> On Thu, 28 Jun 2012, Jonathan D Reed wrote:
> 
>> Author: jdreed
>> Date: 2012-06-28 18:59:17 -0400 (Thu, 28 Jun 2012)
>> New Revision: 25588
>> 
>> Modified:
>>  trunk/debathena/scripts/build-server/build-all/do-build
>> Log:
>> - Revert part of r25586 since we don't in fact want to look at the
>> psuite's -staging repo
> 
> I'm still not sure I fully understand the reasoning, but I'll go with it.

I think my reasoning is:
a) staging should only be used for builds prior to release
b) we are unlikely to ever be building for one suite before the previous one has been released (though I almost kicked off a Quantal build today)
Given (a) and (b), when determining the highest version of a package in the psuite to use in bootstrapping the suite, there should be nothing in the psuite's staging, so we shouldn't need to look there (and if there is something left in the psuite's staging, it is almost certainly Wrong(tm)). 

Basically, the goal of this change was to get do-build to upload to -staging, which is accomplished with the dareprepro calls, which use DEBATHENA_RELEASE.

-Jon

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