Bug#672198: [developers-reference] NMU clarification for section 5.11.1

[Chris Knadle <Chris.Knadle@coredump.us>]

Package: developers-reference
Version: 3.4.7
Severity: wishlist
Tags: patch

In a long email thread on [debian-devel] concerning a package which has a 
maintainer that is temporarily MIA due to being time overloaded, the 
discussion came to an idea for using NMUs in order to bring the package up to 
date to upload a new upstream version of the software.  I was directed to read 
section 5.11 of the Developer's Reference, but it doesn't seem to clearly 
state that this is allowed.  Stefano Zacchiroli responded with a post [1] 
explaining NMUs from his point of view which I find is a bit more clear in 
this area.

Attached is a minimal patch against commit:

   r9201 | taffit | 2012-04-25 09:25:10 -0400 (Wed, 25 Apr 2012)

in the repository for the Developer's Reference.  Diffstat:

 pkgs.dbk |   11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)



[1] http://lists.debian.org/debian-devel/2012/04/msg00486.html

  -- Chris

--
Chris Knadle
Chris.Knadle@coredump.us

diff --git a/pkgs.dbk b/pkgs.dbk
index af8bcf0..6959ac8 100644
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -1923,8 +1923,15 @@ Before doing an NMU, consider the following questions:
 <itemizedlist>
 <listitem>
 <para>
-Does your NMU really fix bugs? Fixing cosmetic issues or changing the
-packaging style in NMUs is discouraged.
+Will the NMU help the maintainer?
+</para>
+</listitem>
+<listitem>
+<para>
+Does your NMU really fix bugs? ("Bugs" includes wishlist bugs for packaging
+a new upstream version, but care should be taken to minimize the impact to
+the maintianer.) Fixing cosmetic issues or changing the packaging style
+(dh, cdbs, etc) in NMUs is discouraged.
 </para>
 </listitem>
 <listitem>