[00:05] <sidi> Just wanting to confirm something I strongly suspect: there is no way for Quilt to support patches on or additions of binary files? I'm patching theme packages and need to add additional PNG files.
[00:27] <wgrant> sidi: quilt itself can't, but the 3.0 (quilt) Debian source package format can include extra binaries listed in debian/source/include-binaries.
[15:04] <Odd_Bloke> wgrant: I assume that you are depending on armhf cloud images for ScalingStack, right?
[15:05] <Odd_Bloke> (cjwatson: ^)
[15:08] <Odd_Bloke> Oh, wait, perhaps you're using the arm64 images for the armhf builders.
[15:25] <cjwatson> Odd_Bloke: Right.  We could use the armhf images in principle, but multi-architecture builders can be more efficiently deployed so we'd prefer that.  I believe there's an SRU in process to let us emulate armhf more accurately.
[15:28] <Odd_Bloke> cjwatson: OK, so if we were to drop armhf cloud images in xenial, that wouldn't make you sad?
[15:33] <cjwatson> Odd_Bloke: It *probably* won't affect us, but wgrant is a little more current on this
=== smoser` is now known as smoser
[21:59] <wgrant> Odd_Bloke: Why would you drop armhf cloud images?
[22:00] <wgrant> We don't current use them, but they're pretty handy for testing and it'd be nice to leave the option open/
[22:00] <wgrant> Given they don't even have a bootloader, are they non-trivial to build?
[22:04] <wgrant> Odd_Bloke: (but other consumers of scalingstack, eg. pitti, want to use armhf cloud-images and I'm trying to sort the cloud config out so they can)
[23:23] <sergio-br2> launchpad seems slow today