From bda25f439fa8e7992b2a6b3f1dfe286fdedb984c Mon Sep 17 00:00:00 2001 From: aph Date: Sun, 12 Sep 1999 22:13:33 +0000 Subject: [PATCH] add stuff for dinstall bug closing; note alternate names for DSA git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@842 313b444b-1b9f-4f58-a734-7bb04f332e8d --- debian/changelog | 8 +++++-- developers-reference.sgml | 49 +++++++++++++++++++++++++++++---------- 2 files changed, 43 insertions(+), 14 deletions(-) diff --git a/debian/changelog b/debian/changelog index 4bedc96..dc477b6 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,14 +2,18 @@ developers-reference (2.7.1) unstable; urgency=low * Sec. "Registering as a Debian developer": we are transitioning away from non-free PGP -- remove allusions to non-free software such as - PGPv2 or v5 insofar as possible; recommend use of DSA keys rather than + PGPv2 or v5 insofar as possible; recommend use of DSS keys rather than RSA * Sec. "Maintaining Your Public Key": remove PGP-centric stuff + * Sec. "When bugs are closed by new uploads": describe how to close bugs + via a magic changelog entry (closes: Bug#43690) + * Sec. "Generating the changes file": refer to Sec. "When bugs are + closed by new uploads" for closing bugs via a changelog entry * developers-reference.sgml: re-enable RCS variables in CVS sources * debian/control,rules: dynamically generate the TOC in the package description from developers-reference.sgml - -- Adam Di Carlo Sat, 11 Sep 1999 21:22:10 -0400 + -- developers-reference (2.7.0) unstable; urgency=low diff --git a/developers-reference.sgml b/developers-reference.sgml index 987c7d3..40e1987 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -5,7 +5,7 @@ %commondata; - + @@ -191,11 +191,12 @@ OpenPGP is a open standard based on .

The recommended public key algorithm for use in Debian development -work is the DSA (Digital Signature Standard). Other key types may be -used however. Your key length must be at least 1024 bits; there is no -reason to use a smaller key, and doing so would be much less secure. -Your key must be signed with at least your own user ID; this prevents -user ID tampering. gpg does this automatically. +work is the DSA (sometimes call ``DSS'' or ``DH/ElGamal''). Other key +types may be used however. Your key length must be at least 1024 +bits; there is no reason to use a smaller key, and doing so would be +much less secure. Your key must be signed with at least your own user +ID; this prevents user ID tampering. gpg does this +automatically.

Also remember that one of the names on your key must match the email address you list as the official maintainer for your packages. For @@ -804,9 +805,11 @@ The changes file is a control file with the following fields:

All of these fields are mandatory for a Debian upload. See the list of control fields in the for the contents of these fields. Only the -Distribution field is discussed here, since it relates to the -archive maintenance policies. +Packaging Manual"> for the contents of these fields. You can close +bugs automatically using the Description field, see . Only the Distribution field is +discussed in this section, since it relates to the archive maintenance +policies. Picking a distribution @@ -1712,7 +1715,7 @@ You should never close bugs via the bug server `close' command sent to &email-bts-control;. If you do so, the original submitter will not receive any feedback on why the bug was closed. - When bugs are closed by new uploads + When bugs are closed by new uploads

If you fix a bug in your packages, it is your responsibility as the package maintainer to close the bug when it has been fixed. However, @@ -1721,8 +1724,30 @@ been accepted into the Debian archive. Therefore, once you get notification that your updated package has been installed into the archive, you can and should close the bug in the BTS.

-Again, see the BTS documentation for details on how to do this. -Often, it is sufficient to mail the .changes file to +If you are using a new version of dpkg-dev and you +do your changelog entry properly, dinstall will close the +bugs automatically. All you have to do is follow a certain syntax +in your debian/changelog file: + +acme-cannon (3.1415) unstable; urgency=low + + * Frobbed with options (closes: Bug#98339) + * Added safety to prevent operator dismemberment, closes: bug #98765, + bug #98713, #98714. + * Added manpage. closes: #98725. + + +Technically speaking, the following Perl regular expression is what is +used: + + /closes:\s*(bug)?\#\d+(,\s*(bug)?\#\d+)*/gi + + +The author prefers the (closes: Bug#XXX) syntax, +since it stands out from the rest of the changelog entries. +

+If you want to close bugs the old fashioned, manual way, it is usually +sufficient to mail the .changes file to XXX-done@bugs.debian.org, where XXX is your bug number. -- 2.30.2