path: root/wiki/src/blueprint/freezable_APT_repository.mdwn
diff options
authorintrigeri <>2015-10-31 10:15:57 +0000
committerintrigeri <>2015-10-31 10:42:28 +0000
commit624753aaeb7e332c34cee25dd6af4edbd30859fb (patch)
tree83c04ed16c63e9903044001b11988ca86c59c6a0 /wiki/src/blueprint/freezable_APT_repository.mdwn
parent91ff3d4c9bfeb620804e34142b016ff98315a1ff (diff)
Update blueprint.
Diffstat (limited to 'wiki/src/blueprint/freezable_APT_repository.mdwn')
1 files changed, 8 insertions, 2 deletions
diff --git a/wiki/src/blueprint/freezable_APT_repository.mdwn b/wiki/src/blueprint/freezable_APT_repository.mdwn
index 9039de7..352b0f2 100644
--- a/wiki/src/blueprint/freezable_APT_repository.mdwn
+++ b/wiki/src/blueprint/freezable_APT_repository.mdwn
@@ -150,6 +150,12 @@ except:
* if a set of APT repository snapshots is encoded directly in that
branch: use them, even for
+XXX: add special handling of deb.tails.b.o, that we need since it's
+the repo where we can sneak freeze exceptions in. In theory it's not
+related to our great APT repository snapshots plans, since it has its
+own snapshots mechanism already, but ideally we would integrate it
+into the new system entirely?
## Different problems ⇒ different solutions
Note that:
@@ -423,8 +429,8 @@ time soon. Time will tell.
- * seed from existing mirror not managed by reprepro: use `_detect`
- as suggested on <>
+ * use `Log:` in `conf/distributions`? deployed (20151030), let's look
+ at it and reconsider in a few weeks
* use `Tracking:` in `conf/distributions`?
* use a leading dash for `Update: - ...` in `conf/distributions`?