Bug#886548: libreoffice-common: Try to ship all AppArmor profiles in enforce mode

2018-02-23 Thread Rene Engelhard
[ I know this, maybe you should Cc the submitter? n...@bugs.debian.org does NOT go to the submitter ] Hi, On Fri, Feb 23, 2018 at 03:23:12PM +0100, Olivier Tilloy wrote: > Note that ubuntu accidentally shipped the apparmor profiles in enforce > mode for 5.4.5 on 17.10 as part of a stable release

Bug#886548: libreoffice-common: Try to ship all AppArmor profiles in enforce mode

2018-02-23 Thread Olivier Tilloy
Note that ubuntu accidentally shipped the apparmor profiles in enforce mode for 5.4.5 on 17.10 as part of a stable release update, and we have been getting rather negative feedback as this broke numerous real use cases. See https://launchpad.net/bugs/1751005.

Bug#886548: libreoffice-common: Try to ship all AppArmor profiles in enforce mode

2018-01-07 Thread Rene Engelhard
Hi, On Sun, Jan 07, 2018 at 03:40:55PM +0100, intrig...@debian.org wrote: > The remaining blocker seems to be autopkgtests being broken by > AppArmor, due to using custom paths: Bascially anything which needs "custom" paths. Another incarnation of this was

Bug#886548: libreoffice-common: Try to ship all AppArmor profiles in enforce mode

2018-01-07 Thread intrigeri
Package: libreoffice-common Version: 1:5.4.4-1 Severity: wishlist Hi, libreoffice-common 1:5.4.4-1 stopped disabling all profiles but the oosplash and soffice.bin profiles are still shipped in complain mode. This bug report is meant to track and discuss what needs to be done to ship them in