[07:51] <sil2100> Hello!
[07:51] <sil2100> We would need to have mir building all required binaries for arm64
[07:52] <sil2100> For xenial+ (so xenial and yakkety essentially)
[07:53] <sil2100> I tried a test build in my xenial-enablement silo but it fails to build due to some files missing during install
[07:53] <sil2100> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-004/+build/10483762
[08:08] <duflu> sil2100: Please join in then: https://bugs.launchpad.net/mir/+bug/1579866
[08:42] <duflu> Europe wakes up, and Launchpad buckles, times out instead of working.
[08:42] <duflu> Time to change focus
[09:04] <sil2100> duflu: thanks! Could someone bump the priority up? Since this is a critical bug from our xenial POV
[09:04] <sil2100> duflu: without this fixed we cannot get xenial arm64 images building for testing
[09:08] <duflu> sil2100: Well I've run out of time to do what I was doing. Will attempt a proposal for you now
[09:08] <duflu> May or may not work
[09:08] <sil2100> duflu: thanks! Just modifying the debian/control parts didn't do the job
[09:09] <duflu> Oh
[09:09] <sil2100> duflu: the link I attached has a build log from that attempt ;)
[09:09] <sil2100> It's missing some files during install
[09:09] <sil2100> So maybe the build system doesn't build something for arm64 that it should?
[09:10] <sil2100> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-004/+build/10483762 <- I used a test MP with the debian/control changes to see where we're at
[09:10] <sil2100> dh_install: missing files, aborting
[09:10] <sil2100> Looks like pretty critical files seem to be missing
[09:15] <duflu> sil2100: Did you also change 'rules'?
[09:15] <duflu> Search armhf
[09:15] <duflu> I'll try...
[09:21] <sil2100> No, I didn't go that 'deep' ;)
[09:28] <duflu> sil2100: Because 'rules' tells it to not build the android platform (drivers)
[09:28] <duflu> I've proposed a branch
[09:28] <sil2100> \o/
[09:28] <duflu> Might not work
[09:28] <duflu> But meeting now
[09:28] <duflu> then EOD probably
[09:28] <sil2100> Yeah, let me forward that to my test branch and rebuild, seeing if it fails on my silo
[09:28] <sil2100> duflu: thanks for looking into that
[09:29] <duflu> No problem
[09:30] <duflu> sil2100: On that note we also have an Nvidia driver and 'rules' tells packaging to not build that either (!?)
[09:30] <duflu> It's also not totally finished
[09:31]  * duflu wonders if Larabel is listening
[18:29] <tedg> bregma: Can one run U8 yakkety in qemu?
[18:31] <bregma> tedg, I don't think so , for lack of Mir-capable drivers (just like on a RasPi)
[18:32] <tedg> bregma: Ah, okay. I thought that I had done it once, but not sure how.
[18:32] <tedg> bregma: Is there a way to do SW rendering?
[18:33] <bregma> I keep asking the Mir guys that and I never get a completely straight answer, but I don't think so
[18:40] <kdub> tedg, I think goldfish, the android emulator, might work (in the sdk?) but haven't used that in a long time
[18:41] <kdub> and iirc, that's qemu-based
[18:42] <tedg> kdub: Cool, we'll look.