update info about handling of orig.tar.gz

git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@5935 e39458fd-73e7-0310-bf30-c45bca0a0e42

2 files changed, 7 insertions, 5 deletions

diff --git a/doc/how-to-DTSA b/doc/how-to-DTSA
index 7a1b85605f..e63ff5237b 100644
--- a/doc/how-to-DTSA
+++ b/doc/how-to-DTSA
@@ -10,6 +10,10 @@ Upload
 The upload can be done by any DD and is described in
 .../website/index.html.
 
+If the orig.tar.gz is already on security.debian.org (either stable-security
+or testing-security), then DON'T include it. Otherwise a bug in dak will
+prevent the buildds from building it.
+
 It is a good idea to check in the buildlog that all new patches
 actually get applied. Maybe you forgot to put them in patches/series
 or because of some bug dpatch ignored a patch.
@@ -37,11 +41,6 @@ rt.d.o.
 Autobuilds
 ==========
 
-There seems to be a bug in dak: If the orig.tar.gz is already in
-stable-security, the orig.tar.gz is not symlinked into the
-buildd/lenny  directory and the buildds cannot download the source.
-Workaround: Ask aj to create the symlink manually
-
 When you have the buildlogs and the builds look ok, you have to sign
 the changes file embedded in the buildlog and send it to the buildd
 [1]. If you use your own script to do that: the Subject needs to be
diff --git a/website/index.html b/website/index.html
index d846762d80..fe48f86e93 100644
--- a/website/index.html
+++ b/website/index.html
@@ -110,6 +110,9 @@
 		new version from unstable reaches testing, and to avoid
 		breaking secure-testing too badly with fixes that have not
 		been tested first in unstable.</li>
+		<li>If the orig.tar.gz is already on security.debian.org
+		(either in stable-security or in testing-security) 
+		don't include it in the upload.</li>
 		<li>Only make uploads for issues that the testing security
 		team plans to issue a DTSA announcement for.
 		Contact the team first to avoid duplicate work.</li>