On Sat, 2022-10-08 at 11:00 +0200, Niels Thykier wrote: > 2) We now have a debuginfod service, so you do not even have to install > dbgsym packages anymore (if you configure gdb to use it). For the > cases where you do install the dbgsym, you still have to manage > inter-source dbgsym dependencies manually. The debuginfod service is not protected by the archive keys and it isn't available offline, so I currently prefer to use debian-goodies' `find-dbgsym-packages --install` command. Since I don't have any foreign architectures enabled, I can't be affected by the issue with not strict enough dependencies though. Removing all dependencies would mean that removing an obsolete library package would no longer also remove the dbgsym package and a lot of obsolete library packages would accumulate without manual action and it could be time consuming to track down no longer used dbgsym packages. Keeping the dependencies does also block some use-cases, some of that can be worked around using debuginfod, with the usual downsides. I have often wanted a different kind of relationship between packages and their dbgsym packages than mere Depends. Currently when a dbgsym is installed it keeps the library package installed even after it is no longer used and both should be auto-removed. So I believe the optimal thing to do would be stricter depends for now and later if apt adds some kind of special handling for dbgsym, then all of the Depends could be dropped to enable more use-cases. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part