On Fri, 2024-05-03 at 13:35 +0200, Simon Josefsson wrote: > I wonder why no QA tool reported this?
As implied by the usertags I used, the adequate tool found it: http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/ In addition, piuparts has a test for broken symlinks too, and as well as that it runs adequate, which also found the broken symlink: https://piuparts.debian.org/sid/pass/libntlm0_1.8-2.log > Seems like a simple thing for lintian to discover? For this specific case lintian could do something, but in the general case that is impossible, because symlinks can point at files owned by another package, which could be in depends, or recommends or suggests, or even be something the sysadmin is expected to download later. > Or did you use some tool to discover this that isn't linked from the PTS? The piuparts pages are only linked from the PTS when there is an error, but invalid symlinks and most adequate issues don't count as errors. Perhaps it should change to always link piuparts in the right panel and to raise minor TODO items when symlink and adequate issues are present. > A patch like the one below seems to fix this. But maybe we should raise > a lintian wishlist bug report too. Feel free to raise any extra bugs. Please XCC me if you do. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
