This bug was fixed in the package apparmor - 2.3.1+1403-0ubuntu27.3
---
apparmor (2.3.1+1403-0ubuntu27.3) karmic-proposed; urgency=low
* parser/parser_main.c: check ctime instead of mtime, since dpkg will
install profiles with their publication dates, not install dates
(LP:
** Tags added: verification-done
** Tags removed: verification-needed
--
apparmor cache files not regenerated on upgrade
https://bugs.launchpad.net/bugs/466315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Accepted apparmor into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Committed
** Description changed:
+ impact: people upgrading from Jaunty to Karmic will see some services fail to
start due to outdated profiles not correctly being loaded (specifically, this
happens for bind9).
+ how the bug ha
** Description changed:
Binary package hint: bind9
If you have installed apparmor, and install bind9, this fails to start
complaining about access denied (openssl.cnf file the first time,
named.pid in other configurations).
The problem is that bind9 doesn't install an apparmor prof
** Changed in: apparmor (Ubuntu)
Status: Triaged => In Progress
--
apparmor cache files not regenerated on upgrade
https://bugs.launchpad.net/bugs/466315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Summary changed:
- bind9 apparmor cache files not regenerated on upgrade
+ apparmor cache files not regenerated on upgrade
--
apparmor cache files not regenerated on upgrade
https://bugs.launchpad.net/bugs/466315
You received this bug notification because you are a member of Ubuntu
Bugs, whic
