Stable Release Update Regression/Build Problem

[Scott Kitterman]

On Tuesday 24 June 2008 12:16, Matt Zimmerman wrote:
> On Tue, Jun 24, 2008 at 03:42:15PM +0200, Sebastien Bacher wrote:
> > Le mardi 24 juin 2008 à 14:23 +0100, Matt Zimmerman a écrit :
> > > Agreed, it's sensible to test the update in the same environment to
> > > which it is about to be deployed.
> >
> > Right, that makes sense but is not easy to do. Hardy got quite some
> > updates and it's not really easy to try each combination. Testing one
> > update against hardy-updates is not always correct since sometime
> > several packages are moved to updates the same day and that's this
> > combination that should be tested. Having a way to test installability
> > before copying the binaries to updates would be nice though
>
> That's a good point; exactly mirroring the sequence would force the updates
> to be tested in lock-step, and slow things down.  So perhaps it can't
> always be the exact environment, but I think we should aim for something
> close and do what we can within the constraints we have.
>
> A static check for installability is clearly a good idea in any case.
>

I think I have a sense of it.  I'll work up a diff and run it by the other 
members of motu-sru, ubuntu-sru, and the sru-verification teams.

Scott K