14:47 <rbasak> mdeslaur: I spoke with dannf about the same concerns you have in bug 1427406, sorry for not getting you 
               involved at the time.
14:47 <mdeslaur> rbasak: I don't see how we'll be able to maintain updates with those patches
14:47 <rbasak> mdeslaur: we should talk
14:48 <rbasak> mdeslaur: AIUI we essentially agreed that if the patch couldn't be merged it would be dropped. But we 
               should clarify that with dannf.
14:48 <rbasak> (I didn't have security in mind at the time, just normal merges - sorry)
14:49 <mdeslaur> do I publish untested binaries if the patches do merge?
14:49 <mdeslaur> having the patches be arch-specific is a PITA
14:49 <rbasak> Yes - we arranged the patches to apply to the affected architectures only
14:49 <rbasak> That was to minimise risk
14:50 <rbasak> Can't regress an architecture that already has known data corruption
14:50 <rbasak> The theory was that the worst case would be no worse than no carrying the patch
14:50 <rbasak> than not carrying
14:51 <rbasak> Meanwhile the hyperscale team were going to lead efforts to get the bug fixed upstream
14:51 <rbasak> And we didn't expect to be carrying this into 16.04.
14:51 <mdeslaur> is there a trick to actually figuring out if the patches apply?
14:51 <rbasak> You mean in case you get an FTBFS?
14:52 <mdeslaur> no, just to know if they apply or not
14:52 <rbasak> I'm guessing you're not asking about patch --dry-run, so I think I'm failing to understand your question
14:53 <mdeslaur> yes, that's what I'm asking about
14:53 <mdeslaur> is there a way to make quilt apply the arch-specific patches, just to see if they apply
14:53 <mdeslaur> without me having to manually try to apply them
14:53 <rbasak> I'm not sure, sorry. I left that to dannf.
14:54 <rbasak> He's not here. We should get him involved in this conversation.
14:54 <mdeslaur> he's in #ubuntu-server