From 224cfaf1fa22890537e502078455e6703d2899a2 Mon Sep 17 00:00:00 2001
From: Russ Allbery
Date: Sat, 12 Jun 2010 13:26:28 -0700
Subject: [PATCH] Document Checksums-Sha1 and Checksums-Sha256
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.
---
policy.sgml | 59 +++++++++++++++++++++++++++++++++++++++++++++++------
1 file changed, 53 insertions(+), 6 deletions(-)
diff --git a/policy.sgml b/policy.sgml
index 720150d..23a8c90 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -2488,8 +2488,6 @@ Package: libc6
The syntax and semantics of the fields are described below.
-
-
These fields are used by dpkg-gencontrol to
generate control files for binary packages (see below), by
@@ -2563,15 +2561,17 @@ Package: libc6
- Format (mandatory)
- Source (mandatory)
+ - Binary
+ - Architecture
- Version (mandatory)
- Maintainer (mandatory)
- Uploaders
- - Binary
- - Architecture
- - Build-Depends et al
+ - Homepage
- Standards-Version (recommended)
+ - Build-Depends et al
+ - Checksums-Sha1
+ and Checksums-Sha256 (recommended)
- Files (mandatory)
- - Homepage
@@ -2615,6 +2615,8 @@ Package: libc6
- Description (mandatory)
- Closes
- Changes (mandatory)
+ - Checksums-Sha1
+ and Checksums-Sha256 (recommended)
- Files (mandatory)
@@ -3472,6 +3474,51 @@ Files:
+
+ Checksums-Sha1
+ and Checksums-Sha256
+
+
+ These fields contain a list of files with a checksum and size
+ for each one. Both Checksums-Sha1
+ and Checksums-Sha256 have the same syntax and differ
+ only in the checksum algorithm used: SHA-1
+ for Checksums-Sha1 and SHA-256
+ for Checksums-Sha256.
+
+
+
+ Checksums-Sha1 and Checksums-Sha256 are
+ multiline field. The first line of the field value (the part
+ on the same line as Checksums-Sha1:
+ or Checksums-Sha256:) is always empty. The content
+ of the field is expressed as continuation lines, one line per
+ file. Each line consists of the checksum, a space, the file
+ size, a space, and the file name. For example (from
+ a .changes file):
+
+Checksums-Sha1:
+ 1f418afaa01464e63cc1ee8a66a05f0848bd155c 1276 example_1.0-1.dsc
+ a0ed1456fad61116f868b1855530dbe948e20f06 171602 example_1.0.orig.tar.gz
+ 5e86ecf0671e113b63388dac81dd8d00e00ef298 6137 example_1.0-1.debian.tar.gz
+ 71a0ff7da0faaf608481195f9cf30974b142c183 548402 example_1.0-1_i386.deb
+Checksums-Sha256:
+ ac9d57254f7e835bed299926fd51bf6f534597cc3fcc52db01c4bffedae81272 1276 example_1.0-1.dsc
+ 0d123be7f51e61c4bf15e5c492b484054be7e90f3081608a5517007bfb1fd128 171602 example_1.0.orig.tar.gz
+ f54ae966a5f580571ae7d9ef5e1df0bd42d63e27cb505b27957351a495bc6288 6137 example_1.0-1.debian.tar.gz
+ 3bec05c03974fdecd11d020fc2e8250de8404867a8a2ce865160c250eb723664 548402 example_1.0-1_i386.deb
+
+
+
+
+ In the .dsc file, these fields should list all
+ files that make up the source package. In
+ the .changes file, these fields should list all
+ files being uploaded. The list of files in these fields
+ must match the list of files in the Files field.
+
+
+
--
2.39.5