There's definitely stuff in 2.8.95 that I want---what most comes to mind
is the newer Python implementations of the various AppArmor utilities,
which don't have the problems of the deprecated Perl ones:
https://bugs.launchpad.net/bugs/950921
(see comment #3)
Still, Ubuntu plays things pretty fast and loose, especially with the
non-mainline kernel patches. Even if we *could* get those into Jessie, I
don't think we'd want to, just because it's not in character for Debian
to include bleeding-edge patches in a stable release kernel.
As for the userspace: It might be possible to use the newer userspace
without the kernel patches, but of course that hasn't been tested, and
it would be an "unsupported" configuration. Which in itself isn't a
showstopper, but for the fact that it's not Debian driving AppArmor
development. If Debian runs into trouble with that setup, we don't
really have the people on this side to fix it, and Ubuntu's got enough
on their plate already supporting *one* version of the kernelspace.
So far, we've run into some issues with profiles having newer syntax
than what Debian's userspace supports. Those has been relatively easy to
fix; just edit the profile, reload, test. Kernel incompatibilities would
be a *lot* harder to address.
For my part, I think option 1 is the way to go for Jessie. Debian as a
whole is "well-tested, known working," after all :-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
