Bug#1030222: [DSE-Dev] Bug#1030222: selint: please restrict check only where valgrind is available

2023-02-01 Thread Amin Bandali
Amin Bandali writes: > Hello there, > > You might find it more convenient to depend on 'valgrind-if-available' > rather than 'valgrind' itself, per the attached patch. It also skips > tests that need valgrind, for problematic arches. What do you think? To be fully clear, by "it" in "it also

Bug#1030222: [DSE-Dev] Bug#1030222: selint: please restrict check only where valgrind is available

2023-02-01 Thread Amin Bandali
Hello there, You might find it more convenient to depend on 'valgrind-if-available' rather than 'valgrind' itself, per the attached patch. It also skips tests that need valgrind, for problematic arches. What do you think? diff --git a/debian/control b/debian/control index 44fca69..a130223

Bug#1030222: [DSE-Dev] Bug#1030222: selint: please restrict check only where valgrind is available

2023-02-01 Thread Christian Göttsche
> Would it be possible to check and restrict valgrind dependency only on the > above architectures? I am probably going to drop the dependency on valgrind completely, as the testsuite with valgrind also fails on mipsel (maybe some DWARF incompatibility?). Valgrind is used in the upstream CI, and