This could use some diffs attached to see how bad the damage is, but as long as the three combinations are tested, I'm fine with this in theory:
1) old kernel and new userspace 2) new kernel and old userspace 3) new kernel and new userspace Also, it's not clear if the "other packages that need updating in lockstep" thing is a hard dependency or just a "so they can make use of the feature". If it's a hard dependency, you'll need that specified in package relationships (new apparmor should probably have a "Breaks: foo (<< ver), bar (<< ver)" rather than making all of those packages depend on versioned apparmor). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1362199/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
