[Secure-testing-commits] r5935 - doc website

stef-guest at alioth.debian.org stef-guest at alioth.debian.org
Sat May 26 11:09:27 UTC 2007


Author: stef-guest
Date: 2007-05-26 11:09:27 +0000 (Sat, 26 May 2007)
New Revision: 5935

Modified:
   doc/how-to-DTSA
   website/index.html
Log:
update info about handling of orig.tar.gz

Modified: doc/how-to-DTSA
===================================================================
--- doc/how-to-DTSA	2007-05-26 10:46:42 UTC (rev 5934)
+++ doc/how-to-DTSA	2007-05-26 11:09:27 UTC (rev 5935)
@@ -10,6 +10,10 @@
 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 @@
 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

Modified: website/index.html
===================================================================
--- website/index.html	2007-05-26 10:46:42 UTC (rev 5934)
+++ website/index.html	2007-05-26 11:09:27 UTC (rev 5935)
@@ -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>




More information about the Secure-testing-commits mailing list