Your message dated Sun, 13 Apr 2025 10:41:02 +0000
with message-id <e1u3ulq-00f00b...@fasolo.debian.org>
and subject line Bug#1057621: fixed in valgrind 1:3.24.0-3
has caused the Debian Bug report #1057621,
regarding valgrind should not drop valgrind-dbg
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1057621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: valgrind
Version: 1:3.20.0-1
Severity: serious
X-Debbugs-Cc: Adam Borowski <kilob...@angband.pl>
-dbgsym packages are not part of the normal archive,
and they can therefore not be expected to be pulled in
by normal dependencies.
For the usual case where debug symbols are only used
when debugging in a debugger this is no problem,
but valgrind-dbg is (like libc6-dbg) an exception:
Package: valgrind
Recommends: valgrind-dbg, gdb
https://sources.debian.org/src/valgrind/1%3A3.20.0-2/debian/README.Debian/#L11-L16
Debian's valgrind package comes stripped of any debug symbols, which are
provided by the valgrind-dbg package. Note that it's recommended to install
such package because without those symbols valgrind may generate less
helpful error messages in certain situations, or not work at all.
-- Alessandro Ghedini <gh...@debian.org> Sun, 09 Mar 2014 00:00:00 +0100
--- End Message ---
--- Begin Message ---
Source: valgrind
Source-Version: 1:3.24.0-3
Done: Michael Stapelberg <stapelb...@debian.org>
We believe that the bug you reported is fixed in the latest version of
valgrind, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Stapelberg <stapelb...@debian.org> (supplier of updated valgrind
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 13 Apr 2025 11:53:29 +0200
Source: valgrind
Architecture: source
Version: 1:3.24.0-3
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini <gh...@debian.org>
Changed-By: Michael Stapelberg <stapelb...@debian.org>
Closes: 1057621
Changes:
valgrind (1:3.24.0-3) unstable; urgency=medium
.
* Remove Recommends: valgrind-dbg in favor of not stripping vgpreload*.so.
Closes: #1057621. (Thanks Chris Hofstaedtler for the suggestion.)
Checksums-Sha1:
60ca91318106644c8ac7703e7ac941122a9e0d67 2608 valgrind_3.24.0-3.dsc
6b9efb4c5ed7f2631aefe7f053d797d1acbe0137 32908 valgrind_3.24.0-3.debian.tar.xz
3caee907f6e6fa005dca4feacbefb72a8e051e51 11221
valgrind_3.24.0-3_amd64.buildinfo
Checksums-Sha256:
9866148d4b3edbc91238f49b69de7e32b9e080c961e39d004f52acde5911439b 2608
valgrind_3.24.0-3.dsc
4b01316ac2e14b0fdb7717581728939692342169193113a1b04f6824a16e280a 32908
valgrind_3.24.0-3.debian.tar.xz
337f334f22cca231ccbff7f2ed90d1d9320b7cde9e9ccb6b5725b01b5e392d47 11221
valgrind_3.24.0-3_amd64.buildinfo
Files:
1b30beb7a1e2e4902235fc2641744efa 2608 devel optional valgrind_3.24.0-3.dsc
e488cb404fd3c04a30bf35c76d15545b 32908 devel optional
valgrind_3.24.0-3.debian.tar.xz
44cb438148757ebc1a9decace749754e 11221 devel optional
valgrind_3.24.0-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEQk4U1wPnxtQ9nW82TnFg7UrI7h0FAmf7jW8ACgkQTnFg7UrI
7h0W7w/9Fw4bqdcxJ6wPPNhhhO3dPqfIeS37nSIQC85eAtM33WA/pgBhOlHhcLRc
Xy1V0Ln9X7KxEzoI2chFwBr+xziy94qenEo2Hh3YxIBxHIpw71In4rqxBLMfcfag
dbhVGdBQznXNS+xKe2LW2A1pvWU3a4aXC2mR4uFz3f6iD+MbK0Hyy7F7q41eezne
u1e5jU9ibXBuOPDYS9osBfSl5i2Pgqj1Yi1kXIFpsWcYlAy3CgIlb4/heVi1xNjW
5R9PoGtOXr3HlGAQSqML+KqlaG/It6z7GotfyUMe55Q/0Vd8UjD7Jgi/8OpKS2nf
9wtJNX8SQYe4XRdQateFgMK1YAo4SkXghFGpP2mGmLdF1v2BqbLWRoXXkCUTQIJQ
XvvE8yIlC7OrxgcflOqrlQYQTtTgWuKuWTqgNo/4OS/nVSvL2LMfyJZtB5BSEXJz
Wt/6Qsu06ybCySKiN6uXd/TCnEXNaQ5lFXcv8ETW725qBLPvx2ZqFv7+JioQL5xE
ce3ulP0SFg0dJaoa1tM1BhSoIFWZO46lRfZYxO0wsZjNp8Ik9kwJTWjrp3/XmI/s
2aYRJTfTsLHsTYHknPV3V+OKUEAnlHW93PjQ2ffxa6xds9dYAtvfjZl87SAbNkK1
zJ4A0OYO48eecJGTuGR0T0Eem8oi6l49HRnAd4T3rcxfN/lmuqw=
=OhJf
-----END PGP SIGNATURE-----
pgpcEdvqgLZmI.pgp
Description: PGP signature
--- End Message ---
