Include full URL to the README of the upload queue

[developers-reference.git] / pkgs.dbk

diff --git a/pkgs.dbk b/pkgs.dbk
index 160fa5b11a08fdd1a80ebd4e05bad81eb3e3c6f4..c477164027c774f29841cc72affc81aebc76fc12 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -400,7 +400,8 @@ linkend="dput"/> useful when uploading packages.  These handy programs help
 automate the process of uploading packages into Debian.
 </para>
 <para>
-For removing packages, please see the README file in that ftp directory, and
+For removing packages, please see
+<ulink url="ftp://&ftp-upload-host;&upload-queue;/README"/> and
 the Debian package <xref linkend="dcut"/> .
 </para>
 </section>
@@ -458,8 +459,6 @@ down.  Work is underway to resurrect them.
 <para>
 The queues on master.debian.org, samosa.debian.org, master.debian.or.jp, and
 ftp.chiark.greenend.org.uk are down permanently, and will not be resurrected.
-The queue in Japan will be replaced with a new queue on hp.debian.or.jp some
-day.
 </para>
 </section>
 
@@ -517,10 +516,13 @@ file</literal>.
 <para>
 To alter the actual section that a package is put in, you need to first make
 sure that the <filename>debian/control</filename> file in your package is
-accurate.  Next, send an email &email-override; or submit a
+accurate.  Next, submit a
 bug against <systemitem role="package">ftp.debian.org</systemitem> requesting
 that the section or priority for your package be changed from the old section
-or priority to the new one.  Be sure to explain your reasoning.
+or priority to the new one. Use a Subject like
+<literal>override: PACKAGE1:section/priority, [...],
+  PACKAGEX:section/priority</literal>, and include the justification for the
+change in the body of the bug report.
 </para>
 <para>
 For more information about <literal>override files</literal>, see
@@ -1344,6 +1346,10 @@ should either be reassigned to another package in the case where the actual
 code has evolved into another package (e.g.  <literal>libfoo12</literal> was
 removed because <literal>libfoo13</literal> supersedes it) or closed if the
 software is simply no longer part of Debian.
+When closing the bugs,
+to avoid marking the bugs as fixed in versions of the packages
+in previous Debian releases, they should be marked as fixed
+in the version <literal>&lt;most-recent-version-ever-in-Debian&gt;+rm</literal>.
 </para>
 <section id="s5.9.2.1">
 <title>Removing packages from <filename>Incoming</filename></title>
@@ -1787,17 +1793,15 @@ flavor of Debian built with <command>gcc</command> bounds checking).  It will
 also enable Debian to recompile entire distributions quickly.
 </para>
 <para>
-The buildds admins of each arch can be contacted at the mail address
-<literal><replaceable>arch</replaceable>@buildd.debian.org</literal>.
+The wanna-build team, in charge of the buildds,
+can be reached at <literal>debian-wb-team@lists.debian.org</literal>.
+To determine who (wanna-build team, release team) and how (mail, BTS)
+to contact, refer to <ulink url="&url-wb-team;"></ulink>.
 </para>
 
 <para>
-Since the Release team also has access to wanna-build,
-it has become common practice to ask them to perform actions such as
-the recompilation of packages (binNMUs, see <xref linkend="binary-only-nmu"/>)
-or the retry of failed builds (give-backs).
-The format to use when requesting such actions is described at
-<ulink url="&url-release-wb;"/>.
+When requesting binNMUs or give-backs (retries after a failed build),
+please use the format described at <ulink url="&url-release-wb;"/>.
 </para>
 
 </section>