[Pkg-privacy-maintainers] Bug#908463: Bug#908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy

[Roger Shimizu]

On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann <gregoa at debian.org> wrote:
> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>
>> Disabling the apparmor profiles fix this:
>>
>> aa-complain torbrowser.Tor.tor
>> aa-complain torbrowser.Browser.firefox
>
> After upgrading to 0.2.9-4, adequate complains:
>
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Tor.tor
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.plugin-container
> torbrowser-launcher: obsolete-conffile /etc/apparmor.d/local/torbrowser.Browser.firefox

Sorry, I don't have these errors when upgrading package.

====
# dpkg -i torbrowser-launcher_0.2.9-4_amd64.deb
(Reading database ... 272719 files and directories currently installed.)
Preparing to unpack torbrowser-launcher_0.2.9-4_amd64.deb ...
Unpacking torbrowser-launcher (0.2.9-4) over (0.2.9-3) ...
Setting up torbrowser-launcher (0.2.9-4) ...
Installing new version of config file
/etc/apparmor.d/torbrowser.Browser.firefox ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...
====

> After getting rid of them, I have a starting torbrowser again.
>
> Looks like some dpkg-maintscript-helper(1) magic is needed here ...

Could you provide an example, or even patch?
Thanks!

BTW. I have pushed not-released-yet 0.2.9-5 to branch debian/sid on salsa.
Maybe you can simply build the package by git-buildpackage, and test
the latest appamor profile from intrigeri.

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