Making apparmor "Priority: standard"? [Was: Bug#879590: apparmor: Decide how we enable AppArmor by default]
- To: email@example.com
- Cc: firstname.lastname@example.org
- Subject: Making apparmor "Priority: standard"? [Was: Bug#879590: apparmor: Decide how we enable AppArmor by default]
- From: intrigeri <email@example.com>
- Date: Wed, 25 Oct 2017 18:25:29 +0200
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <email@example.com> (firstname.lastname@example.org's message of "Wed, 25 Oct 2017 17:09:58 +0200")
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
tl;dr: can I make the apparmor package Priority: standard?
I'm working on the last blockers towards starting the experiment I've
proposed on debian-devel@ 2.5 months ago, i.e. enabling AppArmor by
default for a while in testing/sid.
Enabling AppArmor by default on new installations requires two
1. enable the LSM in Linux: problem solved, Ben Hutchings is fine with
doing this in src:linux
2. install the apparmor package by default.
This email is about (2).
My understanding is that making the apparmor package "Priority:
standard" i the way to go. Correct?
The package itself has "Installed-Size: 1803 kB".
I've trimmed the dependencies of this package a bit (just uploaded
2.11.1-2 as a result) so it seems to be an OK thing to do to me.
The dependencies are now:
libc6 (>= 2.17),
debconf (>= 0.5) | debconf-2.0,
lsb-base (>= 3.0-6),
… i.e. only stuff that's installed by default already anyway.
Would you folks have any problem with this change?
Once this is done I'll coordinate with Ben wrt. pushing the other big
red button i.e. (1) once the other blockers have been resolved.