On 02/17/2018 10:11 AM, Vincas Dargis wrote: > On 2/17/18 8:07 PM, John Johansen wrote: >>> So the idea is to wait for 3.0 (BETA?) to implement this long-topic NVIDIA >>> issue then? That would be really nice way, I guess, to fix this in one go, >>> instead of "temporar-stuff-and-real-fix-later". >> >> No the beta won't be a few weeks, I plan to kick out the error and warn >> patches this weekend, I expect we can have the fix in the beta > > That would be fast... I will need to research how to run latest AppArmor or > my (virtual?) machine to work on thought.
As long as you don't need a new libapparmor (you shouldn't for these patches) either grab a tarball or fresh checkout make sure you have the builddeps, sudo apt-get build-dep apparmor cd into the parser/ dir and do make USE_SYSTEM=1 now you can use the built parser by doing ./apparmor_parser or you can do a sudo make install to install it to the system -- AppArmor mailing list AppArmor@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
