-#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1992
-msgid ""
-"The version must be the version of the last maintainer upload, plus <literal>"
-"+nmu<replaceable>X</replaceable></literal>, where <replaceable>X</"
-"replaceable> is a counter starting at <literal>1</literal>. If the last "
-"upload was also an NMU, the counter should be increased. For example, if "
-"the current version is <literal>1.5-1</literal>, then an NMU would get "
-"version <literal>1.5-1+nmu1</literal>. If the current version is "
-"<literal>1.5+nmu3</literal> (a native package which has already been NMUed), "
-"the NMU would get version <literal>1.5+nmu4</literal>. If a new upstream "
-"version is packaged in the NMU, the debian revision is set to <literal>0</"
-"literal>, for example <literal>1.6-0+nmu1</literal>."
-msgstr ""
-
-#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2005
-msgid ""
-"A special versioning scheme is needed to avoid disrupting the maintainer's "
-"work, since using an integer for the Debian revision will potentially "
-"conflict with a maintainer upload already in preparation at the time of an "
-"NMU, or even one sitting in the ftp NEW queue. It also has the benefit of "
-"making it visually clear that a package in the archive was not made by the "
-"official maintainer."
-msgstr ""
-
-#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2015
-msgid ""
-"If you upload a package to testing or stable, you sometimes need to \"fork\" "
-"the version number tree. This is the case for security uploads, for "
-"example. For this, a version of the form <literal>+deb<replaceable>XY</"
-"replaceable>u<replaceable>Z</replaceable></literal> should be used, where "
-"<replaceable>X</replaceable> and <replaceable>Y</replaceable> are the major "
-"and minor release numbers, and <replaceable>Z</replaceable> is a counter "
-"starting at <literal>1</literal>. When the release number is not yet known "
-"(often the case for <literal>testing</literal>, at the beginning of release "
-"cycles), the lowest release number higher than the last stable release "
-"number must be used. For example, while Etch (Debian 4.0) is stable, a "
-"security NMU to stable for a package at version <literal>1.5-3</literal> "
-"would have version <literal>1.5-3+deb40u1</literal>, whereas a security NMU "
-"to Lenny would get version <literal>1.5-3+deb50u1</literal>. After the "
-"release of Lenny, security uploads to the <literal>testing</literal> "
-"distribution will be versioned <literal>+deb51uZ</literal>, until it is "
-"known whether that release will be Debian 5.1 or Debian 6.0 (if that becomes "
-"the case, uploads will be versioned as <literal>+deb60uZ</literal>."