I'm pretty sure it'll break the ISO build.

Refs: #15197

Tails/Stretch is 64-bit only.

Tor Browser release process: bring back the improvement I made yesterday in commit:d97b8303, that was since overwritten by mistake with commit:2b205d5c.

E.g we already use '$VERSION' for the Tails release version.

E.g we already use '$VERSION' for the Tails release version.

Tor Browser import doc: use full version number, to avoid issues when we replace a given build with another one.

E.g. apt-cacher-ng won't check if the tarball it has already cached is still
current, unless we bother configuring it more precisely.

refs: #8183

We don't really "release" the Tor Browser ourselves.

Verifying that all other tarballs match on the client and server takes
quite a bit of time these days.

I.e. also the Unsafe and I2P Browser's. The main reason is so we do
not need different images for these and the Tor browser in the
automated test suite. One may argue, though, that for the Unsafe
Browser this list of fonts would be fingerprintable, but I would be
surprised if it already isn't so due to the Tor Browser Firefox
patches.

So we won't repeat mistakes like #11000 again.

Refs: #11000

To sha256sums-unsigned-build.txt (also the .asc, of course). See:

    https://trac.torproject.org/projects/tor/ticket/15864

Our installation script determines the Tor Browser version from the
tarball filenames and then looks in "$(cat
tbb-dist-url.txt)/$VERSION", which isn't very flexible. For instance,
for the pre-release of Tor Browser 4.5 our script looks in:

    http://people.torproject.org/~mikeperry/builds/4.5/

when they in fact were stored in

    http://people.torproject.org/~mikeperry/builds/4.5-build5/

So let's just store the full URL to the directory storing the
tarballs.

This reverts commit b886a25c.

The changes introduced by b886a25c certainly make things easier for the case when
we're importing the tarballs into our git-annex, but it makes this piece of doc
unusable for other usecases, most notably:

 * quickly testing a new stable or alpha Tor Browser _before_ uploading hundreds
   of MiB
 * for contributors who don't have write access to our git-annex thingie, but
   still want to work on things that involve including a custom, experimental,
   not-released-yet or whatnot Tor Browser in the ISO.

We don't have to change the url in tbb-dist-url.txt any more, so we
can do this with one commit (in Tails' Git) and with less hassle and
complexity.

We check their hashes anyway, but hey, why not. And anyway, otherwise
this curl command doesn't work (unless one adds --location to honor
redirect — to HTTPS — headers).

Closes: #9020