From 1deab7628f8e47eb983d407f53b39981050a6424 Mon Sep 17 00:00:00 2001
From: aba <aba@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Sat, 11 Nov 2006 19:45:25 +0000
Subject: [PATCH] more on changelogs / bug closing

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@3946 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 debian/changelog          |  2 ++
 developers-reference.sgml | 15 +++++++++++----
 2 files changed, 13 insertions(+), 4 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index ee29fa7..7523a76 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -15,6 +15,8 @@ developers-reference (3.3.8) unstable; urgency=low
     Closes: #361311
   * Packages in testing disappear if they're removed from unstable.
     Thanks, Frank Küster, Al Stone. Closes: #365993
+  * Document only the most recent changelog entry is used. Thanks
+    to Kevin Glynn to the suggestion. Closes: #374738
 
  -- Andreas Barth <aba@not.so.argh.org>  Sat, 11 Nov 2006 10:55:44 -0700
 
diff --git a/developers-reference.sgml b/developers-reference.sgml
index b44d8da..5834120 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -7,7 +7,7 @@
   <!ENTITY % dynamicdata  SYSTEM "dynamic.ent" > %dynamicdata;
 
   <!-- CVS revision of this document -->
-  <!ENTITY cvs-rev "$Revision: 1.299 $">
+  <!ENTITY cvs-rev "$Revision: 1.300 $">
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
@@ -2156,6 +2156,7 @@ you should not close a bug until the package which fixes the bug has
 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.
+Also, the bug should be closed with the correct version.
 	<p>
 However, it's possible to avoid having to manually close bugs after the
 upload &mdash; just list the fixed bugs in your <file>debian/changelog</file>
@@ -2180,6 +2181,11 @@ how bug closing changelogs are identified:
 We prefer the <tt>closes: #<var>XXX</var></tt> syntax, as it is the
 most concise entry and the easiest to integrate with the text of the
 <file>changelog</file>.
+Unless specified different by the <var>-v</var>-switch to
+<prgn>dpkg-buildpackage</prgn>, only the bugs closed in the
+most recent changelog entry are closed (basically, exactly
+the bugs mentioned in the changelog-part
+in the <file>.changes</file> file are closed).
 	<p>
 Historically, uploads identified as
 <qref id="nmu">Non-maintainer upload (NMU)</qref>
@@ -2193,9 +2199,10 @@ wrongly closed bugs, send an <tt>reopen <var>XXX</var></tt> command to
 the bug tracking system's control address, &email-bts-control;.  To
 close any remaining bugs that were fixed by your upload, email the
 <file>.changes</file> file to <email>XXX-done@&bugs-host;</email>,
-where <var>XXX</var> is your bug number, and write "Version: XXX"
-in the first line of the body of the email to mark the first version
-where this bug has been closed.
+where <var>XXX</var> is your bug number, and
+put "Version: XXX" and an empty line as the first two lines
+of the body of the email 
+to mark the first version where this bug has been closed.
 	<p>
 Bear in mind that it is not obligatory to close bugs using the
 changelog as described above.  If you simply want to close bugs that
-- 
2.30.2