From eb4fa58d9eea5c7b19d057a7cafe5d6ba73ff258 Mon Sep 17 00:00:00 2001
From: aph <aph@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Sun, 31 Mar 2002 22:08:39 +0000
Subject: [PATCH] from Martin Michlmayr: changes in upload situation, not
 possible to remove from Incoming anymore, talk about dput a bit; closes:
 #135559

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 6917d4f..45aaac6 100644
--- 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.81 $">
+  <!entity cvs-rev "$Revision: 1.82 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -1108,7 +1108,13 @@ To upload a package, you need a personal account on
 official maintainer. If you use <prgn>scp</prgn> or <prgn>rsync</prgn>
 to transfer the files, place them into <tt>&us-upload-dir;</tt>;
 if you use anonymous FTP to upload, place them into
-<ftppath>/pub/UploadQueue/</ftppath>.
+<ftppath>/pub/UploadQueue/</ftppath>.  Please note that you should transfer
+the changes file last.  Otherwise, your upload may be rejected because the
+archive maintenance software will parse the changes file and see that not
+all files have been uploaded.  If you don't want to bother with transfering
+the changes file last, you can simply copy your files to a temporary
+directory on <tt>ftp-master</tt> and then move them to
+<tt>&us-upload-dir;</tt>.
           <p>
 <em>Note:</em> Do not upload to <tt>ftp-master</tt> packages
 containing software that is export-controlled by the United States
@@ -1121,12 +1127,14 @@ to <tt>non-us</tt> (see <ref id="upload-non-us">).  If you are not
 sure whether U.S. export controls apply to your package, post a
 message to &email-debian-devel; and ask.
 	  <p>
-You may also find the Debian package <package>dupload</package> useful
-when uploading packages.  This handy program is distributed with
+You may also find the Debian packages <package>dupload</package> or
+<package>dput</package> useful
+when uploading packages.  These handy program are distributed with
 defaults for uploading via <prgn>ftp</prgn> to <tt>ftp-master</tt>,
 <tt>chiark</tt>, and <tt>erlangen</tt>.  It can also be configured to
 use <prgn>ssh</prgn> or <prgn>rsync</prgn>.  See <manref name="dupload"
-section="1"> and <manref name="dupload" section="5"> for more information.
+section="1">, <manref name="dupload" section="5"> and <manref name="dput"
+section="1"> for more information.
 	  <p>
 After uploading your package, you can check how the archive maintenance
 software will process it by running <prgn>dinstall</prgn> on your changes
@@ -1855,10 +1863,14 @@ package.  When invoked as <tt>apt-cache showpkg
 
 	<sect1>Removing packages from <tt>Incoming</tt>
 	  <p>
-If you decide to remove a package from <tt>Incoming</tt>, it is nice
-but not required to send a notification of that to the appropriate
-announce list (either &email-debian-changes; or
-&email-debian-devel-changes;).
+In the past, it was possible to remove packages from <tt>incoming</tt>.
+With the introduction of the New Incoming system this is no longer
+possible.  Instead, you have to upload a new revision of your package with
+a higher version as the package you want to replace.  Both versions will be
+installed in the archive but only the higher version will actually be
+available in <em>unstable</em> since the previous version will immediately
+be replaced by the higher.  However, if you do proper testing of your
+packages, the need to replace a package should not occur too often anyway.
 
       <sect>Replacing or renaming packages
 	<p>
-- 
2.30.2