now that promises are satisfied, we don't retry slapos node instance
again and again, so this test starts earlier and we need to wait longer
for ERP5 to be ready.

Also tolerate that this 503 can be 404 (I think this happened a few time
on test nodes in the past)

This test was just checking the data from the first recv call, but the
data might arrive in multiple times. Call recv in a loop until we
received the end of the expected message (or until timeout when
something goes wrong).

needed for slapos.testing

and make sure we really use the develop version, by clearing version pin
that might be for another version.

Also clean up comments in version section.

This will be needed for standalone tests.

This will support shared builds from multiple directories

Prevent creating 2 wrapper for the same service if hash changed. Here, one service is exited because port is used by the firt to service to start:

    slappart6:runner-sshd-4248650e36a9a26a6481df1baffd9f58-on-watch                RUNNING   pid 27835, uptime 0:03:45
    slappart6:runner-sshd-b3b68f4278ceb84691ec27521ea229eb-on-watch                EXITED    Mar 06 04:52 PM

To achieve that, update slapos.cookbook and use hash-existing-files option of wrapper recipe

hash-existing-files list all the files used for hash that are not
handled by buildout. For those files, the hash is calculated as soon as
the __init__ function so that if there is a change in those files,
buildout will remove the existing wrapper (it will uninstall the
section) and replace it with the new wrapper.

/reviewed-on !525

Fixed slapos.core stabilises connection_dict during publish, so it is able
to calculate connection-parameter-hash the same way on client and on server, this
having same results when it is expected to have them.

Tasks:

 - [x] release `slapos.core` with nexedi/slapos.core!131 and use the version here

/reviewed-on nexedi/slapos!625

These are changes to profiles to satisfy the requirements from "checkSoftware" function from `slapos.testing`, ie:
 1. rpath is properly set on all executables.
 2. shared parts are not referencing non shared parts.

Eventhough current shared was working, we had several component with the problem 2. This was a problem in the following conditions:
 - because their hash was computed with a signature including the software installation path ( eg `/opt/slapgrid/e96b88e28dac4de1ba005bb48c6daac9/parts/something/`), shared parts were in practice never shared with other softwares. It was effective when re-installing the same software from scratch a second time, but not when using other softwares.
 - when the software was uninstalled, the shared parts stopped working because of missing paths.

As a result of these changes, some parts which used to be shared are no longer shared, but this MR also tries to share a few more parts, the goal was that all parts needed until rebootstrap were shared and also gcc and golang that are significantly large.

/reviewed-on nexedi/slapos!628

ERP5Catalog assumes that dates in catalog are UTC, this works
fine with DATETIME columns that does not carry any timezone
information, but TIMESTAMP columns are converted to mariadb timezone,
which is by default system timezone.

If we want ERP5Catalog to query on TIMESTAMP columns with the existing
logic of converting dates to UTC (because "dates are in UTC in
catalog"), we need to have TIMESTAMP columns in UTC.

This also generally seem a better default than falling back to system
timezone.

/reviewed-on nexedi/slapos!623

backports.lzma was missing from dependencies.

Based on current experiences, update the documentation regarding iptables
and network capability documentation.

It will generate new csr and key if the template changes, also if beacuse of
some reason key or csr is not present anymore.

This change makes the part resist to cases when it is becoming uninstalled and
installed again, so that it will not shoot its own foot and leaving the macro
user in inconsistent state.

depend on not shared nginx-dav-ext-module

because fonts-* all write in same parts/fonts/ this cannot be shared
yet.

xserver tries to write in xkeyboard-config:

make[2]: Nothing to be done for 'install-exec-am'.
 /bin//mkdir -p '/tmp/slaps/shared/xkeyboard-config/02d353dc7c1ab898ea120142e33b42f6/share/X11/xkb/compiled'
/bin//mkdir: cannot create directory ‘/tmp/slaps/shared/xkeyboard-config/02d353dc7c1ab898ea120142e33b42f6/share/X11/xkb/compiled’: Permission denied
Makefile:730: recipe for target 'install-dist_xkbcompiledDATA' failed
make[2]: *** [install-dist_xkbcompiledDATA] Error 1

find . -type f -executable | xargs ldd | egrep '(^\S|not found)' | grep -B1 'not found'
reported that this component creates binaries that are missing missing
rpath because libzip cannot be found.

Also enable shared as it looks shareable.

Now this component can be shared.

Maybe newer versions of file in
https://github.com/file/file/commits/master/magic/Magdir/msooxml have an
equivalent fix and the patch is no longer needed. I have kept the change
minimal.

Most components depend on perl.

We'll use "go1.4-bootstrap-20171003.tar.gz, which contains the Go
1.4 source code plus accumulated fixes to keep the tools running on
newer operating systems." as described in
https://golang.org/doc/install/source#bootstrapFromSource

(this archive contains the "time: Skip TestParseInLocation test."
commit)

Sorting will make dumped data "canonical", so it will limit amount of order
based changes.

Destroyed nodes shall be just destroyed, and there is no need to send whole
configuration to them.

This will stabilise list of published slaves.

Server returns slave list with request and publish keys, but only request keys
are important.

In order to avoid needless updates and nonsense data remove those polluted
keys before publishing information about each slave.