[Pkg-privacy-maintainers] Bug#934119: torbrowser-launcher: Erroneously manages /etc/apparmor.d/local/torbrowser.* as conffiles

[intrigeri at debian.org]

Package: torbrowser-launcher
Version: 0.3.2-1
Severity: normal

With this version, /etc/apparmor.d/local/torbrowser.Browser.firefox
and /etc/apparmor.d/local/torbrowser.Tor.tor are managed as conffiles
again, while they should not: they're supposed to be created/deleted
as needed by bits of maintainer scripts generated by dh_apparmor.

A problematic consequence is that if I have local tweaks in those
files (which is their actual intended purpose), I'm asked on upgrade
to resolve the conflict between my configuration and the empty one
shipped by the package.

I believe we've had the same bug in the past, that got fixed in
d0deb2f923edbaf3c2801c46d74b7925c5605593. I'm not sure what
exact rm_conffile call would be suitable here (depends on which
upgrade paths we shall support).

Cheers,
-- 
intrigeri