Comment 3 for bug 1965901

So this is a bit of a pickle this SRU. Basically we need to decide on one of the two worlds: staying compliant with what the manufacturers demand (not performing the FCC unlock by default) and not breaking users (as previously modemmanager was automatically performing the unlock). We would probably need to consult someone regarding the legal aspect of automatically unlocking the devices - so it's something we really should do. Since by default we should really REALLY make sure that we're not breaking existing users, but then again - we shouldn't be doing things that are 'not okay' by our main packages as well.

However, in the meantime, I'll review the SRU as-is, without the auto-unlocking, consider pulling it into focal-proposed and then set a block-proposed tag until we know for sure which way to go. We can always patch the package with the unlocks and re-upload, if needed.

A bit of additional data regarding the regression potential of this change, maybe even some pros of just going with 1.118 as-is:
 * From what I know, some of the locked modems (the Lenovo-shipped ones I think?) are already broken by a firmware upgrade right now.
 * Users upgrading to the next LTS (22.04), once upgrades are enabled, will encounter this issue anyway, having to manually perform the unlock.