Thanks for the bug report! This only seems to affect the apparmor package that was SRU'ed to trusty from xenial. Xenial doesn't look to be affected.
** Changed in: apparmor (Ubuntu) Importance: Undecided => Medium ** Changed in: apparmor (Ubuntu) Status: New => Confirmed ** Also affects: apparmor (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu Trusty) Status: New => Confirmed ** Changed in: apparmor (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: apparmor (Ubuntu) Status: Confirmed => Invalid -- 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/1661406 Title: apparmor failing to be purged on trusty Status in apparmor package in Ubuntu: Invalid Status in apparmor source package in Trusty: Confirmed Bug description: Version: 2.10.95-0ubuntu2.5~14.04.1 When executing apt -y purge apparmor. The purge run but has errors as files do not exist and the rmdir fails to execute. rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or directory Steps to reproduce: apt-get update apt-get -y install apparmor apt -y purge apparmor I will put workarounds in place for now in puppet but this is making puppet not like it.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1661406/+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