Initially I was also in favor of changing the apparmor profile instead of the samba packaging, but after I saw Michał's MP (with this approach), I'm kind of changing my mind, and here is my reasoning:
With the change to apparmor, all ubuntu users, regardless if they use samba or not, will get the update. All of them, because even though the change is in the bin:apparmor-profiles pacakge, it comes from src:apparmor, which builds many other apparmor binary packages and some of them are installed by default in ubuntu. If instead we made the change in the samba packaging, fixing the binary path, then only samba users would get the update. We can still argue whether it's worth an sru, but at least we could stage the update so it goes out with other more important samba updates. Paride, what do you think? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1979879 Title: Apparmor profile in 22.04 jammy - fails to start when printing enabled Status in apparmor package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Triaged Status in samba source package in Jammy: Triaged Bug description: See bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 Fix was backported, but the path to samba-bgqd is wrong on 22.04. Currently apparmor profile has it like this: /usr/lib*/samba/samba-bgqd When in fact 22.04 has it on /usr/lib/x86_64-linux-gnu/samba/samba- bgqd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1979879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
