[SCM] Debian package checker branch, master, updated. 2.5.9-36-g657f7c9
The following commit has been merged in the master branch:
commit 657f7c91a51734f0a4eefd921f86525905f1050d
Author: Niels Thykier <niels@thykier.net>
Date: Sat Jun 30 15:32:58 2012 +0200
lintian(1): Mention some 2.5.10 changes and update BUGS section
Under --debug, mention that running times will be measured when using
-d twice (or more) and under "CHECKING LAST BUILD" that
<source>_<version>_all.changes will also be tried.
Finally mention that two Lintian processes can be run in parallel as
long as they are not using the same Lab.
Signed-off-by: Niels Thykier <niels@thykier.net>
diff --git a/man/lintian.pod.in b/man/lintian.pod.in
index aab01fd..a4b29cc 100644
--- a/man/lintian.pod.in
+++ b/man/lintian.pod.in
@@ -137,7 +137,9 @@ General options:
Display debugging messages. (Implies B<-v> and overrules any B<-q>).
-Can be used multiple times to increase the debug information.
+Can be used multiple times to increase the debug information. If
+passed twice or more, Lintian will emit approximate run times for
+collections and checks (if L<Time::HiRes> can be loaded).
This option cannot be specified in the config file. If used on the
command line it will override the B<verbose> and the B<quiet> options
@@ -747,6 +749,11 @@ returned by dpkg).
Pseudo architecture used by mergechanges(1).
+=item I<all>
+
+Used when building architecture indep packages only (e.g
+dpkg-buildpackage -A).
+
=item I<source>
Used for "source only" builds (e.g. dpkg-buildpackage -S).
@@ -813,8 +820,9 @@ exit.
=head1 BUGS
-Lintian does not have any locking mechanisms yet.
-(Running several checks simultaneously is likely to fail.)
+Lintian does not have any locking mechanisms yet. (Running several
+Lintian processes on the same laboratory simultaneously is likely to fail
+or corrupt the laboratory.)
If you discover any other bugs in lintian, please contact the authors.
--
Debian package checker
Reply to: