Hi,

I asked this question on Debian bug #822077 and was directed here.

The maintainer script fragments that dh_apparmor generate only deal with the
activation of a policy when the package is installed, and not the
deactivation of it when it's removed.

For the sake of completeness, I would have thought that it should, but I
presume there's some good technical reason why it doesn't?

regards

Andrew

Attachment: signature.asc
Description: Digital signature

-- 
AppArmor mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/apparmor

Reply via email to