From 3f62ef00ed9faa726fe6f3b34159b1eac7eabacb Mon Sep 17 00:00:00 2001 From: Russ Allbery Date: Tue, 22 Jun 2010 10:07:18 -0700 Subject: [PATCH] Further revisions to the Format update 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. --- policy.sgml | 80 +++++++++++++++++++++++------------------------------ 1 file changed, 35 insertions(+), 45 deletions(-) diff --git a/policy.sgml b/policy.sgml index 74f94e8..57a2621 100644 --- a/policy.sgml +++ b/policy.sgml @@ -2600,14 +2600,20 @@ Package: libc6 Debian changes files -- .changes

- The .changes files are used by the Debian archive maintenance - software to process updates to packages. They contain one - paragraph which contains information from the + The .changes files are used by the Debian archive + maintenance software to process updates to packages. They + contain one paragraph which contains information from the debian/control file and other data about the source package gathered via debian/changelog and debian/rules.

+

+ .changes files have a format version that is + incremented whenever the documented fields or their meaning + change. This document describes format 1.8. +

+

The fields in this file are: @@ -2620,10 +2626,10 @@ Package: libc6 Version (mandatory) Distribution (mandatory) Urgency (recommended) - Maintainer (mandatory) The meaning of that field changed in version 1.7. - Changed-By Introduced in format 1.7. + Maintainer (mandatory) + Changed-By Description (mandatory) - Closes Introduced in format 1.6. + Closes Changes (mandatory) Checksums-Sha1 and Checksums-Sha256 (recommended) @@ -3264,25 +3270,30 @@ Package: libc6 Format

- In changes files, this field - specifies a format revision for the file. The syntax of the - format value is the same as that of a package version - number except that no epoch or Debian revision is allowed - - see . + In .changes + files, this field declares the format version of that file. + The syntax of the field value is the same as that of + a package version number except + that no epoch or Debian revision is allowed. The format + described in this document is 1.8. +

+ +

+ In Debian source + control files, this field declares the format of the + source package. The field value is used by programs acting on + a source package to interpret the list of files in the source + package and determine how to unpack it. The syntax of the + field value is a numeric major revision, a period, a numeric + minor revision, and then an optional subtype after whitespace, + which if specified is an alphanumeric word in parentheses. + The subtype is optional in the syntax but may be mandatory for + particular source format revisions. + The source formats currently supported by the Debian archive + software are 1.0, 3.0 (native), + and 3.0 (quilt). +

- -

- In Debian source control - files, this field specifies a format revision for the source package. - The syntax of the format value is the same as that of a package version - number, except that no epoch or Debian revision is allowed - and that it can optionally be followed by a parenthesis with a name - dpkg-source uses the major number and the content of the - parenthesis to decide which perl module to use to build or unpack - the source package. For instance, Dpkg::Source::Package::V1 for format - 1.0 and Dpkg::Source::Package::V3::quilt for format 3.0 (quilt) - . -

@@ -3542,27 +3553,6 @@ Checksums-Sha256: must match the list of files in the Files field.

- - - Checksums-Sha1 - -

- This field is similar to the Files - field, except that it uses the Sha1 algorithm instead of MD5 - for the checksums. -

-
- - - Checksums-Sha256 - -

- This field is similar to the Files - field, except that it uses the Sha1 algorithm instead of MD5 - for the checksums. -

-
- -- 2.39.5