added another question and answer, prompted by Ray Dassen

CVS version numbers

english/devel/testing.wml: 1.9 -> 1.10

1 files changed, 27 insertions, 0 deletions

diff --git a/english/devel/testing.wml b/english/devel/testing.wml
index 5dc5cd066e4..a1cbef34de5 100644
--- a/english/devel/testing.wml
+++ b/english/devel/testing.wml
@@ -142,6 +142,33 @@ all</kbd> packages' installability on non-i386 architectures. ("It's a
 gross hack and I'm not really happy to have made it, but there you go."
 --aj)</p>
 
+<h3><q>My package is stalled because it's out of date on some architecture.
+What do I do?</q></h3>
+
+<p>Check the status of your package in the
+<a href="http://buildd.debian.org/build.php">build log database</a>.
+If the package doesn't build, it will be marked as <em>failed</em>;
+investigate the build logs and fix any of the problems that are caused
+by your package's sources.</p>
+
+<p>If you happen to notice that some architectures have built the new
+version of your package, but it isn't showing up in "testing" script output,
+then you just have to be a bit more patient until the respective buildd
+maintainer uploads the files to the Debian archive.</p>
+
+<p>If you notice that some architectures haven't built your new version of
+the package at all, despite the fact you uploaded a fix for an earlier
+failure, the reason is probably that it's marked as waiting for dependencies
+(Dep-Wait). You also see the list of these so-called
+<a href="http://buildd.debian.org/stats/">wanna-build states</a> to make
+sure.</p>
+
+<p>These problems usually get fixed eventually, but if you've been waiting
+for a longer period of time (say, two weeks or more), notify the respective
+port buildd maintainer if such an address is documented on the
+<a href="$(HOME)/ports/">port web page</a>, or the mailing list of the
+port.</p>
+
 <h3><q>Are there any exceptions? I'm sure <tt>acmefoo</tt> has just made
 it into "testing" despite not satisfying all of the requirements.</q></h3>