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

Vincas Dargis vindrg at gmail.com
Wed Oct 11 16:02:54 UTC 2017


On 2017.10.10 19:57, intrigeri wrote:
>> Not sure what updating mere request means. Should I simply create new MR with alternative `pux`?
> 
> Yes: fork a branch based on mine, add a commit with this change and an
> suitable justification, create a new MR and add a note on mine to say
> it's obsoleted by yours (I'll close it).

Got it, thanks.

>>> … and then propose a branch forked off current Vcs-Git on the Debian side?
> 
>> Sorry I do not follow, how do I propose branch for Debian?
> 
> Fork the repo somewhere, push your branch there, and point to it from
> this bug report (with a "Control: tag -1 + patch" pseudo-header).

Uhm, so I just attach a patch, as in other cases? I just got confused about that wording
I guess. Or is there actually a possibility to have user branches in Alioth, as in Launchpad?


> Please ensure you update debian/README.Debian accordingly so it points
> to the correct upstream MR :)

I see what you mean, will do.



More information about the pkg-apparmor-team mailing list