[04:29] <ScottK> infinity: I've uploaded to updates accidentally before.  Long before the britney changes and studd.
[04:30] <ScottK> studd/stuff
[04:37] <infinity> ScottK: Yeah, wgrant dug up stats to prove that it was never disallowed, with some 100ish uploads to *-updates over the last 4 years.
[04:38] <infinity> ScottK: No reason not to fix that now.  I'd rather have Soyuz catch it than rely on me doing so (where I clearly wasn't up to the task earlier) :P
[04:48] <slangasek> it was allowed on the grounds that we thought sometimes it would be urgent to get uploads straight into -updates without the -proposed indirection
[04:56] <infinity> slangasek: Has there ever been such an update where the ~30m delay would have been an issue?
[04:56] <slangasek> I don't know, I'm just saying why it was never blocked
[04:56]  * infinity nods.
[11:53] <jamespage> infinity, thanks for fixing up the section in the eucalyptus packaging
[12:14] <Laney> please reject ^ - forgot -v
[12:20] <cjwatson> Laney: done
[12:20] <Laney> ta
[16:17] <chrisccoulson> jdstrand, (or any other AA), could you please approve the flash upload for raring? :)
[16:17] <jdstrand> sure, I'll do it
[16:18] <jdstrand> chrisccoulson: done
[16:22] <infinity> chrisccoulson: Do we get a new flashplugin-nonfree that picks up that version?
[16:22] <chrisccoulson> infinity, yes
[16:31] <stgraber-uds> infinity, cjwatson: FYI I just finished testing the new rebuild feature for the ISO tracker. python3-qatracker has been updated to match and I've filed an RT ticket. Still need to write a client tool for nusakan to query the rebuild list, trigger and update the status on the tracker.
[16:57] <stgraber> infinity, cjwatson, balloons: self-service rebuild code is now in production. I'll start poking at the nusakan side of things later this week.
[16:58] <infinity> stgraber: Shiny.
[16:58] <Laney> nice
[16:59] <stgraber> I'm not really happy with the way those are visible in the UI though (just "(re-building)" being appended to the product title) but I didn't feel like doing icon design so if someone wants something shinier, patches are welcome.
[17:04] <cjwatson> stgraber: awesome.  next step I guess is to write something to do the inverse of qa_product ...
[17:05] <stgraber> cjwatson: right, the get_list function exported over the API will give us the series name and the product title, so we need to do the inverse of qa_product using that and then trigger the build
[17:06] <stgraber> nusakan will also need to call an update_status function when it starts building (indicating that the rebuild is in-progress and can't be canceled) and then again once it's done
[17:18] <infinity> chrisccoulson: ^^ All your flash uploads have been bounced to partner/release.
[17:55] <jdstrand> infinity: re flash> thanks! :)
[20:25] <stgraber> cjwatson: hey, so I'm looking at doing that reverse qa_product function. It looks to me like we're almost to the point where we could just list all the possiblities into a separate text file (similar to default-arches) and end up with something that's as readable (if not more).
[20:25] <stgraber> do you think that's reasonable or do you really want to keep that as code?
[20:26] <stgraber> thinking of having something like: <qatracker name> <project> <image type> <publish type> <architecture>
[20:26] <stgraber> with the possible addition of a <series> field if we ever need one
[20:29] <cjwatson> stgraber: be my guest
[20:29] <cjwatson> Clearly ought to be table-driven
[22:30] <stgraber> ogra_: around?
[22:31] <stgraber> I'm finishing to port qa_product() from a bunch of if statements to a table in a text file. I'm a bit confused by the Ubuntu Touch entries though
[22:31] <stgraber> do we actually have two different projects being currently built and published under the same name on the tracker?
[22:32] <stgraber> (one apparently using armhf+<codename> as the architecture and the other just using <codename>)