Comment 20 for bug 1758647

There was a misunderstanding there: I never suggested we should use xkb-keymap instead (or at least, that's not the message I was trying to convey).

The intent was to reduce delta by not removing so much code, when console-setup merges are already difficult. I didn't foresee that some of that code setting a default would impact ubiquity (because ubiquity does things specially with d-i components, sometimes running them multiple times). There's always a need to update ubiquity after changing d-i components; it's inevitable since some of them are embedded in ubiquity source.

The removals of xkb-keymaps aren't ubiquity-specific: we don't use this code in d-i, and instead use multiple screens to change keyboards. That's a conscious decision.

The point for supporting xkb-keymap "in ubiquity" is more about making sure that we either "rebuild" the value based on layoutcode/variantcode, or otherwise unset it before running the configuration script -- ie. leave it in, but just explicitly ignore its values.