Bug#877255: [pkg-apparmor] Bug#877255: apparmor-profiles-extra: usr.bin.totem profile produces aa-logprof error: permission contains unknown character(s) Pux

2017-10-25 Thread intrigeri
Control: tag -1 + pending Vincas Dargis: > Attached patch from upstream MR [0] Thanks, applied to Vcs-Git. I've got another queued fix or two that I want to apply before I upload (most likely today or tomorrow: that's not high priority but still, let's try to keep our backlog small by tackling

Bug#877255: apparmor-profiles-extra: usr.bin.totem profile produces aa-logprof error: permission contains unknown character(s) Pux

2017-10-11 Thread Vincas Dargis
Control: tag -1 + patch Attached patch from upstream MR [0] [0] https://code.launchpad.net/~talkless/apparmor-profiles/+git/apparmor-profiles/+merge/332143 diff --git a/debian/README.Debian b/debian/README.Debian index 8469bcb..8ef2e61 100644 --- a/debian/README.Debian +++

Bug#877255: apparmor-profiles-extra: usr.bin.totem profile produces aa-logprof error: permission contains unknown character(s) Pux

2017-10-10 Thread intrigeri
Hi, Vincas Dargis: > On 2017.09.30 08:27, intrigeri wrote: >> Interestingly >> http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference#Execute_rules >> says that Pux is supported since 2.5, so I wonder who's correct. Thanks to everyone who helped clarifying this matter :) >> Replacing

Bug#877255: apparmor-profiles-extra: usr.bin.totem profile produces aa-logprof error: permission contains unknown character(s) Pux

2017-09-30 Thread Vincas Dargis
On 2017.09.30 08:27, intrigeri wrote: Interestingly http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference#Execute_rules says that Pux is supported since 2.5, so I wonder who's correct. I've grep'ed through upstream apparmor-profiles repository too, there is no single `Pux` usage.

Bug#877255: apparmor-profiles-extra: usr.bin.totem profile produces aa-logprof error: permission contains unknown character(s) Pux

2017-09-29 Thread intrigeri
Hi, Vincas Dargis: > Running `aa-logprof` produces this error: > ERROR: permission contains unknown character(s) Pux [...] > Looking at `man apparmor.d`, I see these modes: > EXEC TRANSITION = ( 'ix' | 'ux' | 'Ux' | 'px' | 'Px' | 'cx' | 'Cx' | > 'pix' | 'Pix' | 'cix' | 'Cix' | 'pux' | 'PUx'

Bug#877255: apparmor-profiles-extra: usr.bin.totem profile produces aa-logprof error: permission contains unknown character(s) Pux

2017-09-29 Thread Vincas Dargis
Package: apparmor-profiles-extra Version: 1.14 Severity: important Tags: upstream Dear Maintainer, Running `aa-logprof` produces this error: ERROR: permission contains unknown character(s) Pux I have grepped through /etc/apparmor.d: $ sudo fgrep -R Pux /etc/apparmor.d/