[10:05] <Laney> hey I was just looking at the buildd images published on https://cloud-images.ubuntu.com/buildd/releases/ (specifically the 20.04 one). The manifest says it has cloud-init but it doesn't actually seem to be there in the rootfs, so I don't seem to be able to pass vendor-data to new buildd instances. In fact the images look to have been minimised somehow compared to the manifest alongside, is that right?
[10:05] <Laney> I'm assuming you are using these ...
[10:05] <Laney> and feel free to redirect me to CPC :-)
[10:11] <Laney> the real thing I wanted to do was get snapcraft to pass vendor-data to set a custom archive mirror if given on the commandline, and it's also using these images
[10:12] <tomwardill> errr, I'd have to defer to cjwatson at least there :)
[10:14] <cjwatson> Laney: Yeah, redirecting you to CPC :)
[10:14] <cjwatson> We don't want cloud-init for the chroots and lxd images, but I'd have no problem with it being there for VMs used by snapcraft
[10:15] <Laney> mmm
[10:38] <Laney> ok, the answer for those interested is - those manifests are buggy and that bug is already in the progress of being fixed. the contents of the tarballs and images is correct
[10:39] <cjwatson> Good good
[10:40] <Laney> so my idea of using cloud-init there appears to be a non-starter
[10:40]  * Laney moans
[13:03] <rbasak> Given that I have permission to accept from the Focal proposed queue, if I do a pocket copy from a PPA into the Focal proposed queue, will it get held in Unapproved? I'd like that to "stage" it so as not to interfere with the point release.
[13:04] <cjwatson> rbasak: Yes, unless you use the --auto-approve flag to copy-package (so don't do that)
[13:04] <rbasak> Perfect answer. Thanks :)