[18:36] <mfo> hey folks, there's an issue w/ casper-md5check that it might ignore fsck.mode=skip (there are reasonable use cases to disable the integrity check in the bug).  it's low impact and has a workaround, so not a biggie, but in case someone has cycles to review the MR in bug 1892369 (and maybe change the 'Fix Released' status for subiquity, which I can't).  thanks!
[18:37] <bdmurray> dbungert: ^
[18:38] <bdmurray> Oh actually if the fix is in casper the subiquity task is irrelevant.
[18:42] <dbungert> bdmurray: some of the commentary talks about serial console and subiquity, I suggest we leave the task for now and perhaps the serial console bit needs a look
[18:42] <dbungert> mfo: I've moved the subiquity status back to New on that bug
[18:42] <mfo> dbungert, thx!
[18:43] <bdmurray> mfo: getting this fixed for Focal won't happen until the next point release so release noting what you've found out about the position of the argument would be useful
[18:44] <mfo> dbungert: hmm, i think the serial console thing was just a side discussion, afaict.  the main issue/thing seems to be casper / skipping the integrity check.  :)
[18:48] <mfo> bdmurray, yes, i'm aware it can't be effectively fixed in focal until the next point release, but i thought of bringing it up as we have to fix it in devel anyway, and maybe already have jammy out w/out this issue.   but i realize the bar is higher per the release schedule.
[18:51] <bdmurray> mfo: Without having looked closely at the code I'm happy with getting this into Jammy
[18:51] <mfo> bdmurray,  cool, thanks for checking this.
[18:53] <bdmurray> Thank you for getting to the bottom of it.