From 8e31cd6cf729ec89a96f9c35c74e579893730123 Mon Sep 17 00:00:00 2001 From: Manoj Srivastava Date: Thu, 16 Jun 2005 05:11:35 +0000 Subject: [PATCH] Finished up chapter 5 changes Author: jdg Date: 2001/04/19 09:22:17 Finished up chapter 5 changes git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-99 --- policy.sgml | 93 +++++++++++++++++++++++++++++++++++------------------ 1 file changed, 62 insertions(+), 31 deletions(-) diff --git a/policy.sgml b/policy.sgml index c8537a4..1f622ef 100644 --- a/policy.sgml +++ b/policy.sgml @@ -2164,8 +2164,9 @@ Though there is nothing stopping an author who is also the Debian maintainer from using it for all their changes, it will have to be renamed if the Debian and - upstream maintainers become different - people. + upstream maintainers become different people. In such a + case, however, it might be better to maintain the + package as a non-native package.

.

@@ -2179,13 +2180,13 @@

That format is a series of entries like this: - package (version) distribution(s); urgency=urgency +package (version) distribution(s); urgency=urgency - * change details - more change details - * even more change details + * change details + more change details + * even more change details - -- maintainer name and email address date + -- maintainer name and email address date

@@ -2210,6 +2211,16 @@ dpkg changelog format (though there is currently only one useful keyword, urgency). + +

+ Usual urgency values are low, medium, + high and critical. They have an + effect on how quickly a package will be considered for + inclusion into the testing distribution, and + give an indication of the importance of any fixes + included in this upload. +

+

@@ -2222,13 +2233,33 @@

- The maintainer name and email address need not - necessarily be those of the usual package maintainer. - They should be the details of the person doing - this version. The information here will be - copied to the .changes file, and then later used - to send an acknowledgement when the upload has been - installed. + If this upload resolves bugs recorded in the Bug Tracking + System (BTS), they may be automatically closed on the + inclusion of this package into the Debian archive by + including the string: closes: Bug#nnnnn + in the change details. + +

+ To be precise, the string should match the following + Perl regular expression: + +/closes:\s*(?:bug)?\#\s?\d+(?:,\s*(?:bug)?\#\s?\d+)*/i + + Then all of the bug numbers listed will be closed by the + archive maintenance script (katie), or in + the case of an NMU, marked as fixed. +

+ +

+ +

+ The maintainer name and email address used in the changelog + should be the details of the person uploading this + version. They are not necessarily those of the + usual package maintainer. The information here will be + copied to the Changed-By field in the + .changes file, and then later used to send an + acknowledgement when the upload has been installed.

@@ -2240,7 +2271,7 @@

; it should include the time zone specified numerically, with the time zone name or abbreviation - optionally present as a comment. + optionally present as a comment in parentheses.

@@ -2271,21 +2302,22 @@

When dpkg-gencontrol, dpkg-genchanges and dpkg-source - generate control files they do variable substitutions on - their output just before writing it. Variable + generate control files they perform variable substitutions + on their output just before writing it. Variable substitutions have the form ${variable-name}. The optional file - debian/substvars contains variable substitutions - to be used; variables can also be set directly from + debian/substvars contains variable substitutions to + be used; variables can also be set directly from debian/rules using the -V option to the - source packaging commands, and certain predefined - variables are available. + source packaging commands, and certain predefined variables + are also available.

- The is usually generated and modified dynamically by - debian/rules targets; in this case it must be - removed by the clean target. + The debian/substvars file is usually generated and + modified dynamically by debian/rules targets; in + this case it must be removed by the clean + target.

@@ -2324,11 +2356,12 @@

- dpkg-gencontrol adds an entry to this file - for the .deb file that will be created by - dpkg-deb from the control file that it - generates, so for most packages all that needs to be done - with this file is to delete it in clean. + When dpkg-gencontrol is run for a binary + package, it adds an entry to debian/files for the + .deb file that will be created when dpkg-deb + --build is run for that binary package. So for most + packages all that needs to be done with this file is to + delete it in the clean target.

@@ -2351,8 +2384,6 @@ packages, but only when extracting them.

- -

Hard links may be permitted at some point in the future, but would require a fair amount of -- 2.39.2