Comment 3 for bug 1605052

Run with "sh -ex":
+ [ configure = configure ]
+ APP_PROFILE=/etc/apparmor.d/usr.lib.snapd.snap-confine
+ [ -f /etc/apparmor.d/usr.lib.snapd.snap-confine ]
+ LOCAL_APP_PROFILE=/etc/apparmor.d/local/usr.lib.snapd.snap-confine
+ test -e /etc/apparmor.d/local/usr.lib.snapd.snap-confine
+ mktemp
+ tmp=/tmp/tmp.BKsvA38yfB
+ cat
+ dirname /etc/apparmor.d/local/usr.lib.snapd.snap-confine
+ mkdir /etc/apparmor.d/local
+ true
+ mv -f /tmp/tmp.BKsvA38yfB /etc/apparmor.d/local/usr.lib.snapd.snap-confine
+ chmod 644 /etc/apparmor.d/local/usr.lib.snapd.snap-confine
+ aa-status --enabled
+ dpkg-maintscript-helper rm_conffile /etc/apparmor.d/usr.bin.snap-confine 1.0.36-1~ -- configure -- configure

So the .maintscript is not quite correct. I attach a diff with the fix. However, there is still a ugly warning when this gets installed, I think because "ubuntu-core-launcher" switches from arch:any to arch:all:

root@bod:/tmp# dpkg -i ubuntu-core-launcher_1.0.38-0ubuntu0.16.04.2_all.deb snap-confine_1.0.38-0ubuntu0.16.04.2_amd64.deb
(Reading database ... 13773 files and directories currently installed.)
Preparing to unpack ubuntu-core-launcher_1.0.38-0ubuntu0.16.04.2_all.deb ...
dpkg-query: package 'ubuntu-core-launcher' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
Unpacking ubuntu-core-launcher (1.0.38-0ubuntu0.16.04.2) over (1.0.27.1) ...
Selecting previously unselected package snap-confine.
Preparing to unpack snap-confine_1.0.38-0ubuntu0.16.04.2_amd64.deb ...
Unpacking snap-confine (1.0.38-0ubuntu0.16.04.2) ...
Setting up snap-confine (1.0.38-0ubuntu0.16.04.2) ...
Setting up ubuntu-core-launcher (1.0.38-0ubuntu0.16.04.2) ...