Hello, It would be nice to be able to run lintian on a package directory before running debuild, to be able to catch various trivial things such as CVS or .svn directories left around, debian versions when no matching .orig.tar.gz is present in the upper directory and so on. A possibility of spotting them before the build would be very valuable to avoid spending long time waiting for the build to discover that a .svn dir has left around or that I forgot to generate the .orig.tar.gz and restart the build again. Bye, Enrico
You should be able to emulate this behaviour by only running dpkg-source -b and then calling lintian on the resulting source package. Interesting idea, though. Let's see what we can do :) Gruesse,
Hi! I just wanted to +1 on this idea. I am exploring this in order to get my text editor to nag about findings immediately without separate build steps. To implement something similar to e.g. linter-shellcheck[1] in my favorite editor it would help immensely if Lintian would accept simply the path to an existing 'debian/' directory as an argument, or even better if it would accept individual files (e.g. debian/control) and then run all the lints that are applicable to plain debian/* files. [1] https://web.pulsar-edit.dev/packages/linter-shellcheck