Package: valgrind Version: 1:3.13.0-1 Severity: normal Tags: upstream patch
Dear Maintainer, glibc was recently updates in debian unstable to 2.26-1 and revealed bug in valgrind. Fortunatelly it is already fixed in valgrind upstream. https://bugs.kde.org/show_bug.cgi?id=381289 I would appreaciate if you could backport related patch to debian unstable. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.12-200.fc26.x86_64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages valgrind depends on: ii libc6 2.26-1 ii libc6-dbg 2.26-1 Versions of packages valgrind recommends: pn gdb <none> 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
