Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
errtracker: include bits of snap-confine apparmor profile (#3421) #3424
Conversation
mvo5
merged commit 427483f
into
snapcore:release/2.26
Jun 1, 2017
0 of 7 checks passed
artful-amd64
autopkgtest running
Details
continuous-integration/travis-ci/pr
The Travis CI build is in progress
Details
xenial-amd64
autopkgtest running
Details
xenial-i386
autopkgtest running
Details
xenial-ppc64el
autopkgtest running
Details
yakkety-amd64
autopkgtest running
Details
zesty-amd64
autopkgtest running
Details
zyga
deleted the
zyga:backport/2.26/detect-partial-updates
branch
Jun 1, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
zyga commentedJun 1, 2017
This patch extends the error report with information about the used
snap-confine apparmor profile (as expressed by the text of the file) as
well as hint of partial dpkg update.
Partial or failed updates can leave the old (previous) apparmor profile
of snap-confine around (since it is tagged as a conffile) and
subsequently cause any snap execution to fail with access to
"/run/snapd/lock" directory.
To test the theory we will now measure the hashes of the current and any
.dpkg-new versions of the apparmor profile of snap-confine and attach
them to the report.
Signed-off-by: Zygmunt Krynicki zygmunt.krynicki@canonical.com