Control: severity -1 wishlist Hi,
intrigeri: > IIRC the goals was to allow package maintainers, who ship AppArmor > policy, or whose packages are affected by policy shipped via other > means, to easily identify when a bug reported to them might be caused > by AppArmor. This will ease debugging, which in turn will improve the > users' experience (because bugs can be fixed faster). > The idea was to ship a script in the apparmor package, that other > packages' bug script can source if it is present. > This bug script snippet would output at least: > * AppArmor LSM enabled? That part was implemented in reportbug 7.1.8. I think that was the most useful part of this proposal. > * list of installed apparmor packages + version > * maybe output of aa-status? > The apport hook we already is probably a good starting point: > /usr/share/apport/package-hooks/source_apparmor.py I'm not sure the marginal cost/benefit of implementing this would be very interesting now that reportbug includes LSM info. So I'm downgrading severity. > nicoo volunteered to look into it. Feel free to but frankly, I think your time/energy would be more useful elsewhere e.g. on our bugs with severity ≥ normal. Cheers, -- intrigeri
