Bug#432026: cruft on single_file([s] (or directory trees too))
Hi, I've adopted cruft. I've added a filter for this loose file [1] just now. It comes from kernel-package [2]. I feel that kernel-package should had deleted this file on purge in its postrm script. Here is my proposal to move these files from debian/postrm and turn those into a machine readable format: https://wiki.debian.org/Cruft/purge Then a simple "dpkg -S" would find it; without needing to add the "single file" feature here. -- This won't help if we discover the file *after* the package has already been purged. I should add a second scan pass in cruft / cruft-ng to try to attribute "unexplained" files to their respective package. -- [1]https://github.com/a-detiste/cruft/commit/b2916e47cd98da797a2070d381f49eaa6252a453 [2]http://sources.debian.net/src/kernel-package/13.014%2Bnmu1/kernel-img.conf.5/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#432026: cruft on single_file([s] (or directory trees too))
On Sat, Jul 07, 2007 at 04:26:38AM +0800, Dan Jacobson wrote: > $ CRUFT_DEBUG=1 cruft -d /etc/kernel-img.conf > True, -d is for DRIVES, but why not add an option just to check one > mystery meat file to see if it wasn't left by some spaceship, which is > pretty much all one knows if one just uses dlocate and no answer is > given. Sounds like a good idea. I think the way to implement it is to just run the explain scripts and scan the filter files to find out which matches/outputs the filename. Marcin -- Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
