files who won't tell who their parent packages are

[Dan Jacobson <jidanni@dman.ddts.net>]

Let's say a file is bothering me and I want to report it to its
parents or owners or anything
$ locate sndstat
/dev/sndstat #no similarly named brothers
$ apropos sndstat
sndstat: nothing appropriate.
$ dpkg -S /dev/sndstat
dpkg: /dev/sndstat not found.
$ reportbug -f /dev/sndstat
Finding package for /dev/sndstat
No packages match.
No package specified; stopping.

Is it therefore true that there can be some files, say created by
scripts, who have laundered their origins, so that there is no record
of what caused them to get there, and being that they arrived via
installation of a package, that some better way should be invented of
keeping track of them...
-- 
http://jidanni.org/ Taiwan(04)25854780