Debdiff is good, thanks Simon!. I think it is fair to add fsetid for now to work. If details are found how that can be limited later we can do so still.
With the fixes applied as expected the control socket is usable now when running from [1] in a container. (my old) lintian complains about a few things, but none of it were touched on this change - so leaving them as is for now. Sponsoring into bionic [2] Please help tracking the migration over the next few days ... [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3178/+packages [2]: https://launchpad.net/ubuntu/+source/unbound/1.6.7-1ubuntu2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749931 Title: unbound-control local socket broken by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1749931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
