Package: valgrind-if-available Version: 3.18.1-1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Alessandro Ghedini <gh...@debian.org>, Debian UBports Team <team+ubpo...@tracker.debian.org> 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 Loongson. This is wrong, and it makes at least qtmir FTBFS. If there is any problem with valgrind on mipsel it should be discussed and resolved in valgrind first, if valgrind is available then valgrind-if-available has to provide it. It is also unclear what the baseline problem is this changelog entry is referring to, there is no open bug in the valgrind package mentioned and the closest I could find was a bug that was fixed (sic) 5 years ago. It is also suprising if this is really a mipsel-only issue as the changelog claims, I would have expected any issues to also show up on mips64el. Therefore please report any issues with valgrind on mipsel as bugs against src:valgrind, but in any case please make valgrind-if-available always provide valgrind on all architectures where it is available.
