Package: apparmor
Version: 2.11.0-11
Severity: important

My plan is:

1. in testing/sid, ship a conffile (in a package built from
   src:apparmor) that pins the most recent feature set fully supported
   by our policy, i.e. Linux 4.12's or 4.13's (depending on whether
   we've fixed all the regressions brought by 4.13 yet); this should
   make the transition to Linux 4.14 smooth;

2. once our policy has been updated to work well with Linux 4.14's
   AppArmor features (#877581), bump the pinned feature set to 4.14's

3. rinse & repeat for Linux 4.15 etc. using another, dedicated bug
   report

I'll file another bug report about doing something similar to address
the Stretch + Linux from backports use case.

Cheers,
-- 
intrigeri

Reply via email to