apparmor: 4.0.3 -> 4.1.0, rewrite#400430
Conversation
6b5b9da to
357951c
Compare
357951c to
0b9a2cc
Compare
|
|
@ofborg build libapparmor libapparmor.passthru.tests |
0b9a2cc to
ba6ea8e
Compare
|
@ofborg build libapparmor libapparmor.passthru.tests |
600b63d to
b448118
Compare
b448118 to
4ff79a5
Compare
This comment was marked as resolved.
This comment was marked as resolved.
4ff79a5 to
9ec5cbc
Compare
41c3ccc to
a0872d1
Compare
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
|
@ofborg build libapparmor libapparmor.passthru.tests |
|
The ofborg build is timing out, so i suppose the |
|
Failed because of a HTTP 404 (so safe to ignore) |
|
I have just reported the parser test fails on musl upstream: https://gitlab.com/apparmor/apparmor/-/issues/513 |
156651d to
d47c4d3
Compare
d47c4d3 to
457c0ed
Compare
|
While the parser on musl is still somewhat broken, it can't be correct to hard-code glibc here. Asking stdenv for the correct libc for logprof is (hopefully) a little less broken. Replacing the parser with the musl based parser via overlay does still pass our VM test, so it is probably not completely broken. |
|
So while our parser tests are semi-broken, the VM tests do still pass with musl based parser. This is most likely less broken than it was before this PR. I am happy with this current state and would just say musl+apparmor users are on their own if they do end up running into edge cases with the parser here. |
Upstream release: https://gitlab.com/apparmor/apparmor/-/releases/v4.1.0 Notable changes made to the packaging: - apparmor-kernel-patches: drop. This was outdated and unused, and wouldn't even apply to any kernel anymore. - aa-teardown: migrate to writeShellAPplication - apparmor-*: migrate to by-name - apparmor-*: enable checks and actually run checks - libapparmor: test python module imports correctly - libapparmor: no seperate $python output (makes no sense)
457c0ed to
4f34d46
Compare
4f34d46 to
8be53b0
Compare
8be53b0 to
5467162
Compare
Upstream release: https://gitlab.com/apparmor/apparmor/-/releases/v4.1.0
Notable changes made to the packaging:
This should be basically compatible with any preexisting setup using apparmor. I tried my best to keep ABI.
Tested build types
This does unbreak a couple cross builds that were previously broken.
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.