Public bug reported: 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. ** Affects: apparmor Importance: Critical Assignee: Tyler Hicks (tyhicks) Status: In Progress ** Affects: apparmor (Ubuntu) Importance: Critical Status: Confirmed ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Importance: Undecided => Critical ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484178 Title: Policy cache file mtimes are not being set correctly To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1484178/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
