This bug was fixed in the package apparmor - 2.13.2-9ubuntu4
---
apparmor (2.13.2-9ubuntu4) disco; urgency=medium
* debian/tests/control and debian/tests/compile-policy: don't test
thunderbird since the Ubuntu packaging doesn't ship a profile
-- Jamie Strandboge Wed, 27 Mar
Uploaded to disco-proposed.
** Changed in: apparmor (Ubuntu)
Status: Triaged => Fix Committed
--
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/1817799
Title:
[FFe]
I've confirmed that the "Could not open '/var/lib/snapd/apparmor/snap-
confine'" is not present in standard install of disco. This was a local
issue.
I've also updated the packaging to remove the "dpkg: warning: unable to
delete old directory '/etc/apparmor.d/cache': Directory not empty"
message.
As discussed on IRC, if the upgrade is clean, and you're committing to
keeping a close eye on bugs/regressions and fixing ASAP, go for it.
** Changed in: apparmor (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
FYI, disco now has 2.38 (I've updated the description accordingly).
** Description changed:
Feature Freeze exception for AppArmor 2.13.2
The security team is pushing to get AppArmor 2.13 into 19.04 since we
want AppArmor 3 (or higher) in 20.04 and we'd like to update to 2.13.2
to have
** Description changed:
Feature Freeze exception for AppArmor 2.13.2
The security team is pushing to get AppArmor 2.13 into 19.04 since we
- want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
- update to it to test the new features that are available now and make
- the
** Changed in: apparmor (Ubuntu)
Status: In Progress => New
--
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/1817799
Title:
[FFe] apparmor 2.13
Status in apparmor
** Description changed:
- FFe paperwork still in progress
-
Feature Freeze exception for AppArmor 2.13.2
The security team is pushing to get AppArmor 2.13 into 19.04 since we
want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
update to it to test the new features that
** Description changed:
FFe paperwork still in progress
Feature Freeze exception for AppArmor 2.13.2
The security team is pushing to get AppArmor 2.13 into 19.04 since we
want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
update to it to test the new features that
** Description changed:
FFe paperwork still in progress
Feature Freeze exception for AppArmor 2.13.2
The security team is pushing to get AppArmor 2.13 into 19.04 since we
want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
update to it to test the new features that
** Description changed:
FFe paperwork still in progress
Feature Freeze exception for AppArmor 2.13.2
The security team is pushing to get AppArmor 2.13 into 19.04 since we
want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
update to it to test the new features that
** Attachment added: "upgrade.log"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+attachment/5245939/+files/upgrade.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Here is the upgrade log. Note that these parser errors are unrelated to
apparmor 2.13 and an issue with the snapd packaging:
AppArmor parser error for /etc/apparmor.d in
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open
'/var/lib/snapd/apparmor/snap-confine'
AppArmor
Here is the sbuild build log
** Attachment added: "apparmor_2.13.2-9ubuntu1_amd64-2019-03-13T21:48:49Z.build"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+attachment/5245940/+files/apparmor_2.13.2-9ubuntu1_amd64-2019-03-13T21%3A48%3A49Z.build
--
You received this bug
** Description changed:
- TODO
+ FFe paperwork still in progress
+
+ Feature Freeze exception for AppArmor 2.13.2
+
+ The security team is pushing to get AppArmor 2.13 into 19.04 since we
+ want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
+ update to it to test the new
15 matches
Mail list logo
