This bug was fixed in the package ntp - 1:4.2.4p6+dfsg-1ubuntu3
--------------- ntp (1:4.2.4p6+dfsg-1ubuntu3) karmic; urgency=low
* Add enforcing AppArmor profile (LP: #382905) - debian/control: add Conflicts/Replaces on apparmor-profiles < 2.3.1+1403-0ubuntu10 (since we are now shipping usr.sbin.ntpd) and apparmor < 2.3.1+1403-0ubuntu10 (since we are now shipping tunables/ntpd) - debian/control: add Suggests on apparmor - debian/ntp.dirs: add apparmor directories - debian/ntp.preinst: force complain on certain upgrades - debian/ntp.postinst: reload apparmor profile - debian/ntp.postrm: remove the force-complain file - add debian/apparmor-profile* - debian/rules: install apparmor-profile and apparmor-profile.tunable - debian/README.Debian: add note on AppArmor * debian/patches/fix-nano.patch: enable nanokernel support (LP: #412242)
-- Jamie Strandboge <email address hidden> Tue, 11 Aug 2009 18:25:50 -0500
This bug was fixed in the package ntp - 1:4.2.4p6+ dfsg-1ubuntu3
--------------- 4p6+dfsg- 1ubuntu3) karmic; urgency=low
ntp (1:4.2.
* Add enforcing AppArmor profile (LP: #382905) 3.1+1403- 0ubuntu10 (since we are now shipping usr.sbin.ntpd) and 0ubuntu10 (since we are now shipping ntpd) ntp.postinst: reload apparmor profile apparmor- profile* profile. tunable README. Debian: add note on AppArmor patches/ fix-nano. patch: enable nanokernel support (LP: #412242)
- debian/control: add Conflicts/Replaces on apparmor-profiles <
2.
apparmor < 2.3.1+1403-
tunables/
- debian/control: add Suggests on apparmor
- debian/ntp.dirs: add apparmor directories
- debian/ntp.preinst: force complain on certain upgrades
- debian/
- debian/ntp.postrm: remove the force-complain file
- add debian/
- debian/rules: install apparmor-profile and apparmor-
- debian/
* debian/
-- Jamie Strandboge <email address hidden> Tue, 11 Aug 2009 18:25:50 -0500