[08:34] lifeless: I'll release it GPL any day now - just need to sync that release with the juju charm merge proposal for reasons. [08:39] stub: ah, Reasons! [08:44] http://zork.net/~nick/pix/reasons.svg <-- lifeless [08:46] Spads: thanks :) [12:13] wgrant: I just noticed that all recipes are going to fail under scalingstack, because buildrecipe specifically checks for Xen. What would your preferred fix for that be? virt-what looks promising, but it isn't in hardy so there's a bootstrapping problem. Maybe add a check for whether /proc/cpuinfo contains "QEMU Virtual CPU"? [12:17] cjwatson: My preferred fix is to delete the check because it's stupid. [12:17] Ha [12:18] I'll prepare you a branch for that then .. [12:18] If I want to compromise a non-virt builder that's accidentally running virt jobs, I can almost as easily escape from a binary build chroot [12:25] Yeah [12:25] I hadn't realised it was added as an alleged security mechanism, but you're right, bug 662664 [12:25] <_mup_> Bug #662664: recipe builds should ensure they run only under xen

[12:27] https://code.launchpad.net/~cjwatson/launchpad-buildd/delete-virt-check/+merge/198242 === Ursinha-afk is now known as Ursinha [12:34] cjwatson: Yeah, I tried to explain that chroots weren't root-safe anyway, but that didn't get very far :) [12:44] Any objection to a launchpad-buildd deployment soon, then? [12:44] (Obviously I should organise some QA first) [12:45] I forget what's pending [12:45] * wgrant looks [12:46] I wonder if infinity has anything else. === wedgwood_ is now known as wedgwood