-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
many: update apparmor to 4.0.1 #14150
Merged
Merged
Changes from 11 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
70e1d20
build-aux: update vendored apparmor to 4.0.1 release
alexmurray 21a500c
build-aux: add autoconf-archive to apparmor/build-packages
alexmurray 3d7f8c1
build-aux: remove apparmor parser performance patch
alexmurray 9054d87
build-aux: remove remote patch application logic
zyga 8e4d4bf
build-aux: remove local patch application logic
zyga e00e683
cmd/configure.ac: expect apparmor 4.0.1 when building as a snap
alexmurray 1368576
sandbox/apparmor: use apparmor 4.0 abi with vendored parser
alexmurray 4068f94
sandbox/apparmor: add debug logging when probing parser features
alexmurray 592758b
sandbox/apparmor: log apparmor_parser version when probing features
alexmurray 3f176dd
tests/main: update for new vendored apparmor 4.0
alexmurray c52a550
Reapply "i/builtin: allow docker-support to use mqueue (#13738)" (#13…
zyga 6ff315b
interfaces: adjust docker-support test to handle mqueue
zyga 700f794
sandbox/apparmor: mask mqueue feature until apparmor 4.0.1
zyga c5df0af
sandbox/apparmor: support bundled 3.0 or 4.0 (preferred) abi
zyga 1ec2e54
sandbox/apparmor: unify test mocking logic
zyga ae4c83e
sandbox/apparmor: refactor appArmorParserVersion not to clobber cmd
zyga 93867c1
sandbox/apparmor: fix pair of typos
zyga File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably remove this file once we have moved to using core24 as build base. Right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit of an annoying part. The parser looks at the host's socket.h file to determine what kind of sockets one can create and to know their names.
If the snap is built on an old system, where the definition of old is always inaccurate. In theory we could drop it but we'd alwayd be at the risk of compiling but silently failing to understand specific network types.