We were previously using the linux-i686 langpacks in the linux-x86_64
builds.

David Fifield authored Feb 05, 2019 and Georg Koppen committed Feb 06, 2019

First added in https://bugs.torproject.org/15512 for Firefox 38 ESR,
these are no longer needed.

Tor Browser no longer sets these to false:
https://bugs.torproject.org/14952#comment:49
https://github.com/arthuredelstein/tor-browser/commit/14952+1

network.http.spdy.enabled.http2draft no longer even exists:
https://bugzilla.mozilla.org/show_bug.cgi?id=1132357

network.http.spdy.enabled.v3-1 no longer even exists:
https://bugzilla.mozilla.org/show_bug.cgi?id=1248197

The nightly version of obfs4 now requires Yawning's utls fork, so we
change projects/goutls to use Yawning's fork.

While doing that we rename keyring/obfs4.gpg to keyring/yawning.gpg, to
use the same keyring in obfs4 and goutls. And we refresh it to get the
new subkeys.

boklm authored Jan 30, 2019 and Georg Koppen committed Feb 01, 2019

The build of HTTPS-Everywhere requires python3.6, however the python3.6
package which we were using has now been removed from Debian Unstable.

We now build python 3.6 ourselves. As the different platforms use a
different suite by default, we add the common-stretch target to
rbm.conf, which we use to avoid building a different python for each
platform.

This reverts commit 031ecd73.

We need to back this out for now because it is causing reproducibility
issues, see #29185.

2018 is gone. Get over it.

Updating this version number will cause the old images created by
debootstrap-image to be discarded when a new image is built by
container-image. However existing images from container-image will not
be discarded as container-image's filename doesn't depend on
debootstrap-image's filename.

Versions bump and Changelog update

When bumping mingw-w64 for the crash fix in #28874 we forgot to adapt
our Windows mozconfig files to take into account that we don't need to
define CXXFLAGS anymore. The changes landed in commit
a91a7e405752bbdbe39101f7aaeb1e1d932199db in the mingw-w64 repo.

Remove the python3.6-lxml package for the list of dependencies to build
https-everywhere. This package does not exist anymore in Debian Buster,
and it seems it is not required to build https-everywhere.

Which should have been "bug_28618_v3", but the changes are okay at
least...

Richard Pospesel authored Nov 28, 2018 and boklm committed Jan 23, 2019

This patch passes in the build channel to makensis as a !define so that
the tbb-windows-installer torbrowser.nsi installer script can use
appropriate branding and set branding-specific names and install paths.

When bumping mingw-w64 for the crash fix in #28874 we forgot to adapt
our Windows mozconfig files to take into account that we don't need to
define CXXFLAGS anymore. The changes landed in commit
a91a7e405752bbdbe39101f7aaeb1e1d932199db in the mingw-w64 repo.

Richard Pospesel authored Nov 20, 2018 and Georg Koppen committed Jan 21, 2019

Updated firefox build and config to pass appropriate path for
tor-browser branding using the --with-branding ./mach configure flag.

Richard Pospesel authored Jan 15, 2019 and Georg Koppen committed Jan 21, 2019

Updated the https-everywhere deps section to install python3.6 and
python3.6-lxml. Previously python and python-lxml were listed, but these
packages now map to the 3.7 versions.

This reverts commit 49eb43da.

No longer needed after we bumped the binutils version to 2.32.1 in
bug 26148.

With older versions of binutils, the order in which .o files were
included in an .a archive did not affect the output when linking a
program or library, which is no longer the case with recent versions of
binutils. To avoid reproducibility issues we patch the libtool version
included in gcc to make the creation `libstdc++.a` reproducible.

The NoScript update fixes #28873 and #28720 on our side.