Package: valgrind
Version: 1:3.8.1-4
Followup-For: Bug #701691
Just ran into this issue on our build box abel -- I was genuinly surprised to
see valgrind available for that architecture so immediately jumped to install
it -- but as this report shows, it is next to useless on armel, so why we carry
armel build at all thus confusing poor users?
may be
override_dh_auto_test:
: # do nothing for now
should be tuned up to run at least few really quick tests to guarantee that
valgrind works to at least some degree on a given platform, and if not -- fail
that build thus avoiding users' frustration with useless package. Meanwhile
removing all the builds for unsupported architectures.
NB I have been enabling build-time testing for all of my packages and yes
-- it does give more work to make package suitable for testing/stable BUT it
provides a guarantee against many bugs being unraveled on users systems after.
Cheers,
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'stable'), (100, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages valgrind depends on:
ii libc6 2.17-7
ii libc6-dbg 2.17-7
Versions of packages valgrind recommends:
ii gdb 7.6-5
pn valgrind-dbg <none>
Versions of packages valgrind suggests:
pn alleyoop <none>
pn kcachegrind <none>
pn valgrind-mpi <none>
pn valkyrie <none>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
