[11:12] <mvo> hey, I was wondering if someone could help me - it looks like core snap builds are quite unhappy right now: https://code.launchpad.net/~snappy-dev/+snap/core - failures and chroot problems is what I see today, any hints what I can do to help?
[11:16] <wgrant> mvo: Ugh, looks like the LXD SRU is bad
[11:16] <wgrant> Or just incompatible
[11:16] <wgrant> I suspect
[11:22] <wgrant> mvo: Ah, you manually requested new builds?
[11:22] <wgrant> Was confused by the amd64 failure, but that's from the primary archive. It looks like someone manually retried, but without using the PPA
[11:23] <wgrant> So it's just the LXD issues on arm64 and armhf
[11:23] <mvo> wgrant: uh, silly me
[11:23] <mvo> wgrant: yes, after the chroot problem I requested builds, that was a mistake
[11:23] <mvo> wgrant: the real issue is the chroot problem for arm/arm64
[11:23] <mvo> armhf/arm64
[11:24] <mvo> (heh, you said it already)
[11:29] <cjwatson> pylxd 5904292b0c82ad0e16181025056aed208f654ac7
[11:30] <cjwatson> actually 17cdd3972bd6413d13c2fc5e4a675a7b8d77450f
[11:31] <cjwatson> so in fact https://github.com/lxc/pylxd/commit/17cdd3972bd6413d13c2fc5e4a675a7b8d77450f
[11:50] <wgrant> Right, images hopefully fixed.
[11:50]  * wgrant stabs all the arm64s and ppc64els
[11:53] <cjwatson> I'm looking into the pylxd SRU.  Just constructing test cases here (I think zesty may need fixing as well, but we'll see)
[11:57] <mvo> wgrant: yay, thanks a bunch. should I try a armhf/arm64 rebuild now?
[11:57] <wgrant> mvo: Yep, should be fine, I think.
[11:58] <wgrant> Just had to revert to old images and ensure new ones wouldn't be produced until we get pylxd fixed.
[12:07] <cjwatson> now to wait for a load of images to download so I can test this
[12:18] <wgrant> mvo: Great, looks like those have both succeeded.
[13:32] <mvo> wgrant: yes, thanks a bunch!
[18:36] <Saviq> hi, can someone please bump ppa:mir-team/dev size again? we seem to be pushing faster than it prunes... :/
[20:25] <cjwatson> Saviq: done
[20:37] <Saviq> cjwatson: thanks