Control: tag -1 moreinfo Alessandro Ghedini <gh...@debian.org> writes: > could you please remove valgrind from armel? It used to build there with a > somewhat ugly hack (valgrind doesn't support armel baseline architecture), but > it stopped doing so a couple months ago, and there doesn't seem to be much > interest in armel valgrind from arm porters (nor from me FWIW). Also see > #720409.
There are still quite a lot of packages build-depending on valgrind: # Broken Depends: alleyoop: alleyoop eclipse-linuxtools: eclipse-cdt-valgrind libtest-valgrind-perl: libtest-valgrind-perl # Broken Build-Depends: abiword: valgrind alleyoop: valgrind dbus: valgrind diod: valgrind gsasl: valgrind gss: valgrind jq: valgrind libdrm: valgrind libtest-valgrind-perl: valgrind mpich: valgrind mpich2: valgrind pypy: valgrind qpid-cpp: valgrind rhmessaging: valgrind shishi: valgrind swi-prolog: valgrind valkyrie: valgrind (>= 3.6.0) xserver-xorg-video-intel: valgrind The ones I looked at restricted the build-dep on valgrind to the architectures that have it. So armel needs to be removed from these lists first. These are also a few false positives as dak doesn't look at architecture restrictions. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
