© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
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).