On Monday, May 11 2020, Christian Ehrhardt wrote:
> The only thing that I found is that there was a follow on fix which IMHO should be included as well: > => https://gitlab.com/apparmor/apparmor/-/commit/ef591a67cedc1da0676b26448ea96fa8c073c253 > Due to that the state is "needs fixing", but other than this is already seems to be good.
I was wondering here how I could have missed the commit above... And now I know! This commit was only applied to master, but I was only considering the apparmor-2.13 branch when cherry-picking patches.
So yeah, there you go...
Thanks
-- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14
« Back to merge proposal
On Monday, May 11 2020, Christian Ehrhardt wrote:
> The only thing that I found is that there was a follow on fix which IMHO should be included as well: /gitlab. com/apparmor/ apparmor/ -/commit/ ef591a67cedc1da 0676b26448ea96f a8c073c253
> => https:/
> Due to that the state is "needs fixing", but other than this is already seems to be good.
I was wondering here how I could have missed the commit above... And
now I know! This commit was only applied to master, but I was only
considering the apparmor-2.13 branch when cherry-picking patches.
So yeah, there you go...
Thanks
--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14