dpkg-buildpackage -m<addr> flag was changed for -e<addr> when NMU'ing;

[developers-reference.git] / developers-reference.sgml

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 535c3f694b517f2a69d8bd63c4cc50167cfa80f2..a3d4b80ba46acd30412e4a82e513d39ddee88495 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -5,7 +5,7 @@
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.54 $">
+  <!entity cvs-rev "$Revision: 1.56 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -1542,7 +1542,7 @@ of things you should check or be aware of.
            <item>
 Don't set architecture to a value other than ``all'' or ``any'' unless
 you really mean it.  In too many cases, maintainers don't follow the
-instructions in the <url id="&url-debian-policy;;" name="Debian Policy
+instructions in the <url id="&url-debian-policy;" name="Debian Policy
 Manual">.  Setting your architecture to ``i386'' is usually incorrect.
            <item>
 Make sure your source package is correct.  Do <tt>dpkg-source -x
@@ -1600,7 +1600,7 @@ NMU of the source package ``foo_1.3-1'' would be numbered
 ``foo_1.3-1.0.1''.
        <p>
 The way to invoke <prgn>dpkg-buildpackage</prgn> is as
-<tt>dpkg-buildpackage -B -m<var>porter-email</var></tt>.  Of course,
+<tt>dpkg-buildpackage -B -e<var>porter-email</var></tt>.  Of course,
 set <var>porter-email</var> to your email address.  This will do a
 binary-only build of only the architecture-dependant portions of the
 package, using the `binary-arch' target in <file>debian/rules</file>.