Be clear which control files consist of a single paragraph and use
consistent terminology.  Be more consistent about <file> markup.  Use
an SGML entity for the .changes file version to avoid repeating it.

Drop historical information about the version changes in .changes
files.  It doesn't seem useful at this point.  Specify the format
of Format for source packages separately since referring to the
version format with exceptions and additions is more confusing and
it's not really a version in the same sense.  Add the full list of
supported source package formats in a footnote.  Add a bit more
explanation for how the source package format is used.

Charles Plessy authored May 29, 2010 and Russ Allbery committed Jun 22, 2010

The Format field has a different meaning for Debian source control files and
Debian changes files. This patch :

 - documents the use and syntax of the Format field for these two types
   of control files.

 - Specifies the format 1.8 of Debian changes files, adds descriptions for
   the Checksums-Sha1 and Checksums-Sha256 files, and provides some history
   for the Closes, Changed-By and Maintainer fields.

Document the SETTITLE command in the debconf policy.  Inclusion of this
command should not pose any problems as it has been supported since 2003
(debconf version 1.3.22).

Patch from Frans Pop <elendil@planet.nl>.

* Avoid "Debianised" or "Debianized" in favor of just "Debian" or
  "Debian package" as appropriate.  Patch from Ben Finney.
  (Closes: #586163)

Recommend Breaks over Conflicts for most purposes.  List the places
Breaks should be used and the places Conflicts should be used.  Add
Breaks to the example in Replaces, and add a footnote explaining
why Breaks is normally required along with Replaces when files are
moving between packages.  Add additional discussion of conflicting
with a virtual package.

Conflicts:
	debian/changelog

Terminate an HTML entity and be clearer about the cross-reference
to the Maintainer field in the Uploaders field.

The syntax of Maintainer is a must, not a should.  The comma
separator in Uploaders is a must, not a should.  Now allow people
to use multi-line Uploaders fields freely.  Be explicit that the
Changed-By field has the same syntax as Maintainer and be clearer
about what identity goes here.

Add documentation for the Checksums-Sha1 and Checksums-Sha256 fields
and mark them as recommended for both source and changes files.  Also
reorder the field listing in source and changes files to match the
order in which dpkg-dev writes the fields.

Say instead that installing the library development package must
result in installation of all the required files, which allows for
further splits with appropriate Depends.

* Clarify the wording around which build dependencies must be satisfied
  for different debian/rules targets and add a footnote to the
  description of the build-arch and build-indep targets explaining why
  this split does not currently work as desired.  (Closes: #328951)

* Explicitly state that packages may remove unmodified, obsolete
  configuration files during  upgrade.  (Closes: #470633)

* Add an example for Replaces when a package is split.  Thanks, Uwe
  Kleine-König.  (Closes: #572253)

Bug#555978.

Also look for LPPL version 1.3a and for any version of the license.
Be case-insensitive when looking for the Artistic 2.0 license.