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

[Roger Shimizu]

Dear Intrigeri,

Thanks for your report, and sorry I just had time to look at this issue.

On Wed, Aug 7, 2019 at 5:21 PM <intrigeri at debian.org> wrote:
>
> 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.

So you mean we should revert 9fdce2a576782bb0790416bcf739b31ceb869c6b?

> 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).

d0deb2f923edbaf3c2801c46d74b7925c5605593 was just add entries of
rm_conffile line.
I'm not sure why we should remove rm_conffile here.
Please provide more info if possible. Thank you!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1