This was already fixed in AppArmor 2.10.1
** Changed in: apparmor
Status: Fix Committed => 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/1484178
Title:
Policy cache file mtimes are not being set correctly
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
Oliver Grawert (ogra) reported that Ubuntu Touch image builds were
failing due to incorrect timestamps on pre-compiled policy cache
files.
Starting in AppArmor 2.10, the policy cache file's mtime was meant to be
updated to be equal to the newest mtime detected
on the profile and abstraction files used to generate the policy cache file:
http://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3079
That change was not correct and resulted in the mtime of the policy
cache file to either not be updated (equal to the policy cache file
creation time) or to be updated to an incorrect time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1484178/+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
