[07:53] <wgz> do I need a l-osa to qa a bug watch change, to manually run the update script on qastaging?
[07:57] <wgrant> wgz: Given how trivial that change is, I'd probably avoid QAing it. staging is somewhat designed to not run checkwatches at all, since it can easily DoS remote bugtrackers.
[07:57] <wgrant> And it doesn't have a local debbugs mirror
[07:57] <wgrant> (but yes, if you really want to QA it, you'll need a sysadmin)
[07:58] <wgz> okay, I'll wimp out on your advice then :)
[07:58] <wgrant> :)
[21:09] <cody-somerville> is staging down?
[21:09] <cody-somerville> 'Technically, this is a 503 error and has been caused by our database being temporarily offline. '
[21:11] <cody-somerville> also, https://api.dogfood.launchpad.net/ seems to have an invalid ssl cert
[21:30] <lifeless> cody-somerville: dogfood is expected, its crap
[21:31] <cody-somerville> lifeless, indeed. I'm testing error handling code
[21:31] <cody-somerville> lifeless, so thought it would be perfect :P
[21:31] <cody-somerville> (error handling code in api script that is)
[21:36] <lifeless> this is about the time a staging restore should be taking place, so thats possible
[21:36] <lifeless> however, its sunday, so meh :)
[23:53] <wgrant> lifeless: (yes, staging's meant to be down, as it's restoring and/or failing to restore around now)