Bug#1022222: valgrind-if-available shouldn't stop providing valgrind on mipsel

Control: severity -1 normal (I intended to avoid having to argue by implementing specific objective tests that valgrind has to meet to be declared available, but I did not manage to get that done. Thus, arguing...) On Sat, Oct 22, 2022 at 12:12:40PM +0300, Adrian Bunk wrote: > Package: valgrind-

Processed: Re: Bug#1022222: valgrind-if-available shouldn't stop providing valgrind on mipsel

Processing control commands: > severity -1 normal Bug #102 [valgrind-if-available] valgrind-if-available shouldn't stop providing valgrind on mipsel Severity set to 'normal' from 'serious' -- 102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102 Debian Bug Tracking System Conta

Bug#1022222: valgrind-if-available shouldn't stop providing valgrind on mipsel

Package: valgrind-if-available Version: 3.18.1-1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Alessandro Ghedini , Debian UBports Team Control: affects -1 src:qtmir valgrind-if-available (3.18.1-1-1) unstable; urgency=medium ... * Drop mipsel as valgrind disagrees about blah blah baseline Loo