Yeah Jamie, thanks for the status update - absolutely right for apparmor
(ubuntu).
Yet - at least I - have no idea what to backport in regard to provide debdiffs
in that case.
I would have hoped you(r team) would know what that was about in particular and
might have discussed/considered/rejected that as an SRU already.
I read the apparmor changelog but couldn't spot anything since xenial which
pointed towards this or a similar issue that could be backported.
I'll nominate a Xenial/Yakkety task to let you consider what would need to be
backported.
If nobody knows then these tasks will go "confirmed / low" I guess :-/
** Also affects: tor (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: tor (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
** No longer affects: tor (Ubuntu Xenial)
** No longer affects: tor (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670408
Title:
Missing apparmor rules cause tor to fail to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
