Comment 15 for bug 2052789

The statement in the bug was correct -- we had not anticipated or thought an apparmor change would get backported to an LTS branch that would necessitate the backport of the functionality in `snap_validate_seed`. but now we have a break, where the HWE of focal (5.15) and LTS of jammy (5.15) got changed to include things.

What is really required is the functionality added to match on ${kern_major_min}, so it's a few commits / bugs deep.

goes back to the origin commit in ubuntu/jammy : bd1690bd16c70f9631ee2798514b51ed2dc973d5

which was never backported because there weren't going to be new kernel versions of 20.04 (5.15 was already out) and we didn't believe there'd be an addition to apparmor that'd break it:

https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2015596

and follow up:

https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2024639

So, i'd say, no, it's not about fixing LP #2038957 specifically, it's about how a kernel change caused us to require the functionality to special case on kernel version. Actually, the original bug doesn't say anything about focal: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384

so this may be a _side effect_. Let me ping that ticket quickly to see if it was intentional to release this to 20.04 5.15 (it's abnormal to put something in LTS Kernel and then _not_ in HWE of $PREVIOUS_SUITE, but it's not listed on the bug)