Re: Bug#1005324: ITP: valgrind-if-available -- dependency package to pull in Valgrind if it's available

[Adam Borowski <kilobyte@angband.pl>]

On Fri, Feb 11, 2022 at 10:58:26AM +0100, Ansgar wrote:
> On Fri, 2022-02-11 at 10:37 +0100, Adam Borowski wrote:
> >  This metapackage installs Valgrind on architectures where it is
> > available.
> >  As the list of archs where Valgrind works changes quite often,
> 
> The list is the same for all of oldoldstable, oldstable, stable,
> testing and unstable though:
> 
> +---
> | valgrind   | 1:3.12.0~svn20160714-1+b1 | oldoldstable    | amd64, arm64, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> | valgrind   | 1:3.14.0-3                | oldstable       | source, amd64, arm64, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> | valgrind   | 1:3.16.1-1                | stable          | source, amd64, arm64, armhf, i386, mips64el, mipsel, ppc64el, s390x
> | valgrind   | 1:3.18.1-1                | testing         | source, amd64, arm64, armhf, i386, mips64el, mipsel, ppc64el, s390x
> | valgrind   | 1:3.18.1-1                | unstable        | source, amd64, arm64, armhf, i386, mips64el, mipsel, ppc64el, s390x
> +---
> 
> So this would just be "Depends: valgrind" on all architetures?

There's no armel on your lists.

There's no support for most -ports archs, including riscv64 which is
supposed to be released with bookworm.

And x32 is on valgrind's archs list but fails to build.

We also had valgrind quite broken on some archs due to a glibc update, with
no fix for a year (any threaded program segfaulted).


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ Ash nazg durbatulûk,
⣾⠁⢠⠒⠀⣿⡁   ash nazg gimbatul,
⢿⡄⠘⠷⠚⠋⠀ ash nazg thrakatulûk
⠈⠳⣄⠀⠀⠀⠀   agh burzum-ishi krimpatul.