path: root/wiki/src/blueprint/freezable_APT_repository.mdwn
diff options
author127.0.0.1 <>2015-10-22 15:59:11 +0200
committeramnesia <>2015-10-22 15:59:11 +0200
commita6023ebe948422ea89f71c43f913d0345daf684c (patch)
tree913c56789ba8546ac256355a15c204c5d3459312 /wiki/src/blueprint/freezable_APT_repository.mdwn
parentff8167afa87b27edb8f690560eca98e15ec66d48 (diff)
Fix formatting.
Diffstat (limited to 'wiki/src/blueprint/freezable_APT_repository.mdwn')
1 files changed, 1 insertions, 2 deletions
diff --git a/wiki/src/blueprint/freezable_APT_repository.mdwn b/wiki/src/blueprint/freezable_APT_repository.mdwn
index 9256051..092f39d 100644
--- a/wiki/src/blueprint/freezable_APT_repository.mdwn
+++ b/wiki/src/blueprint/freezable_APT_repository.mdwn
@@ -44,8 +44,7 @@ Building an ISO from the `devel` branch always uses the freshest set
of APT repository snapshots available. Resolving what's the latest one
is done at the beginning of the build, so that the entire build uses
the exact same state of these repositories. This is needed for
-reproducible builds, and has a nice side effect: so long, `Hashsum
-mismatch`, and thanks for the fish. (Implementation detail: in
+reproducible builds, and has a nice side effect: so long, `Hashsum mismatch`, and thanks for the fish. (Implementation detail: in
practice, this pointer resolution is done early in `auto/config`, so
that we can 1. specify the snapshots we want via `lb
config --mirror-{bootstrap,chroot}`, which `lb build` uses to generate