Your message dated Mon, 13 Jul 2026 09:51:04 +0000
with message-id <[email protected]>
and subject line Bug#1103846: fixed in valgrind 1:3.27.1-0.1
has caused the Debian Bug report #1103846,
regarding should recommend debuginfod package to allow debugging symbol fetching
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 [email protected]
immediately.)
--
1103846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103846
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: valgrind
Severity: normal
Hello,
Sourceware.org is having issues today so I can't research specifics, but
Valgrind has supported the use of debuginfod's protocol to automatically get
debug symbols just like how GDB does. Debian's (unofficial?) debuginfod
instance is at debuginfod.debian.net and its use is documented elsewhere.
Unlike GDB, Valgrind doesn't use libdebuginfod, but it invokes the command-line
utility debuginfo-find from the debuginfod package. The Debian Valgrind package
appears to have this functionality enabled by default, but Valgrind doesn't
have any package relationship with debuginfod so users will only see this if
they know what they're missing and dig in to finding why it's not working.
Owing to that, I think adding a Recommends on debuginfod is the right way to go
here. Suggests is too weak for something that the majority of users will want
to have, as it allows getting symbols for Debian-packaged libraries even if a
user's own custom application is what's currently under test, and debuginfod is
cognizant of system-wide configuration and environment variables indicating
users' preferences. This will save users a lot of frustration; I see an upload
of Valgrind was just done, but can this be squeezed into Trixie?
Thanks
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: valgrind
Source-Version: 1:3.27.1-0.1
Done: Pierre-Elliott Bécue <[email protected]>
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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pierre-Elliott Bécue <[email protected]> (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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 10 Jul 2026 19:04:03 +0200
Source: valgrind
Architecture: source
Version: 1:3.27.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini <[email protected]>
Changed-By: Pierre-Elliott Bécue <[email protected]>
Closes: 1103846
Changes:
valgrind (1:3.27.1-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
* d/u/signing-key.asc: refreshed
* New upstream version 3.27.1
- Rebased patches
* d/copyright: heavy refresh
* d/control:
- Add a Recommends on debuginfod (Closes: #1103846)
- Bump Standards-Version to 4.7.3
Checksums-Sha1:
37a88089cb11f3554076ea5394549e5402f23484 2681 valgrind_3.27.1-0.1.dsc
0b113f5c80d34743195b78651c2520901ba630cf 17372682 valgrind_3.27.1.orig.tar.bz2
08495cd82338184bc847ba5df874c82a83845c74 228 valgrind_3.27.1.orig.tar.bz2.asc
e1adfe35e5ff5a2e5e29eef93cf0d33b4092accd 52840
valgrind_3.27.1-0.1.debian.tar.xz
578be499131461e39ebc170d3f697afa13b50fe6 11647
valgrind_3.27.1-0.1_amd64.buildinfo
Checksums-Sha256:
cb435fed23e0ad3fd7d94eebff4d0bad1c3e306541f03ccec55e23af1bb60836 2681
valgrind_3.27.1-0.1.dsc
5d589152eb8071c02feab8ce6ab719e431a1fbc3e2b1700f5432632a8b9264dc 17372682
valgrind_3.27.1.orig.tar.bz2
494d6c7fc6966592223c4f9bd1b9c92a062c9930dc2263335e11265026cf5c2c 228
valgrind_3.27.1.orig.tar.bz2.asc
ac560996560f988a94b6bc7467a0426d2951b803aa8623ead156bce48e187dfe 52840
valgrind_3.27.1-0.1.debian.tar.xz
559dc61098f63b7bad3bbbb76520c3ca56e8f6bcc09228f50bc3a9a6519bd695 11647
valgrind_3.27.1-0.1_amd64.buildinfo
Files:
e5fee9e42caa1664bc272d900fa2cbda 2681 devel optional valgrind_3.27.1-0.1.dsc
9b819b1aa88fc5936373fc624aa75723 17372682 devel optional
valgrind_3.27.1.orig.tar.bz2
5a5cec2a7f82602ccd270eef7795b8cd 228 devel optional
valgrind_3.27.1.orig.tar.bz2.asc
654411dc5c3f1672cd72bc11a0b940be 52840 devel optional
valgrind_3.27.1-0.1.debian.tar.xz
cf15ee660c90bb75020816cbc39a5f51 11647 devel optional
valgrind_3.27.1-0.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJSBAEBCgA8FiEE5CQeth7uIW7ehIz87iFbn7jEWwsFAmpUsKAeHHBpZXJyZS1l
bGxpb3R0LmJlY3VlQGlucmlhLmZyAAoJEO4hW5+4xFsL8+AP+wTNHX0yaB8KoRTV
P6Q+EsvWG0Qjeoz7Jwo/It0IXQtcZAkELqU4mRywifKZY4ZnFr308lO6+GYjmMya
rQc7L38raWKNyguTXNULGB96+zMuwZhm2LA1FkqQSKBElLYAZ5wtmxFsQ+3soNk3
FQ696gedP7zX+w8bxOalpqScq9iTrFc9Adn+71dqFNGRLOs4BpWJV0jjqfkcgZeM
IVSeI92IlSHaIorP8GzR5rXDJY1Qi7kiJkVSB7E4GnCAdW6hqOD3/LC6bSinf3I4
F3pvTfAsHOClO6HwET1DuxiDLoCjXRpoh+OgE/ZyjgrwLQSq0s6I3Eb1t6mTqOO3
CFh8MdVXqBBj+8au8NhmN1EUfFAh4A8DrahefDsGpUDKrLkxeIHrEvX63pV2CDvT
KfA+l6Vz0YtQVL1/5WGMMfa+a33uVRxw/XxiwvLBCxeoZdtvo0TKhxKP7KkA0Tsj
1Vn+SfNsK6yzvCTnQJwuhRi377fB36WHum3QnPq5FKjuriJGkxXs7/t5osS3VTjp
1FqufnWx4oulujhyeWeh+VT39N+osoNoJ42dAZIxKnJGGt2t55N8Sc5uHLQmFQ4V
tO04sOefJR8RB5N9Y4dIDaxD39swDgmIt2Gxxxy9lJA/MI8NkhZw67ONnPNPK61y
t+BOsEkna1bLJoH7uv1iECsa5W28
=UGe6
-----END PGP SIGNATURE-----
pgpBhaVOaVZ4x.pgp
Description: PGP signature
--- End Message ---
