Commit 577e6c1b authored by Chris Lamb's avatar Chris Lamb 💬

Consistently use a single space after a full-stop/period.

parent 9b5392fe
......@@ -27,7 +27,7 @@ Info: This package contains a program in $PATH but is named like a
.
People tend to skip library-like named packages when looking for
applications in the package list and hence wouldn't notice this
package. See the reference for some (not perl-specific) reasoning.
package. See the reference for some (not perl-specific) reasoning.
.
In case the program in $PATH is only a helper tool and the package is
primarily a library, please add a Lintian override for this tag.
......
......@@ -8,7 +8,7 @@ Tag: appstream-metadata-in-legacy-location
Severity: minor
Certainty: certain
Ref: https://wiki.debian.org/AppStream/Guidelines
Info: AppStream metadata file was found in /usr/share/appdata/. The
Info: AppStream metadata file was found in /usr/share/appdata/. The
AppStream XML files should be placed in /usr/share/metainfo/.
Tag: appstream-metadata-legacy-format
......@@ -17,7 +17,7 @@ Certainty: certain
Ref: https://wiki.debian.org/AppStream/Guidelines,
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent
Info: AppStream metadata with obsolete <application> root node found.
This indicate a legacy format. The metadata should follow the format
This indicate a legacy format. The metadata should follow the format
the new outlined on the freedesktop.org homepage.
.
It is possible to validate the format using 'appstreamcli validate'.
......@@ -36,7 +36,7 @@ Severity: normal
Certainty: certain
Ref: https://wiki.debian.org/AppStream/Guidelines
Info: The modalias matching rule in the AppStream metadata file is
malformed. Hexadecimal numbers in vendor and product IDs must be
malformed. Hexadecimal numbers in vendor and product IDs must be
upper case.
Tag: appstream-metadata-invalid
......
......@@ -9,7 +9,7 @@ Tag: deprecated-configure-filename
Severity: wishlist
Certainty: certain
Info: The use of 'configure.in' with automake is deprecated and will
not be supported in future versions of automake. Please consider
not be supported in future versions of automake. Please consider
(helping upstream) migrating to 'configure.ac' instead.
Ref: https://lists.gnu.org/archive/html/automake/2013-05/msg00049.html
Experimental: yes
This diff is collapsed.
......@@ -21,14 +21,14 @@ Tag: html-changelog-without-text-version
Severity: important
Certainty: certain
Info: If the upstream changelog file is HTML formatted, a text version
should also be accessible as "changelog.gz". (This can be created by
should also be accessible as "changelog.gz". (This can be created by
"lynx -dump -nolist")
Ref: policy 12.7
Tag: changelog-file-not-compressed
Severity: important
Certainty: certain
Info: Changelog files should be compressed using "gzip -9". Even if they
Info: Changelog files should be compressed using "gzip -9". Even if they
start out small, they will become large with time.
Ref: policy 12.7
......@@ -42,7 +42,7 @@ Ref: policy 4.4
Tag: debian-news-file-not-compressed
Severity: normal
Certainty: certain
Info: NEWS.Debian files should be compressed using "gzip -9". The file
Info: NEWS.Debian files should be compressed using "gzip -9". The file
must always have the same name.
Ref: devref 6.3.4
......@@ -50,7 +50,7 @@ Tag: changelog-is-dh_make-template
Severity: important
Certainty: certain
Info: The changelog file has an instruction left by dh_make, which has
not been removed. Example:
not been removed. Example:
.
* Initial release (Closes: #nnnn) <nnnn is the bug number of your ITP>
.
......@@ -76,7 +76,7 @@ Tag: changelog-file-missing-in-native-package
Severity: important
Certainty: certain
Info: Each Debian package (which provides a /usr/share/doc/<i>pkg</i>
directory) has to install a changelog file. Since this package seems
directory) has to install a changelog file. Since this package seems
to be a native Debian package (i.e., there is no upstream source),
the file should usually be installed as
/usr/share/doc/<i>pkg</i>/changelog.gz
......@@ -146,7 +146,7 @@ Severity: normal
Certainty: certain
Info: The add-log-mailing-address variable is no longer honored in
debian-changelog-mode, and should not appear in packages' changelog
files. Instead, put something like this in your ~/.emacs:
files. Instead, put something like this in your ~/.emacs:
.
(setq debian-changelog-mailing-address "userid@debian.org")
......@@ -227,7 +227,7 @@ Certainty: possible
Info: The most recent changelog entry contains an entry that appears to
say this is a new upstream release (a comment similar to "new upstream
release," possibly with a word between "upstream" and "release"), but the
upstream portion of the package version number didn't change. This may
upstream portion of the package version number didn't change. This may
indicate that the package version was not updated properly in
<tt>debian/changelog</tt>.
......@@ -260,13 +260,13 @@ Ref: #906155, sbuild(1)
Tag: syntax-error-in-debian-changelog
Severity: normal
Certainty: possible
Info: While parsing the Debian changelog, a syntax error was found. If
Info: While parsing the Debian changelog, a syntax error was found. If
you have old changelog entries that don't follow the current syntax but
that you want to keep as-is for the historical record, add the line:
.
Old Changelog:
.
with no leading whitespace before the legacy entries. This line and
with no leading whitespace before the legacy entries. This line and
everything after it will be ignored.
Ref: policy 4.4
......@@ -293,7 +293,7 @@ Tag: possible-missing-colon-in-closes
Severity: important
Certainty: possible
Info: To close a bug in the Debian changelog, the word "closes" must be
followed by a colon. This entry looked like it was intended to close a
followed by a colon. This entry looked like it was intended to close a
bug, but there's no colon after "closes".
Ref: policy 4.4
......@@ -310,7 +310,7 @@ Tag: debian-news-entry-uses-asterisk
Severity: wishlist
Certainty: possible
Info: The latest entry in NEWS.Debian appears to use asterisks to present
changes in a bulleted list, similar to the normal changelog syntax. The
changes in a bulleted list, similar to the normal changelog syntax. The
Debian Developer's Reference recommends using regular paragraphs in
NEWS.Debian rather than a bulleted list.
Ref: devref 6.3.4
......@@ -320,7 +320,7 @@ Severity: normal
Certainty: possible
Info: The version number of the most recent <tt>NEWS.Debian</tt> entry
does not match any of the version numbers in the changelog file for this
package. This usually means the version in <tt>NEWS.Debian</tt> needs to
package. This usually means the version in <tt>NEWS.Debian</tt> needs to
be updated to match a change to package version that happened after the
<tt>NEWS.Debian</tt> entry was written.
......@@ -328,7 +328,7 @@ Tag: spelling-error-in-changelog
Severity: minor
Certainty: certain
Info: Lintian found a spelling error in the latest entry of the Debian
changelog. Lintian has a list of common misspellings that it looks for.
changelog. Lintian has a list of common misspellings that it looks for.
It does not have a dictionary like a spelling checker does.
.
When writing a changelog entry for a spelling fix that includes the
......@@ -339,15 +339,15 @@ Tag: spelling-error-in-news-debian
Severity: minor
Certainty: certain
Info: Lintian found a spelling error in the latest entry of the
NEWS.Debian file. Lintian has a list of common misspellings that it
looks for. It does not have a dictionary like a spelling checker does.
NEWS.Debian file. Lintian has a list of common misspellings that it
looks for. It does not have a dictionary like a spelling checker does.
Tag: new-package-should-close-itp-bug
Severity: normal
Certainty: certain
Info: This package appears to be the first packaging of a new upstream
software package (there is only one changelog entry and the Debian
revision is 1), but it does not close any bugs. The initial upload of a
revision is 1), but it does not close any bugs. The initial upload of a
new package should close the corresponding ITP bug for that package.
.
This warning can be ignored if the package is not intended for Debian or
......@@ -359,7 +359,7 @@ Severity: normal
Certainty: certain
Info: The given line of the latest changelog entry is over 80 columns.
Such changelog entries may look poor in terminal windows and mail
messages and be annoying to read. Please wrap changelog entries at 80
messages and be annoying to read. Please wrap changelog entries at 80
columns or less where possible.
Tag: debian-changelog-line-too-short
......@@ -388,7 +388,7 @@ Tag: changelog-news-debian-mismatch
Severity: normal
Certainty: possible
Info: The latest entries in the Debian changelog file and NEWS.Debian file
are for the same version but the given field doesn't match. The
are for the same version but the given field doesn't match. The
changelog information is canonical and the NEWS.Debian information is
ignored, but it may be confusing to users to have them be different.
......@@ -418,7 +418,7 @@ Tag: version-refers-to-distribution
Severity: minor
Certainty: certain
Info: The Debian portion of the package version contains a reference to a
particular Debian release or distribution. This should only be done for
particular Debian release or distribution. This should only be done for
uploads targeted at a particular release, not at unstable or
experimental, and should refer to the release by version number or code
name.
......@@ -433,10 +433,10 @@ Tag: debian-changelog-has-wrong-day-of-week
Severity: normal
Certainty: certain
Info: The date in the changelog entry is not consistent with the actual
day of that week. Either the date is wrong or the day of week is wrong.
day of that week. Either the date is wrong or the day of week is wrong.
.
To avoid problems like this, consider using a tool like dch(1) or
date(1) to generate the date. Example:
date(1) to generate the date. Example:
.
$ date -R -ud '2013-11-05 23:59:59'
Tue, 05 Nov 2013 23:59:59 +0000
......@@ -448,11 +448,11 @@ Info: The changelog entry references a temporary security identifier,
like "TEMP-0000000-2FC21E".
.
The TEMP identifier will disappear in the future once a proper CVE
identifier has been assigned. Therefore it is useless as an
external reference. Even worse, the identifier is not stable and
identifier has been assigned. Therefore it is useless as an
external reference. Even worse, the identifier is not stable and
may change even before a CVE is allocated.
.
If a CVE has been allocated, please use that instead. Otherwise,
If a CVE has been allocated, please use that instead. Otherwise,
please replace the TEMP identifier with a short description of the
issue.
Ref: #787929, #807892
......@@ -523,7 +523,7 @@ Info: The date format in the latest changelog entry file appears to be invalid.
day-of-week, dd month yyyy hh:mm:ss +zzzz
.
To avoid problems like this, consider using a tool like dch(1) or
date(1) to generate the date. Example:
date(1) to generate the date. Example:
.
$ date -R -ud '2013-11-05 23:59:59'
Tue, 05 Nov 2013 23:59:59 +0000
......
......@@ -6,8 +6,8 @@ Info: This script checks for various problems with .changes files
Tag: malformed-changes-file
Severity: serious
Certainty: certain
Info: There is no "Format" field in your .changes file. This probably
indicates some serious problem with the file. Perhaps it's not actually
Info: There is no "Format" field in your .changes file. This probably
indicates some serious problem with the file. Perhaps it's not actually
a changes file, or it's not in the proper format, or it's PGP-signed
twice.
.
......@@ -18,7 +18,7 @@ Ref: policy 5.5
Tag: no-description-in-changes-file
Severity: serious
Certainty: certain
Info: There is no "Description" field in your .changes file. A
Info: There is no "Description" field in your .changes file. A
description is mandatory and is usually constructed from the descriptions
in the control file of the package by the package build tools.
Ref: policy 5.5
......@@ -27,8 +27,8 @@ Tag: bad-distribution-in-changes-file
Severity: important
Certainty: certain
Info: You've specified an unknown target distribution for your upload in
the <tt>debian/changelog</tt> file. It is possible that you are uploading
for a different distribution than the one Lintian is checking for. In
the <tt>debian/changelog</tt> file. It is possible that you are uploading
for a different distribution than the one Lintian is checking for. In
that case, passing --profile $VENDOR may fix this warning.
.
Note that the distributions <tt>non-free</tt> and <tt>contrib</tt> are no
......@@ -44,14 +44,14 @@ Info: You've specified more than one target distribution for your upload
<tt>debian/changelog</tt> file.
.
Although this syntax is valid, it is not accepted by the Debian archive
management software. This may not be a problem if this upload is
management software. This may not be a problem if this upload is
targeted at an archive other than Debian's.
Ref: policy 5.6.14
Tag: no-urgency-in-changes-file
Severity: normal
Certainty: certain
Info: There is no "Urgency" field in the .changes file. This field is
Info: There is no "Urgency" field in the .changes file. This field is
recommended by policy and is usually derived from the first line of the
most recent changelog entry by the package build tools.
Ref: policy 5.5
......@@ -61,7 +61,7 @@ Severity: important
Certainty: certain
Info: The keyword value of the "Urgency" field in the .changes file is not
one of the allowed values of low, medium, high, critical, and emergency
(case-insensitive). This value normally taken from the first line of the
(case-insensitive). This value normally taken from the first line of the
most recent entry in <tt>debian/changelog</tt>, which is probably where
the error is.
Ref: policy 5.6.17
......@@ -107,7 +107,7 @@ Severity: serious
Certainty: certain
Info: The Changed-By field should contain the package builder's name and
email address, with the name followed by the address inside angle
brackets (&lt; and &gt;). The address seems to be missing.
brackets (&lt; and &gt;). The address seems to be missing.
Ref: policy 5.6.4
Tag: changed-by-address-malformed
......@@ -140,9 +140,9 @@ Info: The Changed-By address includes root user, which is
Tag: backports-changes-missing
Severity: wishlist
Certainty: possible
Info: The changes file only has changelog entries from a single version. It
Info: The changes file only has changelog entries from a single version. It
is recommended for backports to include all changes since (old)stable or
the previous backport. This can be done by adding the '-v' option to the
the previous backport. This can be done by adding the '-v' option to the
build with the appropriate version.
Ref: http://backports.debian.org/Contribute/, #785084
......
......@@ -10,16 +10,16 @@ Tag: file-in-usr-marked-as-conffile
Severity: serious
Certainty: certain
Ref: policy 10.7.2
Info: All configuration files must reside in <tt>/etc</tt>. Files below
Info: All configuration files must reside in <tt>/etc</tt>. Files below
<tt>/usr</tt> may not be marked as conffiles since <tt>/usr</tt> might be
mounted read-only. The local system administrator would therefore not
mounted read-only. The local system administrator would therefore not
have a chance to modify this configuration file.
Tag: non-etc-file-marked-as-conffile
Severity: serious
Certainty: possible
Info: A file installed in some other directory than <tt>/etc</tt>
is marked as conffile. A conffile typically implies a configuration
is marked as conffile. A conffile typically implies a configuration
file, and Policy mandates such files to be in <tt>/etc</tt>.
Ref: policy 10.7.2
......@@ -43,7 +43,7 @@ Severity: serious
Certainty: certain
Ref: policy 10.7
Info: Files in <tt>/etc</tt> must be marked conffiles if they are included
in a package. Otherwise they should be created by maintainer scripts.
in a package. Otherwise they should be created by maintainer scripts.
Tag: file-in-etc-rc.d-marked-as-conffile
Severity: important
......@@ -55,7 +55,7 @@ Tag: conffile-has-bad-file-type
Severity: important
Certainty: certain
Ref: #690051, #690910
Info: The conffiles lists this path, which is not a file. This will
Info: The conffiles lists this path, which is not a file. This will
almost certainly not work.
.
Note that dpkg does not support symlinks being conffiles.
......@@ -64,10 +64,10 @@ Tag: conffile-is-not-in-package
Severity: important
Certainty: certain
Info: The conffiles control file lists this path, but the path does
not appear to exist in the package. Lintian may also emit this tag
not appear to exist in the package. Lintian may also emit this tag
when the file exists, but the canonical name is used in the
"conffiles" control file (e.g. if a parent segment are symlinks).
.
Note that dpkg and Lintian strips all whitespace from the right hand
side of each line. Thus it is not possible for a file ending with
side of each line. Thus it is not possible for a file ending with
trailing whitespace to be marked as a conffile.
......@@ -24,7 +24,7 @@ Certainty: certain
Ref: policy 5.2
Info: The control file has a Build-Depends, Build-Depends-Indep,
Build-Conflicts, or Build-Conflicts-Indep field in a binary
section. These specify source package relationships, and should be in
section. These specify source package relationships, and should be in
the source section of the control file.
Tag: debian-control-has-unusual-field-spacing
......@@ -32,7 +32,7 @@ Severity: pedantic
Certainty: certain
Ref: policy 5.1
Info: The field on this line of <tt>debian/control</tt> has whitespace
other than a single space after the colon. This is explicitly permitted
other than a single space after the colon. This is explicitly permitted
in the syntax of Debian control files, but as Policy says, it is
conventional to put a single space after the colon.
......@@ -65,7 +65,7 @@ Severity: normal
Certainty: possible
Ref: policy 5.1
Info: The field on this line of <tt>debian/control</tt> repeats
the field name in the value of the field. As an example:
the field name in the value of the field. As an example:
.
Maintainer: Maintainer: Some Name &lt;maintainer@mail.example.com&gt;
......@@ -73,9 +73,9 @@ Tag: binary-control-field-duplicates-source
Severity: wishlist
Certainty: certain
Info: In <tt>debian/control</tt>, this field for a binary package
duplicates the value inherited from the source package paragraph. This
duplicates the value inherited from the source package paragraph. This
doesn't hurt anything, but you may want to take advantage of the
inheritance and set the value in only one place. It prevents missing
inheritance and set the value in only one place. It prevents missing
duplicate places that need to be fixed if the value ever changes.
Tag: debian-control-file-is-a-symlink
......@@ -92,7 +92,7 @@ Severity: normal
Certainty: certain
Ref: policy 5.2
Info: The package does not have a "Section:" field in the source package
section of its control file. The Section field is required for source
section of its control file. The Section field is required for source
packages at the request of the Debian ftp-masters.
Tag: section-area-mismatch
......@@ -100,7 +100,7 @@ Severity: important
Certainty: certain
Info: The <tt>debian/control</tt> file places the indicated binary package
in a different archive area (main, contrib, non-free) than its source
package or other binary packages built from the same source package. The
package or other binary packages built from the same source package. The
source package and any binary packages it builds must be in the same
area of the archive, with the single exception that source packages in
main may also build binary packages in contrib.
......@@ -108,19 +108,19 @@ Info: The <tt>debian/control</tt> file places the indicated binary package
Tag: xs-vcs-field-in-debian-control
Severity: wishlist
Certainty: certain
Info: There is an XS-Vcs-* field in the <tt>debian/control</tt> file. As
of dpkg 1.14.6, the XS- prefix is no longer necessary. dpkg now
recognizes these fields and handles them correctly. Consider removing
Info: There is an XS-Vcs-* field in the <tt>debian/control</tt> file. As
of dpkg 1.14.6, the XS- prefix is no longer necessary. dpkg now
recognizes these fields and handles them correctly. Consider removing
the XS- prefix for this field.
Tag: xs-testsuite-field-in-debian-control
Severity: wishlist
Certainty: certain
Info: There is an XS-Testsuite field in the <tt>debian/control</tt> file. As
of dpkg 1.17.10, the XS- prefix is no longer necessary. dpkg now
recognizes this field and handles it correctly. As of dpkg 1.17.11 the
Info: There is an XS-Testsuite field in the <tt>debian/control</tt> file. As
of dpkg 1.17.10, the XS- prefix is no longer necessary. dpkg now
recognizes this field and handles it correctly. As of dpkg 1.17.11 the
field is automatically added by dpkg-source with the value "autopkgtest" if
there is a non-empty <tt>debian/tests/control</tt> file present. Consider
there is a non-empty <tt>debian/tests/control</tt> file present. Consider
either removing the XS- prefix for this field or removing the field
altogether if it contains just the "autopkgtest" value.
......@@ -131,7 +131,7 @@ Info: The <tt>debian/control</tt> file contains an XC-Package-Type field.
As of dpkg-dev 1.15.7, the dpkg development utilities recognize
Package-Type as an official field name and do not add it to binary
packages (the previous concern with the dpkg-dev-supported Package-Type
field). XC-Package-Type should generally now be replaced with
field). XC-Package-Type should generally now be replaced with
Package-Type.
Tag: stronger-dependency-implies-weaker
......@@ -140,7 +140,7 @@ Certainty: certain
Ref: policy 7.2
Info: In the <tt>debian/control</tt> stanza for the given package, a
stronger dependency field implies one of the dependencies in a weaker
dependency field. In other words, the Depends field of the package
dependency field. In other words, the Depends field of the package
requires that one of the packages listed in Recommends or Suggests be
installed, or a package is listed in Recommends as well as Suggests.
.
......@@ -154,7 +154,7 @@ Severity: normal
Certainty: certain
Ref: policy 7.2
Info: The given package declares a dependency on itself in its
<tt>debian/control</tt> stanza. Current versions of dpkg-gencontrol will
<tt>debian/control</tt> stanza. Current versions of dpkg-gencontrol will
silently fix this problem by removing the dependency, but it may indicate
a more subtle bug (misspelling or cutting and pasting the wrong package
name).
......@@ -163,7 +163,7 @@ Tag: duplicate-short-description
Severity: wishlist
Certainty: possible
Info: The listed binary packages all share the same short description (the
first line of the Description control field). The package names may
first line of the Description control field). The package names may
provide enough additional information to distinguish between the
packages, but it's common to also add a word or two to the short
description to clarify the difference.
......@@ -181,8 +181,8 @@ Tag: duplicate-in-relation-field
Severity: pedantic
Certainty: certain
Info: The given field in the <tt>debian/control</tt> file contains
relations that are either identical or imply each other. The less
restrictive one can be removed. This is done automatically by
relations that are either identical or imply each other. The less
restrictive one can be removed. This is done automatically by
<tt>dpkg-source</tt> and <tt>dpkg-gencontrol</tt>, so this does not
affect the generated package.
......@@ -190,8 +190,8 @@ Tag: missing-separator-between-items
Severity: important
Certainty: certain
Info: The given field in the <tt>debian/control</tt> file contains a list
of items separated by commas and pipes. It appears a separator was
missed between two items. This can lead to bogus or incomplete
of items separated by commas and pipes. It appears a separator was
missed between two items. This can lead to bogus or incomplete
dependencies, conflicts etc.
Tag: obsolete-relation-form-in-source
......@@ -199,8 +199,8 @@ Ref: policy 7.1
Severity: serious
Certainty: certain
Info: The forms "&lt;" and "&gt;" mean "&lt;=" and "&gt;=", not "&lt;&lt;"
and "&gt;&gt;" as one might expect. These forms were marked obsolete and
must no longer be used. Use the longer forms instead.
and "&gt;&gt;" as one might expect. These forms were marked obsolete and
must no longer be used. Use the longer forms instead.
Tag: package-depends-on-hardcoded-libc
Severity: normal
......@@ -214,7 +214,7 @@ Certainty: possible
Ref: policy 8.5
Info: The given package appears to be a shared library -dev package, but
the dependency on what seems to be a corresponding shared library package
does not force the same package version. To ensure that compiling and
does not force the same package version. To ensure that compiling and
linking works properly, and that the symlinks in the -dev package point
to the correct files in the shared library package, a -dev package should
normally use <tt>(= ${binary:Version})</tt> for the dependency on the
......@@ -222,10 +222,10 @@ Info: The given package appears to be a shared library -dev package, but
.
Sometimes, such as for -dev packages that are architecture-independent to
not break binNMUs or when one doesn't want to force a tight dependency, a
weaker dependency is warranted. Something like <tt>(&gt;=
weaker dependency is warranted. Something like <tt>(&gt;=
${source:Upstream-Version}), (&lt;&lt;
${source:Upstream-Version}+1~)</tt>, possibly using
<tt>${source:Version}</tt> instead, is the right approach. 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.
......
......@@ -9,7 +9,7 @@ Tag: unknown-control-file
Severity: normal
Certainty: possible
Ref: policy 2.2*
Info: The package contains an unknown control file. Policy says that
Info: The package contains an unknown control file. Policy says that
putting additional files in the package control area is not generally a
good idea.
......
......@@ -45,7 +45,7 @@ Tag: copyright-file-contains-full-gpl-license
Severity: important
Certainty: certain
Info: The copyright file /usr/share/doc/<i>pkg</i>/copyright contains the
complete text of the GPL v1, v2, or v3. It should refer to the file
complete text of the GPL v1, v2, or v3. It should refer to the file
<tt>/usr/share/common-licenses/GPL-1</tt>, <tt>GPL-2</tt>, or
<tt>GPL-3</tt> instead.
Ref: policy 12.5
......@@ -54,7 +54,7 @@ Tag: copyright-file-contains-full-gfdl-license
Severity: important
Certainty: certain
Info: The copyright file /usr/share/doc/<i>pkg</i>/copyright contains the
complete text of the GFDL v1.2. It should refer to the file
complete text of the GFDL v1.2. It should refer to the file
<tt>/usr/share/common-licenses/GFDL-1.2</tt> instead.
Ref: policy 12.5
......@@ -62,7 +62,7 @@ Tag: copyright-file-contains-full-apache-2-license
Severity: important
Certainty: certain
Info: The copyright file /usr/share/doc/<i>pkg</i>/copyright contains the
complete text of the Apache 2.0 license. It should refer to the file
complete text of the Apache 2.0 license. It should refer to the file
<tt>/usr/share/common-licenses/Apache-2.0</tt> instead.
Ref: policy 12.5
......@@ -79,11 +79,11 @@ Info: If the package installs a symbolic link
directory within <i>pkg1</i> and copy the copyright file into that
directory.
.
Transitive dependencies are not allowed here. In other words, if the
Transitive dependencies are not allowed here. In other words, if the
documentation directory is shipped in <i>pkg3</i> and <i>pkg1</i> depends
on <i>pkg2</i>, which in turn depends on <i>pkg3</i>, that's still an
error. Copyright file extractors are not required to go more than one
level deep when resolving dependencies. Each package should have a
error. Copyright file extractors are not required to go more than one
level deep when resolving dependencies. Each package should have a
direct dependency on the package which includes its documentation
directory.
Ref: policy 12.5
......@@ -126,7 +126,7 @@ Tag: helper-templates-in-copyright
Severity: important
Certainty: certain
Info: The /usr/share/doc/<i>pkg</i>/copyright file still contains
template markers from a packaging helper. Please fill in the actual
template markers from a packaging helper. Please fill in the actual
license, upstream copyright holders, and download information about the
package and remove any remaining templates generated by the packaging
helper.
......@@ -273,13 +273,13 @@ Certainty: certain
Info: The copyright file contains the incomplete Debian packaging
copyright boilerplate from older versions of <tt>dh_make</tt>.
<tt>(C)</tt> alone is not considered a valid copyright notice in some
countries. The word <tt>Copyright</tt> or the © symbol should be used
countries. The word <tt>Copyright</tt> or the © symbol should be used
instead or in addition to <tt>(C)</tt>.
.
Copyright notices like this are, in any country that's a signatory to the
Berne Convention, not required to claim copyright on a work, but their
presence may allow claiming additional damages should a copyright case go
to court. If you provide a notice, you may as well provide one that's
to court. If you provide a notice, you may as well provide one that's
legally recognized in a broader range of countries.
Tag: copyright-without-copyright-notice
......@@ -287,30 +287,30 @@ Severity: normal
Certainty: certain
Ref: https://ftp-master.debian.org/REJECT-FAQ.html
Info: The copyright file for this package does not appear to contain a
copyright notice. You should copy the copyright notice from the upstream
source (or add one of your own for a native package). A copyright notice
copyright notice. You should copy the copyright notice from the upstream
source (or add one of your own for a native package). A copyright notice
must consist of Copyright, Copr., or the Unicode symbol of C in a circle
followed by the years and the copyright holder. A copyright notice is
followed by the years and the copyright holder. A copyright notice is
not required for a work to be copyrighted, but Debian requires the
copyright file include the authors and years of copyright, and including
a valid copyright notice is the best way to do that. Examples:
a valid copyright notice is the best way to do that. Examples:
.
Copyright YYYY Firstname Lastname &lt;address@example.com&gt;
Copr. YYYY-YYYY Firstname Lastname &lt;address@example.com&gt;
© YYYY,YYYY Firstname Lastname &lt;address@example.com&gt;
.
If the package is in the public domain rather than copyrighted, be sure
to mention "public domain" in the copyright file. Please be aware that
this is very rare and not the same as a DFSG-free license. True public
to mention "public domain" in the copyright file. Please be aware that
this is very rare and not the same as a DFSG-free license. True public
domain software is generally limited to such special cases as a work
product of a United States government agency.
Tag: spelling-error-in-copyright
Severity: minor
Certainty: possible
Info: Lintian found a spelling error in the copyright file. Lintian has a
list of common misspellings that it looks for. It does not have a
dictionary like a spelling checker does. If this is a spelling error in
Info: Lintian found a spelling error in the copyright file. Lintian has a
list of common misspellings that it looks for. It does not have a
dictionary like a spelling checker does. If this is a spelling error in
the upstream license, in supporting email messages, or a case of Lintian
being confused by non-English text, add an override.
......@@ -319,14 +319,14 @@ Severity: serious
Certainty: wild-guess
Info: This package appears to be covered by the GNU GPL but depends on
the OpenSSL libssl package and does not mention a license exemption or
exception for OpenSSL in its copyright file. The GPL (including version
exception for OpenSSL in its copyright file. The GPL (including version
3) is incompatible with some terms of the OpenSSL license, and therefore
Debian does not allow GPL-licensed code linked with OpenSSL libraries
unless there is a license exception explicitly permitting this.
.
If only the Debian packaging, or some other part of the package not
linked with OpenSSL, is covered by the GNU GPL, please add a Lintian
override for this tag. Lintian currently has no good way of
override for this tag. Lintian currently has no good way of
distinguishing between that case and problematic packages.
Tag: copyright-refers-to-symlink-license
......@@ -334,11 +334,11 @@ Severity: pedantic
Certainty: possible
Info: The copyright file refers to the versionless symlink in
<tt>/usr/share/common-licenses</tt> for the full text of the GPL, LGPL,
or GFDL license. This symlink is updated to point to the latest version
of the license when a new one is released. The package appears to allow
or GFDL license. This symlink is updated to point to the latest version
of the license when a new one is released. The package appears to allow
relicensing under later versions of its license, so this is legally
consistent, but it implies that Debian will relicense the package under
later versions of those licenses as they're released. It is normally
later versions of those licenses as they're released. It is normally
better to point to the version of the license the package references in
its license statement.
.
......@@ -357,7 +357,7 @@ Certainty: possible
Info: The copyright file refers to the versionless symlink in
<tt>/usr/share/common-licenses</tt> for the full text of the GPL, LGPL,
or GFDL license, but the package does not appear to allow distribution
under later versions of the license. This symlink will change with each
under later versions of the license. This symlink will change with each
release of a new version of the license and may therefore point to a
different version than the package is released under.
<tt>debian/copyright</tt> should instead refers to the specific version
......@@ -373,7 +373,7 @@ Tag: copyright-refers-to-nonexistent-license-file
Severity: normal
Certainty: certain
Info: The copyright file refers to a license in
<tt>/usr/share/common-licenses</tt> that doesn't exist. Usually this is
<tt>/usr/share/common-licenses</tt> that doesn't exist. Usually this is
a typo, such as accidentally omitting the <tt>-</tt> between the license
name and the version number.
......@@ -382,7 +382,7 @@ Severity: minor
Certainty: certain
Ref: policy 12.5
Info: The copyright file refers to
<tt>/usr/share/common-licenses/BSD</tt>. Due to the brevity of this
<tt>/usr/share/common-licenses/BSD</tt>. Due to the brevity of this
license, the specificity of this copy to code whose copyright is held by
the Regents of the University of California, and the frequency of minor
wording changes in the license, its text should be included in the
......
This diff is collapsed.
......@@ -8,11 +8,11 @@ Info: This script checks the format of the deb ar archive itself.
Tag: malformed-deb-archive
Severity: serious
Certainty: certain
Info: The binary package is not a correctly constructed archive. A binary
Info: The binary package is not a correctly constructed archive. A binary
Debian package must be an ar archive with exactly three members: