Re: Adding new packages to the key package list

[Niels Thykier <niels@thykier.net>]

On 2015-05-13 22:56, Thomas Goirand wrote:
> Dear release team,
> 
> Right now, the release management includes building an image for
> OpenStack. To do this, we need openstack-debian-images and all of its
> (build-)depends, plus all of the packages it installs in the image. The
> list of packages is as follow:
> 
> [...]
> 
> I guess lots of the above are already marked as key packages, so without
> checking, this would make the below list:
> 
> euca2ools, file, kbd, cloud-init, cloud-utils, openstack-debian-images,
> cloud-initramfs-tools
> 
> [...]
> 
> I'd like to suggest to make these as key packages, so that the process
> of building the OpenStack image weekly doesn't break, which would break
> the whole process which also builds the ISO images.
> 
> Your thoughts?
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 
> 

I think this looks entirely reasonable that they are promoted to key
packages for as long as we use them for building install media.

 * I suppose we should also add a faux package for these packages to
   help Britney prioritise that it remains installable.


~Niels