And it's now provided by Ubuntu and Debian!
..it mostly just points back to the init.d script, but that does lay the
groundwork and prevent it from having to be generated.
Any future improvements I figure should be done in the gitlab (/closes
bug).
** Changed in: apparmor
Status: New => Fix Released
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
--
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/1503762
Title:
Provide systemd service
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor package in Debian:
Confirmed
Status in apparmor package in Gentoo Linux:
Fix Released
Bug description:
AppArmor is in the critical path for bootup for any systems that use
it. Let's specify a systemd service file instead of having systemd
use sysv compatibility mode.
There seems to be a few bugs tracking the precursor this work, like
https://bugs.launchpad.net/apparmor/+bug/1488179, but no actual bug
for the systemd service itself.
AUR has a simple service file, not sure if that would be useful -
https://aur.archlinux.org/packages/apparmor/
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1503762/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
