Comment 23 for bug 340183

Please consider this for a Jaunty Beta freeze exception.

Attached is a debdiff to fix this issue; it also cherrypicks a couple of issues fixed upstream that came to light in testing this fix, namely a situation where the tools could generate an invalid apparmor profile, and where the tools would, in repeated invocations, ask about the same networking events, even though the profile in question had already been modified to allow them.

All the changes in question are limited to the apparmor-utils perl module Immunix/SubDomain.pm; and as the tools do not correctly parse the generated log messages and thus are non-functional, the risk of regression from this fix is low, and should have no impact on the rest of the distribution.

I have tested these changes in packages built for jaunty in my ppa, and as Dariusz Suchojad mentioned, he tested the same changes as applied to intrepid packages, also built from my ppa.

Thanks.