When creating update responses for nightly builds, we don't want to
create a downloads.json file, so we make that optional.

Namecoin will be enabled if all the following are true:

* rbm var/namecoin is set to 1 at build time
    * This is true for nightly on linux only
* env var TOR_ENABLE_NAMECOIN=1 is set at run-time

var/set_default_env is changing $HOME, preventing gpg to find the keys
in its default configuration directory. We avoid that by reseting $HOME
to its previous value before running gpg.

Update testsuite_git_commit so that incremental mars are generated
as part of our nightly builds.

In rbm.conf we currently have var/max_torbrowser_incremental_from set to
2. In order to be able to generate incrementals from the previous two
versions, we need to keep 3 builds.

To make generation of incremental mars easier, we use the version as the
directory name (instead of just the date).

We also define the tbb_version option, which is used to set the
TORBROWSER_NIGHTLY_VERSION environment variable.

Previously we were using the prune-old-builds script which was located
in the testsuite repository in tools/prune-old-builds, as a git submodule.

As this script is not used anywhere other than here, it doesn't make
much sense to keep it as a separate git submodule. To simplify
modification of this script, we move it here.

Researchers at the University of Minnesota generously agreed to running
a default bridge.

This fixes <https://bugs.torproject.org/32547>.

This reverts commit 26be3f16.

This commit causes the android builds to fail. See #32761.

This patch contains two backports for reproducibility issues found and
fixed in LLVM's optimization code.

The patch from bug 42574 might not be necessary in our context as I only
witnessed problems when compiling Stylo with an older Rust (1.32.0) and
then omptimizing with LLVM 8. However, it's hard to exclude any
mismatching builds we encountered so far from being affected by that
issue, so I think it is safer to backport that patch as well.

Bug 43909 is an issue we and Mozilla definitely hit and very likely
responsible for at least the vast majority of different builds we got
over the course of the last weeks and months. Many thanks to Alex
Crichton for the invaluable help in tracking this issue down.

If the linux64 mar-tools is not available, use any of the other
mar-tools that is available.

Asked by GeKo on IRC.

intrigeri authored 5 years ago and boklm committed 5 years ago

This will significantly improve the quality of life of Tails release managers
and developers. Thanks to boklm for the help!

The default bridge CDF2E852BF539B82BD10E27E9115A31734E378C2 has both an
IPv4 and IPv6 address but it is no longer reachable over it's IPv6
address, so it's time to remove it.

This fixes <https://bugs.torproject.org/32659>.

Versions bump and Changelog update