There should not be much risk of regression - this feature was only
supported on samba in mantic, not jammy etc so not many users will
upgrade from mantic to noble - and the current behaviour where this is
broken in noble is the same behaviour as we have in jammy etc. And then
even for users upgrading from mantic, this feature is about samba
accurately reflecting changes in its configuration into the apparmor
policy - so is only needed if you are making changes to the samba
configuration to add new shares etc.

So I think this is fine for a post-release SRU - no need for it to land
for the actual release.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063079

Title:
  samba smbd.service is missing ExecStartPre for update-apparmor-samba-
  profile

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063079/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to