Hi, Jason Cohen: > I am seeing the same behavior in Stretch
I'm not surprised. It's very likely that a number of the AppArmor policy fixes that were pushed to testing/sid (in src:apparmor* at least) since the Stretch release apply to Stretch as well. It would be nice if someone identified them so we can prepare a Stretch update. Such triaging is needed so that the proposed diff against Stretch is as small as possible, which eases reviews by the Release Team and decreases chances of introducing regressions. Would you be interested in this? Personally I'll treat this with low priority *for now*: I want to focus my AppArmor time on the "enabling AppArmor by default in Buster" experiment. Thanks for flagging this bug as affecting 1.11! Cheers, -- intrigeri
