This bug was fixed in the package apparmor - 3.0.4-1ubuntu1
---
apparmor (3.0.4-1ubuntu1) jammy; urgency=medium
* Merge from Debian unstable; remaining changes:
- Drop the following patches that have been included in the upstream
release or which Debian has also included:
Hmm so had to redo my merge after the 3.0.3-0ubuntu9 upload... see new
bileto ticket/PPA for the current version of it
https://bileto.ubuntu.com/#/ticket/4797
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
sorry, I was confused a bit about the issue. I have no objection to
uploading the diff from #7. Still while the patch makes the immediate
mctp issue go away from the current tests it isn't a full fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
FYI I am preparing this in https://bileto.ubuntu.com/#/ticket/4796 - I
have included the original patch from arighi to fix the aa-notify tests
too. Once britney looks happy with this I will upload it to jammy-
proposed.
--
You received this bug notification because you are a member of Ubuntu
Touc
"To unblock kernel development we need apparmor to never fail ADT
testing in devel series, as new kernel is developed. We do not want to
hint to ignore it, because we must never regress apparmor."
unfortunately this is just not possible with the way kernel development
works. The addition of new "f
Ah, it is president's day & night time in australia.
I will upload this, to unblock releasing jammy kernels. And we can
revisit this once everyone is back to back this out; or get a different
implementation in.
Blocking kernel testing with app armor test suite is developer time
critical, and prev
@alexmurray @jjohansen
When are updated apparmor going to be upload that continues to pass
existing test-suites / adt?
At this point failing apparmor ADT, blocks releasing all kernels in
jammy, preventing development of all kernels, and prevents security
kernel fixes.
To unblock kernel developme
updated debdiff in attach FWIW
** Patch added: "apparmor-fix-autotests.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5562493/+files/apparmor-fix-autotests.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
I should note that mctp is NOT part of the abi change in 3.0.4. This
means by default mctp mediation will not be enforced by policy. It will
be accepted in rules if present but since policy was not developed with
mctp in mind, turning it on by default for the policy would be an abi
break and could
@arighi: mctp is already supported in the 3.0.4 release that @alexmurray
is working on merging
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1961196
Title:
apparmor auto
@alexmurray thanks for the update! BTW I found another issue with test-
network.py: this test is failing because utils/apparmor/rule/network.py
is missing the mctp protocol (in network_domain_keywords[]).
I checked upstream, but I couldn't find any fix for this, do you want me
to open another trac
FYI I am working on merging apparmor-3.0.4 from debian unstable to jammy
at the moment which should resolve this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1961196
Tit
This was already fixed upstream with
https://gitlab.com/apparmor/apparmor/-/merge_requests/848 (with a
slightly different patch that works for all python versions).
AppArmor >= 3.0.5 will include the fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1961196
Title:
apparmor autotest failure on jammy with linux 5.15
Status in apparmor package in Ubunt
Simple fix in the attached debdiff
** Patch added: "apparmor-fix-test-aa-notify.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5561612/+files/apparmor-fix-test-aa-notify.debdiff
--
You received this bug notification because you are a member of Ubuntu
Tou
** Description changed:
+ [Impact]
+
+ test-aa-notify is also checking if the output of `aa-notify --help`
+ matches a specific text. However it looks like this output has changed
+ in jammy so the autopkgtest is reporting errors like this:
+
05:17:31 ERROR| [stderr] === test-aa-notify.py ===
16 matches
Mail list logo
