some misc updates

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

2 files changed, 16 insertions, 2 deletions

diff --git a/data/DTSA/hints/joeyh b/data/DTSA/hints/joeyh
index 1bb7b43094..d34f47eccb 100644
--- a/data/DTSA/hints/joeyh
+++ b/data/DTSA/hints/joeyh
@@ -1,3 +1,5 @@
+#sync pcre3/6.3-0.1etch1
+
 sync mozilla-firefox/1.0.4-2sarge2
 sync mozilla/2:1.7.8-1sarge1
 sync centericq/4.20.0-8etch1
diff --git a/doc/announce.2 b/doc/announce.2
index 4ebe743f81..46ddeb6c30 100644
--- a/doc/announce.2
+++ b/doc/announce.2
@@ -35,8 +35,16 @@ available in the repository. These include:
 DTSA-1-1 kismet -
 XXXXXX complete
 
-Currently, security updates are only built for the alpha, i386, ia64,
-mipsel, powerpc and sparc architectures.
+Note that while all of Debian's architectures are supported, we may release
+an advisory before fixed packages have built for all supported
+architectures. If so the missing builds will become available as they
+complete.
+
+We are not currently issueing advisories for security fixes that reach
+testing through normal propigation from unstable, but only for security
+fixes that are made available through our repository. So users of testing
+should continue to upgrade their systems on a regular basis to get such
+security fixes.
 
 Note that this announcement does not mean that testing is suitable for
 production use. Several security issues are present in unstable, and an
@@ -47,6 +55,10 @@ security team's website has information about what security holes are still
 open, and users should use this information to make their own decisions
 about whether testing is secure enough for them.
 
+Finally, we are still in the process of working out how best to serve users
+of testing and keep your systems secure, and we welcome comments and
+feedback about ways to do better.
+
 For more information about the testing security team, see our web site.
 <http://secure-testing.alioth.debian.org/>.