[SCM] Debian package checker branch, master, updated. 2.5.13-37-g4bbd15c
The following commit has been merged in the master branch:
commit 4bbd15cfd8d5fe22c32d4c83dedde01408310c93
Author: Jakub Wilk <jwilk@debian.org>
Date: Sun Jun 23 08:08:42 2013 +0200
checks/*.desc: Fix various typoes
Signed-off-by: Niels Thykier <niels@thykier.net>
diff --git a/checks/apache2.desc b/checks/apache2.desc
index 09f1ed6..a207c8d 100644
--- a/checks/apache2.desc
+++ b/checks/apache2.desc
@@ -23,7 +23,7 @@ Info: The package is an Apache2 HTTPD server module but it depends on a real
future.
.
In particular, module packages must not pull the full web server or any of its
- associated data packages as a depdendency. That's left to the user.
+ associated data packages as a dependency. That's left to the user.
Tag: apache2-module-does-not-depend-on-apache2-api
@@ -58,7 +58,7 @@ Severity: normal
Certainty: certain
Info: The package appears to be a web application which is installing a
configuration file for the Apache2 HTTPD server. To avoid name clashes, any file
- installed to <tt>/etc/apache2/{sites,conf}-availabe</tt> should match the binary package
+ installed to <tt>/etc/apache2/{sites,conf}-available</tt> should match the binary package
name and must not start with <tt>local-</tt>.
@@ -98,7 +98,7 @@ Severity: normal
Certainty: certain
Info: The package is invoking apache2's init script in its maintainer script
albeit it shouldn't do so. Reverse dependencies installing apache2
- configuration pieces should not restart the web server uncondtionally in
+ configuration pieces should not restart the web server unconditionally in
maintainer scripts. Instead they should be using apache2-maintscript-helper
which correctly obeys local policies.
diff --git a/checks/control-file.desc b/checks/control-file.desc
index a2f04fd..6fb786d 100644
--- a/checks/control-file.desc
+++ b/checks/control-file.desc
@@ -181,7 +181,7 @@ Info: The given package appears to be a shared library -dev package, but
weaker dependency is warranted. Something like <tt>(>=
${source:Upstream-Version}), (<<
${source:Upstream-Version}+1~)</tt>, possibly using
- <tt>${source:Version}</tt> instead, is the right apprach. The goal is to
+ <tt>${source:Version}</tt> instead, is the right approach. The goal is to
ensure that a new upstream version of the library package doesn't satisfy
the -dev package dependency, since the minor version of the shared
library may have changed, breaking the <tt>*.so</tt> links.
diff --git a/checks/debhelper.desc b/checks/debhelper.desc
index 49ec999..61748ec 100644
--- a/checks/debhelper.desc
+++ b/checks/debhelper.desc
@@ -209,7 +209,7 @@ Tag: weak-dependency-on-misc-depends
Severity: normal
Certainty: possible
Ref: debhelper(7)
-Info: The source package declares a weak dependecy on ${misc:Depends} in
+Info: The source package declares a weak dependency on ${misc:Depends} in
the given binary package's debian/control entry. A stronger dependency, that
is one that ensures the package's installation, is required so that the
additional commands are available to the maintainer scripts when they are run.
@@ -266,7 +266,7 @@ Info: The source package declares a dependency on ${python3:Depends} in the
Tag: package-file-is-executable
Severity: normal
Certainty: certain
-Info: The packaging file is marked exectuable. For control, changelog and
+Info: The packaging file is marked executable. For control, changelog and
copyright there is no reason for them to be executable.
.
This tag is also emitted if a debhelper file is marked executable without
@@ -276,7 +276,7 @@ Info: The packaging file is marked exectuable. For control, changelog and
Tag: executable-debhelper-file-without-being-executable
Severity: important
Certainty: possible
-Info: The packaging file is marked exectuable, but it does not appear to be
+Info: The packaging file is marked executable, but it does not appear to be
executable (e.g. it has no #! line).
.
If debhelper file is not supposed to be executable, please remove the
@@ -309,7 +309,7 @@ Info: The package uses dh-exec in at least one of its files, but does
Tag: dh-exec-install-not-allowed-here
Severity: important
Certainty: possible
-Info: The package uses a dh-exec-install contruct in a non-.install
+Info: The package uses a dh-exec-install construct in a non-.install
file.
.
The dh-exec-install constructs are only allowed in dh_install's
@@ -323,16 +323,16 @@ Info: The package uses a variable in one of its debhelper config
.
It is recommended to use a known subset of variables. If the package
needs more than that, and makes sure the variable is exported through
- the build one way or the othern, then this tag can be safely ignored
+ the build one way or the other, then this tag can be safely ignored
or overridden.
Tag: debhelper-compat-file-is-missing
Severity: normal
Certainty: certain
Info: The package uses debhelper but does not ship a compat file.
- This is deprecated and eventaully cause the package to FTBFS.
+ This is deprecated and eventually cause the package to FTBFS.
.
- Please refer to the dehelper documentation on how to create the
+ Please refer to the debhelper documentation on how to create the
compat file and the differences between each compat level.
Ref: http://packages.qa.debian.org/d/debhelper/news/20120115T191738Z.html,
debhelper(7)
diff --git a/checks/debian-source-dir.desc b/checks/debian-source-dir.desc
index c252881..e22c19f 100644
--- a/checks/debian-source-dir.desc
+++ b/checks/debian-source-dir.desc
@@ -30,7 +30,7 @@ Severity: serious
Certainty: certain
Info: <tt>debian/source/format</tt> contains an unknown source format. The
formats officially supported by Debian are "3.0 (quilt)", "3.0 (native)"
- and "1.0". dpkg-source additionnaly supports "2.0", "3.0 (git)" and
+ and "1.0". dpkg-source additionally supports "2.0", "3.0 (git)" and
"3.0 (bzr)".
Ref: dpkg-source(1)
diff --git a/checks/files.desc b/checks/files.desc
index 0516fcb..ad12175 100644
--- a/checks/files.desc
+++ b/checks/files.desc
@@ -974,7 +974,7 @@ Severity: serious
Certainty: possible
Info: This type 1 font file includes some postscript fragment with a
non free license of Adobe. In order to check if this tag is genuine
- please follow the proceedure described in the reference.
+ please follow the procedure described in the reference.
.
Should this be a false-positive, please override the tag.
Ref: http://wiki.debian.org/qa.debian.org/type1nondfsg
@@ -984,7 +984,7 @@ Severity: serious
Certainty: possible
Info: This type 1 font file includes some postscript fragment with a
non free license of Adobe. In order to check if this tag is genuine
- please follow the proceedure described in the reference.
+ please follow the procedure described in the reference.
.
Moreover the fragment was likely verbatim copied from black
book without any credit to Adobe.
diff --git a/checks/group-checks.desc b/checks/group-checks.desc
index ef0a158..84843a6 100644
--- a/checks/group-checks.desc
+++ b/checks/group-checks.desc
@@ -61,7 +61,7 @@ Info: The debug package appear to be containing debug symbols for a
symbols for all architecture variants of the binaries available
at the same time.
.
- Making a debug package co-installable with itself is very trival,
+ Making a debug package co-installable with itself is very trivial,
when installing the debug symbols beneath:
<tt>/usr/lib/debug/.build-id/<XX>/<rest-id>.debug</tt>
.
diff --git a/checks/java.desc b/checks/java.desc
index 43c3a1b..fc8f986 100644
--- a/checks/java.desc
+++ b/checks/java.desc
@@ -102,7 +102,7 @@ Info: The package contains a Jar file with Java class files compiled for an
for a newer version of Java than Lintian knows about. In the latter case,
please file a bug against Lintian.
.
- Lastest class version known by Lintian is Java7 (Major version 51).
+ Latest class version known by Lintian is Java7 (Major version 51).
Tag: zip-parse-error
Severity: normal
diff --git a/checks/nmu.desc b/checks/nmu.desc
index 2ea03bb..08048a8 100644
--- a/checks/nmu.desc
+++ b/checks/nmu.desc
@@ -34,7 +34,7 @@ Info: A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a
maintainer.
.
Maybe you didn't intend this upload to be a NMU, in that case, please
- doublecheck that the most recent entry in the changelog is byte-for-byte
+ double-check that the most recent entry in the changelog is byte-for-byte
identical to the maintainer or one of the uploaders. If this is a local
package (not intended for Debian), you can suppress this warning by
putting "local" in the version number or "local package" on the first
@@ -64,7 +64,7 @@ Info: When you NMU a package, that fact should be mentioned on the first line
(case insensitive).
.
Maybe you didn't intend this upload to be a NMU, in that case, please
- doublecheck that the most recent entry in the changelog is byte-for-byte
+ double-check that the most recent entry in the changelog is byte-for-byte
identical to the maintainer or one of the uploaders. If this is a local
package (not intended for Debian), you can suppress this warning by
putting "local" in the version number or "local package" on the first
diff --git a/debian/changelog b/debian/changelog
index 4d674e3..a053a66 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,7 @@ lintian (2.5.14) UNRELEASED; urgency=low
* checks/*:
+ [NT] Rename all checks to include the extension ".pm".
(Closes: #710405)
+ + [JW] Fix typoes in several files.
* checks/binaries.pm:
+ [NT] Also check for the presence of "mcount" to detect
whether a binary was compiled with profiling.
--
Debian package checker
Reply to: