[Pkg-privacy-maintainers] Bug#812981: Bug#812981: Bug#812981: Bug#812981: Bug#812981: torbrowser-launcher: torbrowser cannot start possibly due to apparmor issue

[Holger Levsen]

Hi intrigeri,

On Dienstag, 2. Februar 2016, intrigeri wrote:
> As said in person a couple days ago: my goal here is to avoid creating
> the "AppArmor breaks stuff, disable AppArmor" culture that is harming
> e.g. SELinux' usefulness a lot IMO.

full ack and agreed.

> I trust you to take this into
> account and make a sensible decision, that I'm pretty sure I can live
> with :)

thanks! :)

Two things came to my mind: 

a.) we shouldn't say "disable the apparmor profile if you are using jessie" 
right now, but rather "if you are using apparmor on jessie, upgrade 
torbrowser-launcher to the version from jessie-backports" because that version 
does work with apparmor on jessie.

b.) for fixing this in jessie proper, does it take anything else than just 
merging the profile from jessie-backports into the jessie branch and upload?


cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-privacy-maintainers/attachments/20160202/b74759d4/attachment.sig>