new dapper chroots for -proposed

[Celso Providelo]

On Dec 12, 2007 7:54 PM, Colin Watson <cjwatson at ubuntu.com> wrote:
> On Sun, Nov 11, 2007 at 01:08:06AM +0000, Colin Watson wrote:
> > On Sat, Nov 10, 2007 at 03:29:46PM -0500, Martin Pitt wrote:
> > > Lamont built new dapper buildd chroots which now work with
> > > dapper-proposed, so that linux-backports-modules can finally build. He
> > > put them into chinstrap:~lamont/dapper-proposed, can you please
> > > install them? He also asked to save the old ones.
> >
> > I've done so:
> >
> >   lp_buildd at drescher:~/dapper-proposed/new$ for x in amd64 hppa i386 ia64 powerpc sparc; do manage-chroot.py -s dapper -a $x -f chroot-ubuntu-dapper-$x.tar.bz2 update; done
> >
> > The old chroots are in ~lp_buildd/dapper-proposed/old/ and can be
> > restored using the same procedure.
> >
> > Until this is complete, DO NOT approve any non-proposed uploads! They
> > will build using build-dependencies from -proposed if you do so.
>
> Adam was around and trying to get a grip on the status of our chroots,
> so I reverted to dapper-proposed/old/ since I believe we're done with
> these builds now. If we need to build for dapper-proposed again, we may
> need to re-revert this.
>
> Celso, could you confirm whether or not this bug has been fixed? That
> is, will uploads to dapper-proposed now build with dapper-proposed in
> sources.list, given that they didn't a month ago?

Yes, it's fixed on the builddmaster side.

We pass a proper list of sources.list lines in the 'archives'
argument, following this chart:

{{{
  Pocket    |   Dependencies
  ----------+---------------
    RELEASE | RELEASE
  BACKPORTS | RELEASE SECURITY UPDATES BACKPORTS
   SECURITY | RELEASE SECURITY
    UPDATES | RELEASE SECURITY UPDATES
   PROPOSED | RELEASE SECURITY UPDATES PROPOSED
}}}

Primary archive builds are submitted to ogre-model rules, PPAs don't.

Additionally to RELEASE pocket, PPAs also receive UPDATES and SECURITY pockets.

There are yet two other arguments passed to the slaves:

 'suite' -> plain target suite notation, e.g. 'dapper-proposed' or 'hardy';
 'archive_purpose' -> target archive purpose, e.g 'PRIMARY', 'PPA' or
'SECURITY'.

We are still passing old arguments:

 'ogrecomponent' -> target component name, e.g. 'main', 'multiverse';
 'arch_indep' -> whether or not arch_indep binaries should be built,
True or False.

Ping me on IRC if you have any problem, I hope we still up with the
plan for having single chroots per distroseries.

[]
-- 
Celso Providelo <celso.providelo at gmail.com>