Bug#532945: developers-reference: use of +nmu1 should be recommended only for native packages
In "5.11.2. NMUs and debian/changelog", it is suggested to version NMU
by appending "+nmuN".
It seems however that many people prefer to only use "+nmuN" on native
packages; see discussion at:
I understand that +nmu1 is not a bad idea for debian native packages,
where you wouldn't be able to tell if a passage from 1.0 to 1.0.1 is a
new upstream verion or a NMU. However, it is unnecessary, and indeed it
look ugly, on non-native packages.
The simplest change to the Developer's Reference to document this could
be adding a paragraph like the following before the paragraph "A special
For non-native packages, many developers prefer to append ".N" instead
of "+nmuN". For example, NMUs of a package with version "1.0-2" would
have versions "1.0-2.1", "1.0-2.2" and so on.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
developers-reference depends on no packages.
Versions of packages developers-reference recommends:
ii debian-policy 22.214.171.124 Debian Policy Manual and related d
Versions of packages developers-reference suggests:
ii doc-base 0.9.2 utilities to manage online documen
-- no debconf information