[11:22] <SpecialK|Canon> I need to bail on the standup later today because of a store meeting in ZA, sorry
[11:22] <SpecialK|Canon> My main contributions: 1) I'm writing up OCI versioning notes for tomorrow 2) File your expenses from last week please
[11:35] <cjwatson> Waiting for replacement phone to finish downloading a gazillion things over wet string before I do expenses :)
[12:04] <SpecialK|Canon> zoom zoom zoom!
[12:32] <pappacena> Tom is in vacation, and Ioana will take the day... there will be only me and colin at the standup today, then?
[12:33] <SpecialK|Canon> pappacena: relatedly, you have two swap days!
[12:33] <SpecialK|Canon> cjwatson: LP db/model structure as described in https://docs.google.com/document/d/1SheiqNbiiQu376XPWHEccLUupzpT_HPbADRtqp_boUY/edit#heading=h.wtrqreyakykt - how accurate is that now?
[12:36] <pappacena> kristian, I'm thinking about taking Thursday and Friday...
[12:37] <cjwatson> SpecialK|Canon: I've updated it a little
[12:47] <SpecialK|Canon> cjwatson: fab, thank you!
[12:48] <SpecialK|Canon> pappacena: excellent
[12:49] <SpecialK|Canon> cjwatson: do we have a concrete decision on the OCIPS/OCIR linkage?
[12:51] <cjwatson> SpecialK|Canon: I thought it was clear we weren't linking those at least until we had some practical experience with how people use bugs with OCI projects
[12:52] <SpecialK|Canon> cjwatson: sorry, I've fallen into the trap of conflating the two kinds of series again
[12:52] <cjwatson> Adding a recipe name to OCIRecipe allows us to have more than one recipe per project, which we can use for building for multiple channels
[12:53] <cjwatson> I updated my DB patch for that this morning (https://git.launchpad.net/~cjwatson/launchpad/commit/?id=35651746e6218615c1f4259b64f0f0e6c7cbe3ab)
[12:53] <cjwatson> Fairly sure that's in line with my discussions with William last week
[12:55] <SpecialK|Canon> I think I entirely agree with you, I'm just finding all the places where it's important to be specific lest confusion occur, by walking into them again and getting confused - at least my edits should clarify this
[12:56] <SpecialK|Canon> (Thanks!)
[12:59] <cjwatson> Yep
[12:59] <SpecialK|Canon> I've created a new doc that we all have edit rights to at https://docs.google.com/document/d/1vFuBS6ekm14udGFm4H6bHpuWT163kLUBavRM-uj5Aio/edit# and I'm merging in the predecessor with notes from last week
[13:02] <SpecialK|Canon> Anyone happen to know why setting font to "Ubuntu Mono" occasionally makes GDocs treat it like a header in the TOC on the left?
[13:02] <cjwatson> Afraid not.  Last time I hit that I think I worked around it by indenting or making paragraphs longer or something
[14:04] <cjwatson> ultra-short standup :)
[14:05] <pappacena> hahaha! Yes!
[14:05] <cjwatson> probably just as well, I wasn't sure my network was going to hold up with phone + lxd downloading all the things
[15:15]  * cjwatson considers Built-Using some more
[15:16] <cjwatson> I think we probably need to track source name and version separately in the DB rather than using a SourcePackageRelease FK, because in general we don't have a particularly good way to know which SPR a given parsed relationship line refers to - things could get very confusing when PPAs are involved
[15:38] <cjwatson> Hmm, OTOH we do want to check that the SPR exists at upload time
[15:41] <cjwatson> So maybe this looks slightly like the multiple-archive stuff in DSCFile._getFileByName?
[16:25] <cjwatson> Or maybe something involving expand_dependencies