Bug#814326: Warn if filenames contain wildcard characters (*?)

Hi Jakub, Thanks for the review. :) > "Certainty: certain" seems wrong to me. Updated. > +if ($fname =~ m,[\*\?],) { > > You don't need backslashes here (and IMO they hurt readability). Updated. I tried without but they "looked" wrong without being escaped (they usually are, so it came

Bug#814326: Warn if filenames contain wildcard characters (*?)

* Chris Lamb , 2016-08-25, 12:24: +Tag: file-name-contains-wildcard-character +Severity: normal +Certainty: certain I looked at existing packages in the archive that would trigger this tag[0], and none of their filenames appear to be a result of unexpanded shell wildcard. So "Certainty: certa

Bug#814326: Warn if filenames contain wildcard characters (*?)

tags 814326 + patch thanks Patch attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- From ef3df20be90a63fc6be0ade9087230d480def336 Mon Sep 17 00:00:00 2001 From: Chris Lamb Date: Thu, 25 Aug 2016 12:23:34 +0100 Subject:

Bug#814326: Warn if filenames contain wildcard characters (*?)

Package: lintian Version: 2.5.40.2 Severity: wishlist Hi, I think lintian should complain if files in .deb files contain * or ? characters. These are most likely unexpanded wildcard characters from debian/*.install files or the like. There might legitimate uses for these filenames, but these will