Comment 6 for bug 1553797

I'm confused, what does this have to do with deb installation? The apparmor rule hackery never affected "real" system installation of debs, and the blanket /tmp/adt-run.** pattern should apply to all subsequent temp location installs.

These apparmor rules should apply to click packages (only), not to debs. So do you mean that with this approach /var/cache/apparmor/click-ap.rules does not apply to clicks which are installed *after* creating that file? That indeed would sound like a bug in Apparmor itself as surely a newly installed click package should cause its own profile to be generated on installation?

Can you please be more specific and detailled what the remaining problem is after calling apparmor-rules-update-lite? (Btw, this can be dramatically simplified, but that can happen later).