[pkg-apparmor] Bug#893392: Bug#893392: apparmor: Identify what part of the Apertis delta we could merge into Debian/Ubuntu

Andrew Shadura andrew.shadura at collabora.co.uk
Fri Mar 23 10:17:01 UTC 2018


On Mon, 19 Mar 2018 09:58:55 -0500 Jamie Strandboge
<jamie at canonical.com> wrote:
> On Sun, 2018-03-18 at 15:37 +0100, intrigeri at debian.org wrote:
> 
> >  - split aa-status binary package to drop the Python dependency in
> >    the apparmor binary package
> 
> aa-status IMO really needs to be with the apparmor package, not in
> apparmor-utils and not in a separate apparmor-status pacakge. It is
> used in a lot of documentation and probably within a lot of scripts. I
> recently noticed that it uses python3, which may be what apertis
> objected to, but aa-status actually runs just fine with python2, so
> maybe a better collaboration point would be around Makefile changes on
> this point.

In fact, the reason we have split out aa-status was that we needed to
use AppArmor in a minimal Apertis container, and apparently no other
tools we had in that container used any Python runtime (2 or 3), which
is a dependency with quite a large footprint.

-- 
Cheers,
  Andrew



More information about the pkg-apparmor-team mailing list