This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
FYI, there was a components mismatch where apparmor-notify pulled
python3-notify2 (and its Depends) into main. For now, I've demoted
apparmor-notify to universe and adjusted the seed (in practical terms,
the security team will fix bugs in apparmor-notify regardless of where
it lives). We might revi
Sorry, while being about evaluating the new apparmor this got posted to
the wrong bug :-/
--
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/1895060
Title:
[FFe] apparmor 3 u
I knew from my former tests:
1. apparmor 3.0 = bad
2. downgrading to 2.13.3-7ubuntu6 and back up to 3.0 = good
3. aa-enforce + service restart = good
I checked the logs on the affected systems how this got into the bad
state:
$ grep -E 'configure (lib)?(apparmor|libvirt)' /var/log/dpkg.log
2020-
Thanks! Uploaded:
https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu5
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
** Changed in: apparmor (Ubuntu)
Milestone:
OK, go for it!
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
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/1895060
Title:
[FFe] apparmor 3 upstream r
Yes (barring bugs), there is no intention to break anything :)
--
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/1895060
Title:
[FFe] apparmor 3 upstream release
Status in
Just to confirm, your intention (barring bugs) is that there should be
no breakage for existing apparmor profiles and consumers of the
rewritten tools?
If so, I think this should still be fine at this stage.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
FYI, I accidentally violated the FFe process and uploaded (with a
subsequent binary copy) to groovy-proposed. None of that migrated, so I
deleted what was in groovy-proposed and am now attaching the debdiff,
which has patches to pass proposed migration (we believe). Sorry for the
snafu.
** Patch a
FYI, 3.0.0~beta1-0ubuntu3 should address the dbus autopkgtest issue.
--
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/1895060
Title:
[FFe] apparmor 3 upstream release
Stat
FYI, the fix for the dbus issue is
https://gitlab.com/apparmor/apparmor/-/merge_requests/625. We're
preparing an ubuntu2 upload now.
--
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.ne
FYI, we're looking at the autopkgtest dbus issue now.
--
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/1895060
Title:
[FFe] apparmor 3 upstream release
Status in apparmor
Apologies for posting the description as a comment above...
--
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/1895060
Title:
[FFe] apparmor 3 upstream release
Status in app
As per the draft upstream release notes:
AppArmor 3.0 is a major new release of the AppArmor user space that makes
an important change to policy development and support. Its focus is
transitioning policy to the new features ABI and as such other new features
have been limited.
Apprmor 3.0 is a br
** Attachment added: "groovy-proposed-apparmor-install.log"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+attachment/5411197/+files/groovy-proposed-apparmor-install.log
** Description changed:
As per the draft upstream release notes:
AppArmor 3.0 is a major new relea
15 matches
Mail list logo
