[SCM] Debian package checker branch, master, updated. 2.1.6-12-gca85ece
The following commit has been merged in the master branch:
commit b7350918f2a5c6cd75b674c0bf709f898cb09b77
Author: Russ Allbery <rra@debian.org>
Date: Sat Jan 24 00:16:00 2009 -0800
Replace `' quotes with ""
* checks/*.desc:
+ [RA] Replace `' "balanced" quotes with straight double-quotes. The
old style looks strange with modern fonts. Based on work by Raphael
Geissert.
* collection/*.desc:
+ [RA] Replace `' "balanced" quotes with straight double-quotes. The
old style looks strange with modern fonts. Based on work by Raphael
Geissert.
diff --git a/checks/binaries.desc b/checks/binaries.desc
index f540f85..dfc0c25 100644
--- a/checks/binaries.desc
+++ b/checks/binaries.desc
@@ -97,12 +97,12 @@ Tag: shared-lib-without-dependency-information
Severity: normal
Certainty: certain
Info: The listed shared library doesn't include information about which
- other libraries the library was linked against. (When running `<tt>ldd
- foo.so</tt>' ldd should report about these other libraries. In your
- case, ldd just reports `statically linked'.)
+ other libraries the library was linked against. (When running "<tt>ldd
+ foo.so</tt>" ldd should report about these other libraries. In your
+ case, ldd just reports "statically linked".)
.
To fix this, you should explicitly specify the libraries which are
- used (e.g., `-lc') when building the shared library with `ld'.
+ used (e.g., "-lc") when building the shared library with "ld".
.
If you have questions about this, please contact &debdev;.
diff --git a/checks/conffiles.desc b/checks/conffiles.desc
index a1dd805..3792bef 100644
--- a/checks/conffiles.desc
+++ b/checks/conffiles.desc
@@ -3,7 +3,7 @@ Author: Christian Schwarz <schwarz@debian.org>
Abbrev: cnf
Type: binary
Unpack-Level: 1
-Info: This script checks if the `conffiles' control file of a binary
+Info: This script checks if the conffiles control file of a binary
package is correct.
Tag: file-in-usr-marked-as-conffile
@@ -26,8 +26,8 @@ Tag: relative-conffile
Severity: important
Certainty: certain
Ref: policy E.1
-Info: All entries in the conffile control file should have an absolute
- path specification.
+Info: All entries in the <tt>debian/conffiles</tt> control file should
+ have an absolute path specification.
Tag: duplicate-conffile
Severity: important
diff --git a/checks/copyright-file.desc b/checks/copyright-file.desc
index 2497d5b..238dee1 100644
--- a/checks/copyright-file.desc
+++ b/checks/copyright-file.desc
@@ -7,10 +7,11 @@ Needs-Info: copyright-file
Info: This script checks if a binary package conforms to policy
with regard to copyright files.
.
- Each binary package must either have a /usr/share/doc/<foo>/copyright file
- or must have a symlink /usr/share/doc/<foo> -> <bar>, where <bar> comes
- from the same source package and pkg foo declares a "Depends" relation
- on bar.
+ Each binary package must either have a
+ /usr/share/doc/<foo>/copyright file or must have a symlink
+ /usr/share/doc/<foo> -> <bar>, where <bar> comes
+ from the same source package and pkg foo declares a "Depends" relation on
+ bar.
Tag: no-copyright-file
Severity: serious
@@ -150,7 +151,7 @@ Severity: important
Certainty: certain
Ref: policy 12.5
Info: In the directory name /usr/share/common-licenses, licenses is spelled
- with an `s', not as licences with a `c'.
+ with an "s", not as licences with a "c".
Tag: copyright-file-lacks-pointer-to-perl-license
Severity: important
diff --git a/checks/debconf.desc b/checks/debconf.desc
index 5b34b66..cfab964 100644
--- a/checks/debconf.desc
+++ b/checks/debconf.desc
@@ -30,33 +30,33 @@ Info: A template contains two identical fields (with identical values or
Tag: unknown-field-in-templates
Severity: important
Certainty: certain
-Info: Valid fields are currently `Template:', `Type:', `Choices:', `Default:',
- and `Description:'.
+Info: Valid fields are currently "Template:", "Type:", "Choices:", "Default:",
+ and "Description:".
Ref: debconf-spec aen45, debconf-devel(7)
Tag: no-template-name
Severity: important
Certainty: certain
-Info: The templates file contains a template without a `Template:' field.
+Info: The templates file contains a template without a "Template:" field.
Tag: malformed-template-name
Severity: important
Certainty: certain
-Info: The `Template:' field should contain more than one component, each
- separated by a slash (`/'). Each component may only consist of the
- alphanumeric characters, `+', `-', and `.'.
+Info: The "Template:" field should contain more than one component, each
+ separated by a slash ("/"). Each component may only consist of the
+ alphanumeric characters, "+", "-", and ".".
Tag: no-template-type
Severity: important
Certainty: certain
-Info: The templates file contains a template without a `Type:' field.
+Info: The templates file contains a template without a "Type:" field.
Tag: unknown-template-type
Severity: important
Certainty: certain
-Info: A `Type:' field in a templates file provided by this package uses an
- unknown data type. Valid types are currently `string', `boolean', `select',
- `multiselect', `note', `text', and `password'.
+Info: A "Type:" field in a templates file provided by this package uses an
+ unknown data type. Valid types are currently "string", "boolean", "select",
+ "multiselect", "note", "text", and "password".
Tag: empty-translated-choices
Severity: important
@@ -68,10 +68,10 @@ Info: When the translation of a Choices: field is empty, the whole question
Tag: mismatch-translated-choices
Severity: important
Certainty: certain
-Info: A `Choices:' field is a comma separated list, and translated
- `Choices:' fields must have the exact same number of elements. One
+Info: A "Choices:" field is a comma separated list, and translated
+ "Choices:" fields must have the exact same number of elements. One
of the translations does not follow this rule, you should contact the
- translator and request for a new translation where elements of `Choices:'
+ translator and request for a new translation where elements of "Choices:"
fields have no embedded commas.
.
Cdebconf understands escaped commas in such fields, but packages
@@ -81,21 +81,21 @@ Info: A `Choices:' field is a comma separated list, and translated
Tag: select-without-choices
Severity: important
Certainty: certain
-Info: Templates using the `select' or `multiselect' data types must provide
- a `Choices:' field listing the possible values of the template.
+Info: Templates using the "select" or "multiselect" data types must provide
+ a "Choices:" field listing the possible values of the template.
Ref: debconf-spec aen45, debconf-devel(7)
Tag: boolean-template-has-bogus-default
Severity: important
Certainty: certain
-Info: The `boolean' type in a debconf template, can have only two values: true
+Info: The "boolean" type in a debconf template, can have only two values: true
and false. The default has been set to something different.
Ref: debconf-spec aen45, debconf-devel(7)
Tag: no-template-description
Severity: important
Certainty: certain
-Info: The templates file contains a template without a `Description:' field.
+Info: The templates file contains a template without a "Description:" field.
Ref: debconf-spec aen45, debconf-devel(7)
Tag: duplicate-long-description-in-template
@@ -143,8 +143,8 @@ Info: Packages using debconf should call <tt>db_purge</tt> or its equivalent
Tag: isdefault-flag-is-deprecated
Severity: normal
Certainty: possible
-Info: The 'isdefault' flag on debconf questions is deprecated as of debconf
- 0.5.00, and has been replaced by 'seen' with the inverse meaning. From
+Info: The "isdefault" flag on debconf questions is deprecated as of debconf
+ 0.5.00, and has been replaced by "seen" with the inverse meaning. From
debconf 0.5 onwards there should be very few reasons to use isdefault/seen
anyway, as backing up works much better now. See
/usr/share/doc/debconf-doc/changelog.gz for more information.
@@ -156,39 +156,39 @@ Info: The 'isdefault' flag on debconf questions is deprecated as of debconf
Tag: debconf-config-not-executable
Severity: important
Certainty: certain
-Info: The debconf `config' script in the package control area must be
+Info: The debconf "config" script in the package control area must be
executable.
Tag: no-debconf-config
Severity: important
Certainty: possible
-Info: The package contains a `templates' file in its control area but has no
- corresponding `config' script. This is occasionally OK, but is usually an
+Info: The package contains a "templates" file in its control area but has no
+ corresponding "config" script. This is occasionally OK, but is usually an
error.
Tag: no-debconf-templates
Severity: normal
Certainty: possible
-Info: The package contains a `config' script in its control area but has no
- corresponding `templates' file. This is occasionally OK, but is usually an
+Info: The package contains a "config" script in its control area but has no
+ corresponding "templates" file. This is occasionally OK, but is usually an
error.
Tag: debconf-is-not-a-registry
Severity: important
Certainty: wild-guess
Info: In the Unix tradition, Debian packages should have human-readable and
- human-editable configuration files. This package uses debconf commands
+ human-editable configuration files. This package uses debconf commands
outside its maintainer scripts, which often indicates that it is taking
- configuration information directly from the debconf database. Typically,
- packages should use debconf-supplied information to generate configuration
- files, and - to avoid losing configuration information on upgrades - should
- parse these configuration files in the `config' script if it is necessary
- to ask the user for changes.
+ configuration information directly from the debconf database. Typically,
+ packages should use debconf-supplied information to generate
+ configuration files, and -- to avoid losing configuration information on
+ upgrades -- should parse these configuration files in the <tt>config</tt>
+ script if it is necessary to ask the user for changes.
.
Some standalone programs may legitimately use debconf to prompt the user
- for questions. If you maintain a package containing such a program, please
- install an override. Other exceptions to this check include configuration
- scripts called from the package's post-installation script.
+ for questions. If you maintain a package containing such a program,
+ please install an override. Other exceptions to this check include
+ configuration scripts called from the package's post-installation script.
Ref: devref 6.5.1, debconf-devel(7)
Tag: malformed-prompt-in-templates
@@ -344,7 +344,7 @@ Info: Templates which are not used by the package should be removed from
.
- the maintainer scripts embed a variable in the template name in
order to allow a template to be selected from a range of similar
- templates (e.g. 'db_input low start_$service_at_boot')
+ templates (e.g. <tt>db_input low start_$service_at_boot</tt>)
.
- the template is not used by the maintainer scripts but is used by
a program in the package
diff --git a/checks/description.desc b/checks/description.desc
index 08ef1c1..46546e0 100644
--- a/checks/description.desc
+++ b/checks/description.desc
@@ -57,7 +57,7 @@ Severity: important
Certainty: certain
Info: The first line of the "Description:" should not start with the
package name. For example, the package <tt>foo</tt> should not
- have a description like this: `foo is a program that...'.
+ have a description like this: "foo is a program that...".
Ref: policy 3.4.1
Tag: description-contains-tabs
@@ -70,7 +70,7 @@ Tag: description-starts-with-leading-spaces
Severity: normal
Certainty: possible
Info: The package "Description:" starts with leading spaces. Usually,
- leading spaces are used to switch `verbatim display' on (i.e., lines
+ leading spaces are used to switch "verbatim display" on (i.e., lines
are not wrapped) so this might be a bug in the package.
Tag: possible-unindented-list-in-extended-description
diff --git a/checks/fields.desc b/checks/fields.desc
index 93874d6..c8e904d 100644
--- a/checks/fields.desc
+++ b/checks/fields.desc
@@ -10,14 +10,14 @@ Info: This script checks the syntax of the fields in package control files,
Tag: no-package-name
Severity: serious
Certainty: certain
-Info: The package does not have a `Package:' field in its control file.
+Info: The package does not have a "Package:" field in its control file.
Ref: policy 5.3
Tag: bad-package-name
Severity: serious
Certainty: certain
Info: A package name should be at least two characters long, must consist
- of the alphanumerics and `+' `-' and `.', and must start with an
+ of the alphanumerics and "+" "-" and ".", and must start with an
alphanumeric character.
Ref: policy 5.6.7
@@ -30,7 +30,7 @@ Ref: policy 5.6.7
Tag: no-version-field
Severity: serious
Certainty: certain
-Info: The package does not have a `Version:' field in its control file.
+Info: The package does not have a "Version:" field in its control file.
Ref: policy 5.3
Tag: bad-version-number
@@ -66,13 +66,13 @@ Ref: devref 5.11.2
Tag: no-architecture-field
Severity: serious
Certainty: certain
-Info: The package does not have an `Architecture:' field in its control file.
+Info: The package does not have an "Architecture:" field in its control file.
Ref: policy 5.3
Tag: magic-arch-in-arch-list
Severity: serious
Certainty: certain
-Info: The special architecture values `all' and `any' only make sense if
+Info: The special architecture values "all" and "any" only make sense if
they occur alone.
Ref: policy 5.6.8
@@ -89,13 +89,13 @@ Tag: too-many-architectures
Severity: serious
Certainty: certain
Info: A binary package should list exactly one architecture (the one it is
- compiled for), or the special value `all' if it is architecture-independent.
+ compiled for), or the special value "all" if it is architecture-independent.
Ref: policy 5.6.8
Tag: arch-any-in-binary-pkg
Severity: serious
Certainty: certain
-Info: The special architecture value `any' does not make sense in a binary
+Info: The special architecture value "any" does not make sense in a binary
package.
Ref: policy 5.6.8
@@ -111,7 +111,7 @@ Ref: aspell-autobuildhash(8)
Tag: no-maintainer-field
Severity: serious
Certainty: certain
-Info: The package does not have a `Maintainer:' field in its control file.
+Info: The package does not have a "Maintainer:" field in its control file.
Ref: policy 5.3
Tag: maintainer-name-missing
@@ -139,7 +139,7 @@ Ref: policy 5.6.2
Tag: maintainer-not-full-name
Severity: normal
Certainty: possible
-Info: The `name' part of this maintainer field is just one word, so it
+Info: The "name" part of this maintainer field is just one word, so it
might not be a full name.
Tag: maintainer-address-looks-weird
@@ -180,7 +180,7 @@ Ref: policy 5.6.2
Tag: uploader-not-full-name
Severity: normal
Certainty: possible
-Info: The `name' part of this uploader field is just one word, so it
+Info: The "name" part of this uploader field is just one word, so it
might not be a full name.
Tag: uploader-address-looks-weird
@@ -224,7 +224,7 @@ Ref: devref 5.12
Tag: no-source-field
Severity: serious
Certainty: certain
-Info: The package does not have a `Source:' field in its control file.
+Info: The package does not have a "Source:" field in its control file.
Ref: policy 5.2
Tag: source-field-does-not-match-pkg-name
@@ -252,7 +252,7 @@ Ref: policy 5.6.9
Tag: essential-no-not-needed
Severity: normal
Certainty: certain
-Info: Having `Essential: no' is the same as not having the field at all,
+Info: Having "Essential: no" is the same as not having the field at all,
so it just makes the Packages file longer with no benefit.
Ref: policy 5.6.9
@@ -265,7 +265,7 @@ Ref: policy 5.6.9
Tag: no-section-field
Severity: normal
Certainty: certain
-Info: The package does not have a `Section:' field in its control file.
+Info: The package does not have a "Section:" field in its control file.
.
The field is mandatory for source packages and optional for binary
packages, which use the source package's value as default is nothing
@@ -275,22 +275,22 @@ Ref: policy 5.3
Tag: unknown-section
Severity: normal
Certainty: certain
-Info: The `Section:' field in this package's control file is not one of
+Info: The "Section:" field in this package's control file is not one of
the sections in use on the ftp archive. Valid sections are currently
admin, comm, devel, doc, editors, electronics, embedded, games,
gnome, graphics, hamradio, interpreters, kde, libdevel, libs, mail,
math, misc, net, news, oldlibs, otherosfs, perl, python, science, shells,
sound, tex, text, utils, web, and x11.
.
- The section name should be preceded by `non-free/' if the package
- is in the non-free distribution, and by `contrib/' if the package
+ The section name should be preceded by "non-free/" if the package
+ is in the non-free distribution, and by "contrib/" if the package
is in the contrib distribution.
Ref: policy 2.4
Tag: section-is-dh_make-template
Severity: important
Certainty: certain
-Info: The `Section:' field in this package's control file is set to
+Info: The "Section:" field in this package's control file is set to
unknown. This is not a valid section, and usually means a dh_make
template control file was used and never modified to set the correct
section.
@@ -299,12 +299,12 @@ Ref: policy 2.4
Tag: wrong-section-for-udeb
Severity: normal
Certainty: certain
-Info: udeb packages should have `Section: debian-installer'.
+Info: udeb packages should have "Section: debian-installer".
Tag: no-priority-field
Severity: normal
Certainty: certain
-Info: The package does not have a `Priority:' field in its control file.
+Info: The package does not have a "Priority:" field in its control file.
.
The Priority field can be included in a binary package by passing
the -ip or -isp flags to dpkg-gencontrol when building the package.
@@ -314,14 +314,14 @@ Ref: policy 5.3
Tag: unknown-priority
Severity: important
Certainty: certain
-Info: The `Priority:' field in this package's control file is not one of
+Info: The "Priority:" field in this package's control file is not one of
the priorities defined in the Policy Manual.
Ref: policy 2.5
Tag: superfluous-clutter-in-homepage
Severity: normal
Certainty: certain
-Info: The `Homepage:' field in this package's control file contains
+Info: The "Homepage:" field in this package's control file contains
superfluous markup around the URL, like enclosing < and >.
This is unnecessary and needlessly complicates using this information.
Ref: policy 5.6.23
@@ -329,7 +329,7 @@ Ref: policy 5.6.23
Tag: bad-homepage
Severity: normal
Certainty: certain
-Info: The `Homepage:' field in this package's control file does not
+Info: The "Homepage:" field in this package's control file does not
contain a valid absolute URL. Most probably you forgot to specify
the scheme (e.g. http).
@@ -367,22 +367,22 @@ Ref: policy 5.1
Tag: alternates-not-allowed
Severity: important
Certainty: certain
-Info: Only the `Depends', `Recommends', `Suggests' and `Pre-Depends'
- fields may specify alternate dependencies using the `|' symbol.
+Info: Only the "Depends", "Recommends", "Suggests" and "Pre-Depends"
+ fields may specify alternate dependencies using the "|" symbol.
Ref: policy 7.1
Tag: versioned-provides
Severity: important
Certainty: certain
Ref: policy 7.1
-Info: The `Provides' field may not specify a version range.
+Info: The "Provides" field may not specify a version range.
Tag: obsolete-relation-form
Ref: policy 7.1
Severity: normal
Certainty: certain
-Info: The forms `<' and `>' mean `<=' and `>=', not `<<'
- and `>>' as one might expect. For that reason these forms are
+Info: The forms "<" and ">" mean "<=" and ">=", not "<<"
+ and ">>" as one might expect. For that reason these forms are
obsolete, and should not be used in new packages. Use the longer forms
instead.
diff --git a/checks/files.desc b/checks/files.desc
index ca41c12..22276b8 100644
--- a/checks/files.desc
+++ b/checks/files.desc
@@ -191,7 +191,7 @@ Certainty: certain
Info: The package installs a binary which uses a very short file name (one
or two characters). This is not forbidden by policy, but short names
should be reserved for the user. Unless this short name has been used
- for a while already (like the famous `ls', `rm', `cp' commands), you
+ for a while already (like the famous "ls", "rm", "cp" commands), you
should consider giving these binaries a longer name.
Tag: non-standard-dir-perm
@@ -358,7 +358,7 @@ Info: Scripts are usually not documentation files, unless they are
Tag: symlink-has-too-many-up-segments
Severity: important
Certainty: certain
-Info: The symlink references a directory beyond the root directory `/'.
+Info: The symlink references a directory beyond the root directory "/".
Tag: lengthy-symlink
Severity: important
@@ -381,7 +381,7 @@ Info: The symbolic link is recursive to a higher directory of the symlink
Tag: symlink-contains-spurious-segments
Severity: important
Certainty: certain
-Info: The symbolic link has needless segments like '..' and '.' in the middle.
+Info: The symbolic link has needless segments like ".." and "." in the middle.
These are unneeded, and make the link longer than it could be, which is in
violation of policy.
.
diff --git a/checks/manpages.desc b/checks/manpages.desc
index 4700e3c..600487f 100644
--- a/checks/manpages.desc
+++ b/checks/manpages.desc
@@ -10,9 +10,9 @@ Tag: bad-link-to-undocumented-manpage
Severity: important
Certainty: certain
Info: The symbolic link should reference
- `<tt>../man[237]/undocumented.[237].gz</tt>' for manual pages in
+ "<tt>../man[237]/undocumented.[237].gz</tt>" for manual pages in
<tt>/usr/share/man</tt> or
- `<tt>../../../share/man/man[237]/undocumented.[237].gz</tt>' for manual
+ "<tt>../../../share/man/man[237]/undocumented.[237].gz</tt>" for manual
pages in <tt>/usr/X11R6/man</tt>.
Tag: link-to-undocumented-manpage
@@ -70,13 +70,13 @@ Tag: manpage-has-wrong-extension
Severity: important
Certainty: certain
Info: The manual page has an extension other than
- `<i>section</i>[<i>program</i>].gz'.
+ "<i>section</i>[<i>program</i>].gz".
Ref: policy 12.1
Tag: manpage-not-compressed
Severity: important
Certainty: certain
-Info: Manual pages have to be installed compressed (using `<tt>gzip -9</tt>').
+Info: Manual pages have to be installed compressed (using "<tt>gzip -9</tt>").
Ref: policy 12.1
Tag: x11-games-should-be-in-usr-games
@@ -103,11 +103,11 @@ Ref: policy 12.1
Tag: manpage-has-bad-whatis-entry
Severity: normal
Certainty: certain
-Info: Each manual page should start with a `NAME' section, which lists the
- name and a brief description of the page separated by '\-'. These sections
- are parsed by `mandb' and stored in a database for the use of `apropos' and
- `whatis', so they must be in a certain format. This manual page apparently
- uses the wrong format and cannot be parsed by `mandb'.
+Info: Each manual page should start with a "NAME" section, which lists the
+ name and a brief description of the page separated by "\-". These sections
+ are parsed by "mandb" and stored in a database for the use of "apropos" and
+ "whatis", so they must be in a certain format. This manual page apparently
+ uses the wrong format and cannot be parsed by "mandb".
Ref: lexgrog(1), groff_man(7), groff_mdoc(7)
Tag: manpage-has-useless-whatis-entry
@@ -236,20 +236,20 @@ Tag: hyphen-used-as-minus-sign
Severity: wishlist
Certainty: certain
Info: Manual page seems to contain a hyphen where a minus sign was intended.
- '-' chars are interpreted as hyphens (U+2010) by groff, not as minus signs
+ "-" chars are interpreted as hyphens (U+2010) by groff, not as minus signs
(U+002D). Since options to programs use minus signs (U+002D), this means for
example in UTF-8 locales that you cannot cut&paste options, nor search for
them easily.
.
- '-' must be escaped ('\-') to be interpreted as minus. If you really intend a
- hyphen, write it as '\(hy' to emphasise that fact. See groff(7) and
+ "-" must be escaped ("\-") to be interpreted as minus. If you really intend a
+ hyphen, write it as "\(hy" to emphasise that fact. See groff(7) and
especially groff_char(7) for details, and also the thread starting with
http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481.html
.
If you use some tool that converts your documentation to groff format, it
might be possible that this tool converts dashes of any kind to groff
hyphens, while the safe way of converting dashes is usually to convert them
- to '\-'.
+ to "\-".
.
Because this error can occur <em>very</em> often we show only the
first 10 occurrences for each man page and give the number of
diff --git a/checks/menus.desc b/checks/menus.desc
index d95c41e..434f429 100644
--- a/checks/menus.desc
+++ b/checks/menus.desc
@@ -17,7 +17,7 @@ Severity: important
Certainty: possible
Info: The maintainer script calls the <tt>update-menus</tt> command without
checking for existence first. (The <tt>menu</tt> package which provides the
- command is not marked as `essential' package.)
+ command is not marked as "essential" package.)
.
For example, use the following code in your maintainer script:
if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
@@ -27,7 +27,7 @@ Severity: important
Certainty: possible
Info: The maintainer script calls the <tt>wm-menu-config</tt> command without
checking for existence first. (The <tt>menu</tt> package which provides
- the command is not marked as `essential' package.)
+ the command is not marked as "essential" package.)
.
For example, use the following code in your maintainer script:
if [ -x /usr/sbin/wm-menu ]; then /usr/sbin/wm-menu-config; fi
@@ -37,7 +37,7 @@ Severity: important
Certainty: possible
Info: The maintainer script calls the <tt>install-docs</tt> command without
checking for existence first. (The <tt>doc-base</tt> package which provides
- the command is not marked as `essential' package.)
+ the command is not marked as "essential" package.)
.
For example, use the following code in your maintainer script:
if [ -x /usr/sbin/install-docs ]; then
diff --git a/checks/shared-libs.desc b/checks/shared-libs.desc
index 8217c97..ce56ff9 100644
--- a/checks/shared-libs.desc
+++ b/checks/shared-libs.desc
@@ -73,7 +73,7 @@ Ref: policy 8.1
Tag: dev-pkg-without-shlib-symlink
Severity: normal
Certainty: certain
-Info: A `-dev' package is supposed to install a `libsomething.so' symbolic
+Info: A "-dev" package is supposed to install a "libsomething.so" symbolic
link referencing the corresponding shared library. Notice how the link name
doesn't include the version number -- this is because such a link is used
by the linker when other programs are built against this shared library.
@@ -82,13 +82,13 @@ Ref: policy 8.4
Tag: non-dev-pkg-with-shlib-symlink
Severity: normal
Certainty: possible
-Info: Although this package is not a `-dev' package, it installs a
- `libsomething.so' symbolic link referencing the corresponding shared
+Info: Although this package is not a "-dev" package, it installs a
+ "libsomething.so" symbolic link referencing the corresponding shared
library. When the link doesn't include the version number, it is used by
the linker when other programs are built against this shared library.
.
Shared libraries are supposed to place such symbolic links in their
- respective `-dev' packages, so it is a bug to include it with the main
+ respective "-dev" packages, so it is a bug to include it with the main
library package.
.
However, if this is a small package which includes the runtime and the
@@ -211,7 +211,7 @@ Tag: postinst-must-call-ldconfig
Severity: serious
Certainty: certain
Info: The package installs shared libraries in a directory controlled by
- the dynamic library loader. Therefore, the package must call `ldconfig' in
+ the dynamic library loader. Therefore, the package must call "ldconfig" in
its postinst script.
Ref: policy 8.1.1
@@ -219,7 +219,7 @@ Tag: postrm-should-call-ldconfig
Severity: important
Certainty: certain
Info: The package installs shared libraries in a directory controlled by
- the dynamic library loader. Therefore, the package should call `ldconfig'
+ the dynamic library loader. Therefore, the package should call "ldconfig"
in its postrm script.
Ref: policy 8.1.1
diff --git a/collection/copyright-file.desc b/collection/copyright-file.desc
index 53edd99..7e6ae2a 100644
--- a/collection/copyright-file.desc
+++ b/collection/copyright-file.desc
@@ -1,6 +1,7 @@
Collector-Script: copyright-file
Author: Richard Braakman <dark@xs4all.nl>
-Info: This script copies the `copyright' file of a package into the lintian directory.
+Info: This script copies the "copyright" file of a package into the
+ lintian directory.
Type: binary
Unpack-Level: 2
Output: copyright
diff --git a/collection/debian-readme.desc b/collection/debian-readme.desc
index 6f0d766..bf92191 100644
--- a/collection/debian-readme.desc
+++ b/collection/debian-readme.desc
@@ -1,6 +1,6 @@
Collector-Script: debian-readme
Author: Richard Braakman <dark@xs4all.nl>
-Info: This script copies the `README.Debian' file of a package into the lintian directory.
+Info: This script copies the 'README.Debian' file of a package into the lintian directory.
Type: binary
Unpack-Level: 2
Output: README.Debian
diff --git a/collection/file-info.desc b/collection/file-info.desc
index 2e49543..0ac06a9 100644
--- a/collection/file-info.desc
+++ b/collection/file-info.desc
@@ -1,6 +1,6 @@
Collector-Script: file-info
Author: Richard Braakman <dark@xs4all.nl>
-Info: This script runs the `file' command over all files of a binary package.
+Info: This script runs the "file" command over all files of a binary package.
Type: binary, udeb
Unpack-Level: 2
Output: file-info
diff --git a/collection/init.d.desc b/collection/init.d.desc
index f75b6e4..1901cda 100644
--- a/collection/init.d.desc
+++ b/collection/init.d.desc
@@ -1,6 +1,7 @@
Collector-Script: init.d
Author: Richard Braakman <dark@xs4all.nl>
-Info: This script copies the `etc/init.d' directory into the lintian directory.
+Info: This script copies the "etc/init.d" directory into the lintian
+ directory.
Type: binary
Unpack-Level: 2
Output: init.d
diff --git a/collection/md5sums.desc b/collection/md5sums.desc
index b7db525..74f0fa8 100644
--- a/collection/md5sums.desc
+++ b/collection/md5sums.desc
@@ -1,6 +1,6 @@
Collector-Script: md5sums
Author: Richard Braakman <dark@xs4all.nl>
-Info: This script runs the `md5sums' over all files in a binary package.
+Info: This script runs the "md5sums" over all files in a binary package.
Type: binary, udeb
Unpack-Level: 2
Output: md5sums
diff --git a/collection/objdump-info.desc b/collection/objdump-info.desc
index 1c2204d..e25ef50 100644
--- a/collection/objdump-info.desc
+++ b/collection/objdump-info.desc
@@ -1,6 +1,7 @@
Collector-Script: objdump-info
Author: Christian Schwarz <schwarz@debian.org>
-Info: This script runs `objdump' over all binaries and object files of a binary package.
+Info: This script runs "objdump" over all binaries and object files of a
+ binary package.
Type: binary, udeb
Unpack-Level: 2
Output: objdump-info
diff --git a/collection/override-file.desc b/collection/override-file.desc
index 0f581ea..722a3be 100644
--- a/collection/override-file.desc
+++ b/collection/override-file.desc
@@ -1,6 +1,7 @@
Collector-Script: override-file
Author: Darren Benham <gecko@debian.org>
-Info: This script copies the `override' file of a package into the lintian directory.
+Info: This script copies the "override" file of a package into the lintian
+ directory.
Type: binary, udeb, source
Unpack-Level: 2
Output: override
diff --git a/debian/changelog b/debian/changelog
index a003fa1..21e4659 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,9 @@
lintian (2.1.7) UNRELEASED; urgency=low
+ * checks/*.desc:
+ + [RA] Replace `' "balanced" quotes with straight double-quotes. The
+ old style looks strange with modern fonts. Based on work by Raphael
+ Geissert.
* checks/control-file.desc:
+ [ADB] Fix a typo ("arne't"). Thanks, Raphael Geissert.
* checks/debhelper.desc:
@@ -13,6 +17,11 @@ lintian (2.1.7) UNRELEASED; urgency=low
+ [ADB] Add source-control-file to the list of information needed by
the script. Thanks, Raphael Geissert. (Closes: #512563)
+ * collection/*.desc:
+ + [RA] Replace `' "balanced" quotes with straight double-quotes. The
+ old style looks strange with modern fonts. Based on work by Raphael
+ Geissert.
+
* lib/Checker.pm:
+ [ADB] Remove some unused code.
* lib/Lintian/Collect/Source.pm:
diff --git a/private/TODO b/private/TODO
index 1566413..8a0cdde 100644
--- a/private/TODO
+++ b/private/TODO
@@ -24,7 +24,6 @@ goals not targetted
- go through all tags and make sure that any that should have Policy
references have them, and more generally that appropriate references are
present
-- remove old unbalance `' quotes from all tag descriptions
- rewrite the Lintian manual in something other than DebianDoc-SGML
- update the Lintian manual
+ document severity/certainty
--
Debian package checker
Reply to: