[07:58] <flocculant> balloons: closer \o/ http://i.imgur.com/XuG3sbg.png
[07:58] <flocculant> seems like it falls over in 12.04
[14:58] <gQuigs> what's a good way to simulate a crash for testing apport/whoopsie?
[14:58] <pitti> gQuigs: my standard incandation is: sh -c 'kill -SEGV $$'
[14:59] <pitti> incantation
[14:59] <gQuigs> pitti: awesome, thanks!
[15:12] <balloons> flocculant, ohh good you got it running
[16:30] <flocculant> balloons: almost - no idea what "Setup a site to match your domain, admin/config/services/qatracker/sites" is about :)
[16:30] <flocculant> I was going to edit the wiki - but read only currently
[16:39] <balloons> flocculant, ohh.. just go to the sites tab and make a 'site'
[16:39] <balloons> i guess you've never seen the 'full' admin panel
[16:40] <flocculant> nope - so it doesn't actually have to point to anything with anything like a ip address
[16:40] <davmor2> balloons: is it that ugly :)
[16:41] <flocculant> I'll look shortly - just got a couple of smoke tests to do for trusty
[16:41]  * balloons fires up his copy to look
[16:41] <balloons> davmor2, no.. it's worse
[16:41] <balloons> :-)
[16:41] <flocculant> luckily I hate macs so much I don't have one to test on
[16:42] <davmor2> balloons: hahaha
[16:42]  * flocculant giggles at davmor2 hating them 
[16:44] <davmor2> flocculant: without fail wifi breaks on every new set of installs normally it just fails to install the driver at all, this time it is installing it and ignoring it completely, I'm try the amd64 cd over the amd64+mac now to see if there is any difference I doubt it though
[16:45] <flocculant> yea - read -release
[16:45] <davmor2> flocculant: hence why I hate macs I only have this one because someone has to test it
[16:45] <flocculant> :D
[16:45] <davmor2> flocculant: upgrade went okay
[16:46] <flocculant> cool
[16:47] <davmor2> left them running in vm while I went to bed :)  easiest way to do upgrade tests :D
[16:48] <flocculant> indeed it is :)
[16:48] <flocculant> I didn't get a 14.04 to 16.04 to upgrade
[16:48] <flocculant> but as infinity said something about hwe I didn't look further
[16:49] <flocculant> and Xubuntu doesn't have a 12.04 to upgrade from anymore - not going there :)
[17:03] <balloons> flocculant, yea, just click sites and http://imgur.com/NWBeD0r
[17:04] <flocculant> balloons: thanks :)
[17:31] <jamie1> balloons: sorry to annoy you but can i bug you about aosp stuff for a second?
[17:31] <balloons> jamie1, I'm not sure I have any answers, heh :-)
[17:32] <jamie1> balloons: well you are 1 of 3 people i have met so far on here... lol but i think i have found the stuff required for the z3c build, https://github.com/cyanogenmod/android_device_sony_z3c does that inclued the aosp stuff i need?
[17:35] <flocculant> balloons: ok - that all appears to be in order \o/
[17:36] <jamie1> so i should be able to add that to the devices section and then just modify the device specifics for build then?
[17:37] <balloons> flocculant, brillant. So you can test changes now?
[17:37] <flocculant> I suppose so :)
[17:39] <flocculant> though I'd not know how the first time ofc
[17:40] <flocculant> balloons: is it not possible to import production data? or is that enormous ...
[17:41] <balloons> flocculant, it is possible
[17:43] <flocculant> is it worth it though :)
[17:49] <balloons> all these little things would be nice rolled up into the script
[17:50] <balloons> but.. I think it's fairly easy. You can't do a big import though. so maybe not worth?
[17:52] <balloons> jamie1, I really don't know the answer to that I'm sorry
[17:52] <jamie1> balloons: thanks anywys
[17:52] <balloons> jamie1, however, it's certainly worth trying and seeing what happens
[17:52] <balloons> jamie1, did you talk to some of the other porters?
[17:52] <balloons> or does the guide mention anything?
[17:52] <jamie1> no... and no
[17:58] <flocculant> balloons: seems like some sort of really quietly getting someone trained to deal with tracker merges ...
[17:58] <flocculant> s/going on here
[17:58] <balloons> flocculant, and you can do the same now :-)
[17:59] <flocculant> that's what I was intimating :p
[18:05] <balloons> perhaps simon wants to make the tweaks needed to the script?
[18:05] <balloons> tsimonq2, hacking on a script sound like fun? Could be your first commit
[18:05] <flocculant> which tweaks?
[18:06] <flocculant> nothing it failed with couldn't be dealt with by editing the wiki page
[18:07] <flocculant> eg - Use Trusty as a minimum and what to use to set up http://imgur.com/NWBeD0r
[18:08] <balloons> flocculant, aye, but the script could avoid asking you questions about host for example; it could also load some prod data, or other things
[18:08] <balloons> who knows. At the least, it should be committed to the same repo
[18:08] <flocculant> yea
[18:17] <flocculant> balloons: so logically it would want to be in ubuntu-qa-website/scripts/ I assume
[18:18] <flocculant> might play with that and the script myself actually - could even learn something
[18:31] <gQuigs> can I get this nominated for wily - https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1515446
[18:31] <gQuigs> I already have the fix there
[19:25] <balloons> flocculant, yea I guess that is the logical place
[19:25] <balloons> flocculant, perhaps a readme too
[19:25] <balloons> simple one, but something to point new people to the script
[20:48] <flocculant> balloons: and have the script in launchapd rather than git was what I assumed
[20:49] <balloons> yes, in the bzr repo with the rest of the code
[20:50] <flocculant> right - just checking :)