Buildout complains that two sections can not write to same file (rightfully) thus rewrite in same section.

In Ubuntu 19.10, we use GCC 9.2.1 and glib was failing to compile with
the following message:

  CC       libgio_2_0_la-gdbusauth.lo
gdbusauth.c: In function '_g_dbus_auth_run_server':
gdbusauth.c:1302:11: error: '%s' directive argument is null [-Werror=format-overflow=]
 1302 |           debug_print ("SERVER: WaitingForBegin, read '%s'", line);
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors

So we apply this MR:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/626
corresponding to this commit:
https://gitlab.gnome.org/GNOME/glib/-/commit/2a9ddc630341789c629c17c17565f5a7a7db8a8e

"gdbus: Avoid printing null strings"

This currently only works with python2, so let's explictly use python2
for now.

This fixes commit f9d5bde3.

We also often have MAKEFLAGS with -l option. For b2, this option sets
a time limit in seconds for each job, which led to random failures.

As found by jm@nexedi.com :

>>> with open('/dev/null') as f:
...   subprocess.check_call(('echo', 'foo'), stdout=f)

echo: write error: Bad file descriptor

To easily check regressions in profiles and check that fonts in PDF are what we expect.

See merge request !715

See merge request !718

Check what fonts are used when converting to PDF, using HTML as input.

Checking that something listen on the port is not enough to know when
instance is ready, because apache listen on the port very early. Also,
this does not detect problems on backend.

This fixes a regression in commit a7a36453
("Clean up some zc.recipe.egg sections installing the same scripts/interpreter").

This means the user don't have any instance at this point.

See merge request !717

See commit 1e514399.

The fixes a conflict with 'runner-exporter' due bugs in cns.recipe.symlink

Anyway, a much better idea would be to add ~/software_release/bin to PATH.

This reverts commit 4f4354c3.
It duplicated commit d13b42b7.

It was in conflict with resilient-request-*-pseudo-replicating-*-public-key.

  This means the user don't have any instance at this point.

Even when no referencing section is instanciated.

When full ERP5 / Wendelin software release compilation is done this requires more than 2GB of RAM due to groonga compilation constraints (cc1 gets OOM killed). Thus increase memory for DeploymentTests only.

[duplicity] has at least 2 issues:
- use os.chdir
- creation of paths outside of location

Since commit ebc1636d ("instanciate a
single admin node, by default in the first subpartition"), there was
only 1 admin node (and 1 neoctl wrapper) and this was inconvenient if
the partition hosting it lost.

Only 1 admin node does monitoring.

See merge request !712