Debian_Stretch.md

-[[!tag archived]]
 
-[[!meta title="Porting Tails to Debian Stretch"]]
+
+---
+title: Porting Tails to Debian Stretch
+---
+
 
 This is about the effort to create [Tails
 3.0](https://labs.riseup.net/code/projects/tails/issues?query_id=198),
 based on Debian Stretch.
 
-[[!toc levels=2]]
+
+[[_TOC_]]
+
 
 # Big picture
 
@@ -79,7 +84,7 @@ evaluate the idea of basing Tails on snapshots of Debian testing.
 
 This material is mostly useful for a historical perspective. The next
 steps and up-to-date information are documented on
-[[blueprint/Debian_testing]] instead.
+[Debian testing](Debian_testing) instead.
 
 ## Stretch cycle
 
@@ -90,7 +95,7 @@ of Debian testing would feel like. During the entire cycle:
   - Whenever the porting work feels painful, e.g. because it requires
     updating images, consider fixing the problem at its root in our
     current devel branch, e.g. thanks to dogtail
-    ([[!tails_ticket 10721]]).
+    (tails/tails#10721).
 
 * Keep the documentation up-to-date on feature/stretch (:sajolida:),
   or if it is too ambitious:
@@ -123,7 +128,7 @@ of Debian testing would feel like. During the entire cycle:
     and the
     [Candidates for DTSAs](https://security-tracker.debian.org/tracker/status/dtsa-candidates).
   - How to deal with
-    [[!debwiki OngoingTransitions desc="ongoing transitions"]] that
+    [ongoing transitions](https://wiki.debian.org/OngoingTransitions) that
     block migration of security updates from sid to testing?
 
 * Make testing ISOs available widely with clear explanations of what
@@ -517,3 +522,4 @@ well. In other words, the delta between Stretch and "Buster in
 October" will be substantially bigger than what will happen during the
 next 3-months cycles, and the porting work will be close to the
 maximum one can expect during these 3-months cycles.
+