Self-host the Tor Browser tarballs we need
When upgrading to new a TBB for an imminent Tails release, we often have
to fetch the TBB tarballs from e.g.
http://people.torproject.org/~mikeperry/builds or some other
temporary location. Hence, our release tags will only be buildable
for as long the tarballs stay in that temporary place, which at best is
a few months. If we fetch them from
http://archive.torproject.org/tor-package-archive/torbrowser/ we do
not have this issue, but TBB releases are only put there when publicly
released, which generally is a day or three after we want to build our
release image.
To solve this, we probably will have to host the Tor Browser tarballs ourselves, and point to this permanent location for anything that should be tagged.
Alternatively, if we want to piggy-back on all the good stuff from our
freezable APT repo (#5926 (closed)), we can adapt 10-tbb into a standalone
script (and remove it from within Tails) that prepares a Tor Browser
.deb:s. We then use it to package Tor Browser and upload it to our APT
repo like we do for other packages. Another benefit from this is that we
don’t have to host all TBB tarballs, which will occupy much more
space.
Feature Branch: feature/8125-self-hosted-tor-browser-tarballs
Related issues
- Related to #9020 (closed)
- Blocks #5630 (closed)
Original created by @anonym on 8125 (Redmine)