[08:57] <rbasak> wgrant: thank you!
[08:58] <wgrant> rbasak: np
[12:19] <Odd_Bloke> cjwatson: If it will make a difference (I'm not sure if all the builders are going to come back all at once and build everything in the queue anyway), please could you bump the priority on https://launchpad.net/~daniel-thewatkins/+livefs/ubuntu/wily/cpc/+build/38783 for me?
[12:27] <cjwatson> Odd_Bloke: Shouldn't be needed, they're all coming back now
[12:35] <cjwatson> This architecture is really good at making lots of stuff fail at once; OTOH it's also pretty good at bringing everything back at once
[12:35] <Odd_Bloke> If you're going to do something, do it with style.
[12:37] <cjwatson> Odd_Bloke: building for you now
[12:37] <Odd_Bloke> Thanks!
[12:56] <cjwatson> Odd_Bloke: Ooh, that appears to have worked.
[12:56] <trash> hi, is there a way to make a mailinglist public? by default only team members can subscribe.
[12:56] <cjwatson> + dd if=binary/boot/filesystem.ext4 of=/dev/mapper/loop0p1
[12:56] <cjwatson> 1894400+0 records in
[12:56] <cjwatson> 1894400+0 records out
[12:56] <cjwatson> 969932800 bytes (970 MB) copied, 16.145 s, 60.1 MB/s
[12:56] <Odd_Bloke> cjwatson: It does, yeah.
[12:57] <Odd_Bloke> "disk size: 261M" from 'qemu-img info' is also a good sign.
[12:57] <cjwatson> trash: The only way to do that is to make a team that anyone can join and have that team own the mailing list.
[12:57] <Odd_Bloke> I'll have a poke at the actual output after lunch, but this is definitely looking good.
[12:57] <cjwatson> (as far as I know)
[12:57] <trash> cjwatson: okay, thanks. Then I'll need to use another solution.
[14:02] <Odd_Bloke> cjwatson: That image output looks fine! \o/
[14:03] <cjwatson> Odd_Bloke: Hooray!  Anything else blocking you?
[14:03] <Odd_Bloke> Nope, just need to keep on chugging through the different output bits we do.
[14:04] <cjwatson> Excellent.  You can race the ppc64el scalingstack redeploy ...
[14:04] <wgrant> Ooh, fancy.
[15:39] <nickoe> Hello.
[15:39] <nickoe> What is the url for the sandbox version of lanuchad?
[15:39] <nickoe> *launchpad
[15:40] <teward> I think it's staging.launchpad.net but don't quote me on that
[15:43] <cjwatson> There are a few
[15:43] <cjwatson> staging is one, qastaging.launchpad.net is also relevant
[15:43] <cjwatson> For most purposes you can use either
[15:44] <cjwatson> They differ in things like exactly what revision of code they're running and when their DB is updated
[15:47] <teward>  right
[15:47] <teward> cjwatson: testing API-based calls to make sure my script(s) work the way they need to is still OK to point at qastaging or staging, especially if I want to double check, right?  (I did this for the mass-closing of Karmic bugs that were on my radars, in a plugin, but want to confirm still xD)
[16:03] <cjwatson> teward: yes, that's absolutely fine, that's one of the things they're for