[16489] in athena10
[Debathena] #1600: debathena-apparmor-config postinst interaction
daemon@ATHENA.MIT.EDU (Debathena Trac)
Wed Apr 17 20:32:38 2019
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: Debathena Trac <debathena@mit.edu>
CC: <debathena@mit.edu>, <rlink@cs.cmu.edu>
To: <kaduk@mit.edu>
Date: Thu, 18 Apr 2019 00:32:09 +0000
Reply-To:
Message-ID: <041.15cd17dc3f8a1d2a59ea1872691a2d47@mit.edu>
Content-Transfer-Encoding: 8bit
#1600: debathena-apparmor-config postinst interaction with apparmor incomplete
---------------------------+-----------------------------------
Reporter: kaduk | Owner:
Type: defect | Status: new
Priority: normal | Milestone: The Distant Future
Component: -- | Keywords:
Fixed in version: | Upstream bug:
---------------------------+-----------------------------------
rlink@cs.cmu.edu says:
Nickel version: You should ignore failures to restart apparmor,
since
that can fail for reasons wholly unrelated to your package and
leave
you with a half-installed package.
Ten-cent version: I introduced a systemd circular dependency into
CMUCS Dragon (the custom Ubuntu we run here) that would cause the
systemd apparmor.service to sometimes fail to start. And
restarting
would fail, too.
Y'all test with apparmor_status before kicking off your restart,
but
"apparmor_status --enabled" only reports if you *want* AppArmor
to be running, not whether it *is*.
--
Ticket URL: <https://athena10.mit.edu/trac/ticket/1600>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
