For tagged snapshots, nothing matches rpcbind, tcpd.

... due to even more last minute fixes.

For tagged snapshots, nothing matches ^exim4*.

... due to yet another last minute fix.

This is (probably?) 4843ce77 all over
again. The exact error was:

  Removing unwanted packages
  E: Unable to locate package gcc-6
  E: Unable to locate package gcc-7
  E: Unable to locate package libgcc-7-dev
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Package 'binutils-mingw-w64-i686' is not installed, so not removed
  Package 'binutils-mingw-w64-x86-64' is not installed, so not removed
  Package 'binutils-multiarch' is not installed, so not removed
  Package 'binutils-doc' is not installed, so not removed
  E: Unable to locate package gcc-6
  E: Unable to locate package gcc-7
  E: Unable to locate package libgcc-7-dev
  E: config/chroot_local-hooks/98-remove_unwanted_packages failed (exit non-zero). You should check for errors.

... due a last minute fix.

The arguments passed to seq was actually the desired output. :)

I.e. it'll be built from the stable branch: testing & devel are now
based on Buster. This would be a special bugfix release as it would
include the upgrade to Tor Browser 9.0 (Firefox 68); we've already
done this sort of things and it went well.

Currently translated at 33.3% (6 of 18 strings)

Translation: Tails/wiki/src/sandbox.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcsandboxpo/fr/

The current snapshots are actually at 2019080701 but I have seen FTBFS
on Jenkins (compile error for virtualbox-guest) and a different one
locally (Tor Browser AppArmor profile patch doesn't apply) so I'll
pick the most recent snapshots I successfully built to avoid having to
delay the release further.

In commit 31c44296 this patch was erroneously removed: the restored
patch was *not* upstreamed, so we still need to apply it.

Currently translated at 44.4% (4 of 9 strings)

Currently translated at 44.4% (4 of 9 strings)

I.e. synchronize with the ikiwiki configuration used by our production website.

In the past we recommended forking us on gitlab.com, which was the only mirror
of our main Git repository (aka. tails.git) with a user-friendly "Fork" feature.

Since then, we have another such mirror — Salsa — that we actively use and keep
track of: for example, merge requests can be submitted there and the Foundations
Team will review them. This increases the chances that other teams start to do
the same there as well, until we've decided which GitLab instance will become
the canonical location for our code in the future.

This contrasts with gitlab.com, where we have disabled MRs on purpose.

So, let's point new contributors to a mirror where they can use the common "fork
and send a MR" workflow :)

This number has been decreasing since we wrote the installation
assistant. It went from 39080 in January 2016 down to 8003 in July 2019.