path: root/wiki/src/contribute/release_process/tor-browser.mdwn
diff options
authorTails developers <>2014-10-13 14:54:06 +0200
committerTails developers <>2014-10-13 17:16:52 +0200
commitb498b5bea41ac4138fa42b89248b936886e6ef2f (patch)
tree54cbf0780bdc3fb115ff1c4d130c7f01248dc149 /wiki/src/contribute/release_process/tor-browser.mdwn
parent969edf54ebf2b3c17d08eeba0365a3721ff6a84b (diff)
Separate data from TBB installation script.
Diffstat (limited to 'wiki/src/contribute/release_process/tor-browser.mdwn')
1 files changed, 16 insertions, 8 deletions
diff --git a/wiki/src/contribute/release_process/tor-browser.mdwn b/wiki/src/contribute/release_process/tor-browser.mdwn
index dcdb46e..139e1a5 100644
--- a/wiki/src/contribute/release_process/tor-browser.mdwn
+++ b/wiki/src/contribute/release_process/tor-browser.mdwn
@@ -4,20 +4,28 @@
Have a look at
and see if the desired version is available. We prefer
`` since the other sources periodically cleans
up old releases.
-Fetch the version's `sha256sums.txt` (and verify it with
-`sha256sums.txt.asc`) and then update the variables in
-`config/chroot_local-hooks/10-tbb` as follows:
+Fetch the version's `sha256sums.txt` and `sha256sums.txt.asc`, verify
+with `gpg`, and:
-* set `TBB_DIST_URL` to the url chosen above.
-* set `BUNDLES` to the output of:
+ grep "\<tor-browser-linux32-.*\.tar.xz$" sha256sums.txt > \
+ config/chroot_local-includes/usr/share/tails/tbb-sha256sums.txt
- grep "tor-browser-linux32-.*\.tar.xz" sha256sums.txt
+to make the checksums available at build time, when the tarballs are
+fetched. Then update the url to the one chosen above:
+ echo "" > \
+ config/chroot_local-includes/usr/share/tails/tbb-dist-url.txt
+NOTE: We must use http (not http**s**) due to limitations/bugs in
+`apt-cacher-ng`, which often is used in Tails build
+environments. However, it is of no consequence since we verify the
+checksum file.