summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2017-10-09 04:06:11 +0000
committerintrigeri <intrigeri@boum.org>2017-10-09 04:06:11 +0000
commitb4518adbed01cf748323851e066c5972a42d6850 (patch)
treec8dba69dda873a271c16f01d16b68a9d30bd01c6
parentb65b7186adb7c3eb1815da8f0dcf924d62d4f0bb (diff)
Blueprint: clarify goal.
-rw-r--r--wiki/src/blueprint/Debian_testing.mdwn6
1 files changed, 3 insertions, 3 deletions
diff --git a/wiki/src/blueprint/Debian_testing.mdwn b/wiki/src/blueprint/Debian_testing.mdwn
index 6f002e8..e074538 100644
--- a/wiki/src/blueprint/Debian_testing.mdwn
+++ b/wiki/src/blueprint/Debian_testing.mdwn
@@ -68,9 +68,9 @@ part of a broader community.
At first glance it seems totally doable for Foundations Team
members to run (e.g. locally) a lightweight fork of Debian's
security tracker:
- - Problem to solve: list security issues that affect Tails (last
- release, current stable and testing branches) but are fixed in
- current Debian testing/sid
+ - Problem to solve: list security issues that affect Tails
+ (current stable and testing branches) but are fixed in
+ current Debian testing and/or sid
- Point it to our relevant APT snapshots (and perhaps current
Debian testing or sid instead of Tails devel, to avoid having
to resolve the "latest" unfrozen snapshot)