Control: severity -1 important [Santiago Vila] > Based on the above comment, this bug should really be RC, because > Release Policy says that packages in stretch *must* be buildable in > stretch (this of course includes a machine running the default kernel > for stretch).
All the dependencies are present, and the build if failing will instruct the person supervising the build to change the content of /proc/sys/kernel/perf_event_paranoid from 3 to 2. To build it, you can for example do like this: sudo sh -c "echo 2 > /proc/sys/kernel/perf_event_paranoid" apt-get build-dep coz-profiler apt-get source -b coz-profiler I believe this demonstrate that it is buildable in Stretch. So to me that is no release critical bug here. It is at most important. The severity might change when the autobuilders for the release architectures are affected, which is not the case at the moment. > [ I arrived at this bug because it already fails in my autobuilders ] Are you behind the x32 builder? It is the only one failing on <URL: https://buildd.debian.org/status/package.php?p=coz-profiler&suite=unstable > > If you absolutely need to run the tests during the build, maybe a > workaround would be to add a build-depends on a package which changes > the kernel value for you in its postinst (as I guess that the ordinary > user used to build packages would not be able to do that). Interesting idea. Not sure if such package will be accepted by the ftpmasters, given that the sudo command above will do the same for those privileged enough to change the level. -- Happy hacking Petter Reinholdtsen
