The problematic scenario is this: Stretch is released, the autobuilders are upgraded to stretch and a security hole is discovered in coz-profiler (or some other need for an update in Stretch. In this case, the code will no longer build in the autobuilders, and that would be highly problematic.
What options do we have? I can think of two: (1) Stop verifying during build that coz when the kernel prohibits it or (2) find another way to test coz during build that do not involve the kernel perf interface. Any other ideas? We need a fix for this very soon for the fix to make it into testing. -- Happy hacking Petter Reinholdtsen
