This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5
---
apparmor (2.10.95-0ubuntu2.5) xenial; urgency=medium
* debian/lib/apparmor/functions, debian/apparmor.init,
debian/apparmor.service, debian/apparmor.upstart,
debian/lib/apparmor/profile-load: Adjust the
I've completed the AppArmor test plan:
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
I've also manually verified the AppArmor portion of this SRU.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
Hello Mike, or anyone else affected,
Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package apparmor - 2.10.95-4ubuntu4
---
apparmor (2.10.95-4ubuntu4) yakkety; urgency=medium
* debian/patches/allow-access-to-ibus-socket.patch: Adjust the ibus
abstraction to allow access to the abstract UNIX domain socket location
used in Ubuntu.
** Branch linked: lp:~apparmor-dev/apparmor/apparmor-ubuntu-citrain
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614215
Title:
"md5sums differ" message seems to indicate an install problem
To
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Yakkety)
Importance: Low
Assignee: Tyler Hicks (tyhicks)
Status: In Progress
** Changed in: apparmor (Ubuntu Xenial)
Importance: Undecided => Low
** Changed
The fix will be in the apparmor package. Marking the Ubuntu GNOME task
as invalid.
** Changed in: ubuntu-gnome
Status: Confirmed => Invalid
** Changed in: apparmor (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu)
Importance: High => Low
** Changed in:
This is a bug in the packaging and doesn't affect the upstream AppArmor
project.
** Changed in: apparmor
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614215
That message is harmless but admittedly confusing. It is coming from a
call out to `diff` to see if we need to update debsums files that we
save off for packaging purposes. I'll quiet the output from diff and may
possibly print a less scary message or I may just not print anything.
--
You
Unpacking apparmor-easyprof-ubuntu (16.10.2) over (16.10.1) ...
Setting up apparmor-easyprof-ubuntu (16.10.2) ...
(may take a while)
Files /var/lib/dpkg/info/apparmor-easyprof-ubuntu.md5sums and
/var/lib/apparmor/profiles/.apparmor-easyprof-ubuntu.md5sums differ
--
You received this bug
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614215
Title:
"md5sums differ" message seems to indicate an install problem
To
I also experienced this issue, first on an Ubuntu GNOME 16.10 VM, now on
my Ubuntu GNOME 16.04.1 installation. In my case the files also appear
identical.
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Confirmed
** Also
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614215
Title:
Agree with OP on both points, but also note that when I check the two
supposedly different files afterwards they are in fact identical except
for timestamp:
$ sudo diff /var/lib/dpkg/info/apparmor.md5sums
/var/lib/apparmor/profiles/.apparmor.md5sums; echo $?
0
--
You received this bug
14 matches
Mail list logo
