Control: tags -1 moreinfo Hi Noah, On 02-04-2021 22:00, Noah Meyerhans wrote: > Please unblock package debian-cloud-images 172 files changed, 3798 insertions(+), 1365 deletions(-) > Primarily I'm requesting this because this source package provides the > debian-cloud-images-packages package that is a key package (see > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929214) and updating the > package in bullseye will update the Depends list to match what is actually > required to build cloud images today. Ack. > This package contains a snapshot of the code and configuration used by the > cloud team to generate the images for azure, aws, and openstack. The cloud > team does not build directly from the packages in the archive, but rather > from the salsa repository. So there is no risk of impact to the cloud > images we generate if this package is updated. Keeping the archive package > closer to what's actually used by the cloud team is beneficial to any users > who might be generating their own images based on our configuration. So, I'm very uncomfortable with the union of this key packages tracking package and the actual snapshot package. debian-cloud-images:all is a new upstream release which doesn't follow our freeze policy at all, so I think this should be a NACK. I'm also wondering, technically, do you need the build dependencies of src:debian-cloud-images to be key too to release the cloud images, or should is suffice to guarantee the Depends of debian-cloud-images-packages to be in the next release? If I spot correctly, of the three newly added Depends only fdisk is currently not key yet, BD python3-yaml is also not a key package yet. Should the current package in testing be released with bullseye if we don't update it? Paul
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature