Comment 7 for bug 2024663

Kinetic is EOL, and the remaining upgrade paths no longer experience this problem *currently*:

jammy or earlier to lunar or later: not affected, because jammy has samba 4.15.13 which is less than 4.16.5 (where the B/R was introduced)
lunar to mantic: not affected, because lunar is already 4.17.7 which has the B/R for << 4.16.5

The only remaining scenario is if jammy or focal get a samba version update, much like kinetic did, that advances its version *past* 4.16.5. Looking at the history of samba upgrades in the security pocket, that could still happen. Focal, for example, was released with 4.11.6, and is currently at 4.15.13.

So at the moment:
- current situation does not exhibit the bug anymore
- when the upgrade is done with do-release-upgrade, which is the recommended way of upgrading an ubuntu release, the bug is worked around by the tool

That being said, current kinetic users, faced with an EOL of their release, will definitely want to upgrade to a supported ubuntu release, and will face this bug if they don't use do-release-upgrade. And since the fix will NOT be in the kinetic release, but in lunar and later, it's perhaps still worth it. I'm on the fence, really, with both by ubuntu developer and SRU team member hats on. Maybe with a block-proposed tag for lunar.

To clarify, restarting samba due to an upgrade can be a big deal (in terms of service interruption), and lunar users would see no benefit in this upgrade. This only benefits who is upgrading from kinetic.