Package: www.debian.org
Severity: wishlist
Tags: patch

It seems reasonable to expect that wanna-build-states.wml should mention the
manual state transitions available by mailing the debian-wb-team (give-back
and dep-wait). A proposed patch follows (please check its accuracy with the
wb-team, cc'd).

I've also filed Bug #555961 on release.debian.org proposing clarifications in
<http://release.debian.org/wanna-build.txt>.

For the purposes of current/future website relicensing efforts: I give
permission for the text provided here to be copied and distributed with or
without modification in any medium. There is no warranty.

Thanks,
    Simon

Index: wanna-build-states.wml
===================================================================
RCS file: /cvsroot/webwml/webwml/english/devel/buildd/wanna-build-states.wml,v
retrieving revision 1.20
diff -u -r1.20 wanna-build-states.wml
--- wanna-build-states.wml      2 Sep 2009 07:35:20 -0000       1.20
+++ wanna-build-states.wml      12 Nov 2009 22:36:10 -0000
@@ -62,7 +62,10 @@
        theoretically also explicitly request a different section ordering,
        but that is not usually done.<br />
        There could be other situations where the queue order seems to
-       be ignored; but note that they are all exceptions.
+       be ignored; but note that they are all exceptions.<br />
+       The <code>gb</code> ("give-back") wanna-build command can be used
+       by the wanna-build team to move a failed package back into the
+       <em>needs-build</em> state.
       </dd>
       <dt><a name="building">building</a></dt>
       <dd>A package is marked <em>building</em> from the moment an
@@ -119,7 +122,15 @@
        Build-Depends, and should he or she add it when it is noticed that
        <tt>baz</tt> is <em>dep-wait</em>ing on a non-existing <tt>foo</tt> for
        <tt>m68k</tt>, then the <em>dep-wait</em> state for <tt>m68k</tt> will
-       have to be manually lifted by the <tt>m68k</tt> porters.
+       have to be manually lifted by the <tt>m68k</tt> porters.<br />
+       It is also possible to request that a package in some other state is
+       placed in the <em>dep-wait</em> state, by asking the wanna-build
+       team to apply the <code>dw</code> wanna-build command; for instance, a
+       package that failed to build on the first attempt due to toolchain
+       bugs can be set to <em>dep-wait</em> on toolchain packages that fix
+       those bugs, or a package that should be rebuilt against an updated
+       library can be set to <em>dep-wait</em> on that library (this is
+       useful in conjunction with binary NMUs).
       </dd>
       <dt><a name="bd-uninstallable">BD-Uninstallable</a></dt>
       <dd>During debconf9, <a
@@ -159,7 +170,11 @@
        hardly ever the right thing to do, the option is available to
        the autobuilder admin.<br />
        Note that a package will <strong>never</strong> be marked
-       <em>failed</em> without human intervention.
+       <em>failed</em> without human intervention.<br />
+       It is sometimes useful to ask the wanna-build team to move failed
+       packages into the <em>needs-build</em> or <em>dep-wait</em> state; to
+       do so, follow <a href="http://release.debian.org/wanna-build.txt";>the
+       instructions provided by the release team</a>.
       </dd>
       <dt><a name="not-for-us">not-for-us</a></dt>
       <dd>Certain specific packages are architecture-specific; for

Attachment: signature.asc
Description: Digital signature

Reply via email to