Bug#555967: [patch] describe gb, dw commands in wanna-build-states.wml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Simon,
Thanks for your patch and sorry for the late answer,
Le 12/11/2009 18:39, Simon McVittie a écrit :
> 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).
Kept, and added dle for approval of proper English which I can't judge.
Just to be sure, (since more than a year passed), is the patch still up
to date? Does it need some rewording?
Thanks in advance.
Regards
David
> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJNtJ+2AAoJELgqIXr9/gnyYBwP/izaDxAaTJL7J9YO4HFPe2w3
cfqZHeszjyqGtMmbUQozROPU/Eawz+UAbrV6XMK6U4goQ6Wpt7vCRu7TnKNi14Pw
KmVzSD9dxdc5reO9jlWjo6QDmf261+clJ36F3gnOedYY9O1++T2bJDTMZ/8Yv2ge
TEXwRryz2tqpLvxhiCO5dtWSlJQrkYqQAH00kJrAkkdnYIcH2hUhAujp+BRToOMy
9X26VsGNtJXGvfPp877LPIMM6Kp2trSkWlIbSV7Chv49pM/8UXUDIHDi3myI4Srz
qKGELCkEQrSy63XycfsqX/idbbvZvOUthnAmySkgg+J7CIuRt6wWpKLpRbajQcUV
rLU13xlcMMAu9FTS+S1y7H5zymNApmCKT8u7jI0fqLD/YwPobn4iREEscfSHKsN/
VnJYvk4QXBBGL+3d3adDTdYpKWl+kHMYdiBkE3a30TvA3mnvjWy9LuwcETzTynYP
nJpb7ENo3dPceDw8r+H7Q13HivSsHnN2p5i2ZVMNXCAlOk00N/W+xJNZTyYF6WGN
Q0YNwxjN5gW1DUJbHmxUB2c5SgqCjdCVWVZbmIwbq1d5S5Ede4wycBq99+d5Y/wC
LV64y9TxDkykj9+CTrHNgUeNYHZBdngcZm2s9iduPxC/UBG1+JHmWyXXk0CodpIv
6UtUh9S9OohZ8rjeRWEX
=QqYe
-----END PGP SIGNATURE-----
Reply to: