From 99231830ee9bde735ba2a7566b15ee135954b3f2 Mon Sep 17 00:00:00 2001
From: aph <aph@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Mon, 16 Jun 2003 06:47:46 +0000
Subject: [PATCH] Sec "Managing sponsored packages": remove unnecessary
 'debsign' cmd; closes: #192417

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2326 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 developers-reference.sgml | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 53010fe..a140f58 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.201 $">
+  <!entity cvs-rev "$Revision: 1.202 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -4042,9 +4042,8 @@ that need to be made.  It often takes several rounds of back-and-forth
 email before the package is in acceptable shape.  Being a sponsor
 means being a mentor.
 	<p>
-Once the package meets Debian standards, build the package with
-<example>dpkg-buildpackage -us -uc</example> and sign it
-with <example>debsign -m"<var>FULLNAME</var> <var>email-addr</var>" <var>changes-file</var></example>
+Once the package meets Debian standards, build and sign it with                           
+<example>dpkg-buildpackage -k<var>KEY-ID</var></example>                                  
 before uploading it to the incoming directory.
 	<p>
 The Maintainer field of the <file>control</file> file and the
-- 
2.30.2