Comment 6 for bug 1979879

I see your point, and I find the one about "fixing it the Kinetic way" especially convincing, it may save us headaches in the future, and may help with backports. My concern is that other packages or scripts users wrote and tested on Jammy systems refer to the "wrong" path (/usr/lib/x86_64-linux-gnu/...). If we want to fix samba I think this is the commit to cherry-pick

https://salsa.debian.org/samba-team/samba/-/commit/3e8438ca59263aee8a2599b47a0dccf2d395e1f4

Note that speaking of binaries the commit message says

  Some of them are callable from other packages, and some
  others are specified in config files.

and that's what I'm a bit worried about. OTOH there may be packages in Ubuntu that got merged from Debian and that already refer to the "right" (libexec/...) path. So I think that to make fixing samba definitely safer/better than fixing apparmor we should

 - Check which binaries are affected by the path change
 - Check how they're meant to be user facing
 - Check if and how other packages are calling them.
   https://codesearch.debian.net/ may help here.