Section template-apache-frontend was not updated in buildout.hash.cfg

development.cfg is never used, and having split software definition in
software.cfg and common.cfg just makes development harder.

See merge request nexedi/slapos!832

This reverts commit 1c2d1c0a.
because NEO is not ready for such change.

nbd-host and nbd-port is not required in case of simplified configuration, use
boot-image-url-select instead.

5.2.2 brings in important fix that is needed for wendelin.core 2:
https://github.com/zopefoundation/ZEO/pull/160

They say that `zodbpickle.binary` is now much more lightweight on CPython2:
https://github.com/zopefoundation/zodbpickle/blob/master/CHANGES.rst#200-2019-11-13

software/caddy-frontend implements all requirements and apache-frontend is
not tested neither developed except small fixes, so it's ok to keep it for
reference or some small work outside of official tree, as other developers
might have urge to use it.

*  Updates component/pureftpd url to 1.0.49 version because the one provided do not exist anymore (the 1.0.46 version exists now under the path [https://download.pureftpd.org/pub/pure-ftpd/releases/obsolete/pure-ftpd-1.0.46.tar.bz2](https://download.pureftpd.org/pub/pure-ftpd/releases/obsolete/pure-ftpd-1.0.46.tar.bz2))
*  Deletes explicit slapos.toolbox dependency because it's automatically installed by monitor stack

See merge request nexedi/slapos!834

* syntax highlighting for git commit message and git rebase
* include a slapos logo
* Include some better monospace fonts (Source Code Pro and Jetbrains Mono)

See merge request !831

See merge request !833

This reverts commit 3d12ddae.

The commit was instroducing errors in compilation or at runtime.

Compilation error were like (for cmake in Debian 8 machine):
[ 99%] Built target CTestLib
[100%] Built target ctest
Install the project...
bin/cmake: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by bin/cmake)
bin/cmake: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by bin/cmake)
Makefile:72: recipe for target 'install' failed
make: *** [install] Error 1
cmake: Command 'set -e;make  install' returned non-zero exit status 2
cmake: Compilation error. The package is left as is at /srv/slapgrid/slappart61/srv/runner/shared/cmake/9fc4b0e8f4f03ce17eb7ef43525d2238__compile__/cmake-3.7.2 where you can inspect what went wrong.

Runtime errors were like (for mariadb in Debian 9):
Traceback (most recent call last):
  File "/srv/slapgrid/slappart13/srv/testnode/dfg/soft/e2d325c0fcfb592bc760fe363ac5b17a/parts/slapos.core-repository/slapos/testing/testcase.py", line 168, in setUpModule
    installSoftwareUrlList(cls, [software_url], debug=debug)
  File "/srv/slapgrid/slappart13/srv/testnode/dfg/soft/e2d325c0fcfb592bc760fe363ac5b17a/parts/slapos.core-repository/slapos/testing/testcase.py", line 378, in installSoftwareUrlList
    checkSoftware(cls.slap, software_url)
  File "/srv/slapgrid/slappart13/srv/testnode/dfg/soft/e2d325c0fcfb592bc760fe363ac5b17a/parts/slapos.core-repository/slapos/testing/testcase.py", line 336, in checkSoftware
    raise RuntimeError('\n'.join(error_list))
RuntimeError: /srv/slapgrid/slappart13/srv/testnode/dfg/inst/test0-0/tmp/shared/mariadb/46cf3950f79675ddccafc1c99a13e734/bin/mysql_ldb has some not found libraries:
/srv/slapgrid/slappart13/srv/testnode/dfg/inst/test0-0/tmp/shared/mariadb/46cf3950f79675ddccafc1c99a13e734/bin/mysql_ldb: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.11' not found (required by /srv/slapgrid/slappart13/srv/testnode/dfg/inst/test0-0/tmp/shared/mariadb/46cf3950f79675ddccafc1c99a13e734/bin/mysql_ldb)
/srv/slapgrid/slappart13/srv/testnode/dfg/inst/test0-0/tmp/shared/mariadb/46cf3950f79675ddccafc1c99a13e734/bin/sst_dump has some not found libraries:
/srv/slapgrid/slappart13/srv/testnode/dfg/inst/test0-0/tmp/shared/mariadb/46cf3950f79675ddccafc1c99a13e734/bin/sst_dump: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.11' not found (required by /srv/slapgrid/slappart13/srv/testnode/dfg/inst/test0-0/tmp/shared/mariadb/46cf3950f79675ddccafc1c99a13e734/bin/sst_dump)

Be nice test and clean up your own mess.

~/bin/slapos script does not overwrite $SLAPOS_CONFIGURATION if it's set,
to prevent service accidentally use another slapos.cfg if $SLAPOS_CONFIGURATION
is set for some reason, explicit pass the path of the slapos.cfg

This solves vulnerabilities reported by npm upon installation.

We'd prefer ld to always take LD_RUN_PATH into account, even if any
rpath is specified in the command-line. We could actually change the
wrapper this way but it would not be consistent with the case where
the SR is built with system gcc.

See merge request nexedi/slapos!820

This is quite an ugly workaround

This addresses both :
 - some random failures we sometimes have when installing `python-language-server` fail
 - caddy no longer being installed here since nexedi/slapos!821

See merge request nexedi/slapos!828

It has to be ensured, that parameters are correctly passed to the partitions.

Each node allows for global statistic access for full backend-haproxy, which
is exposed using special frontend, and then transferred back to the master
partition, so that the administrator can access it.

Prevent this kind of errors when first installation fail:

    Error: [Errno 13] Permission denied: 'parts/python-language-server/bin/activate'

by using --clear the virtualenv is recreated from scratch if the command failed
for some reason.

We are observing mariadb crashes in ERP5 with 10.4, so revert back to 10.3

Crashes errors are:

    InnoDB: Assertion failure in file .../mariadb-10.4.14/storage/innobase/lock/lock0lock.cc line 6900

in non debug mode and:

    mysqld: .../mariadb-10.4.14/storage/innobase/row/row0sel.cc:4480: dberr_t row_search_mvcc(byte*, page_cur_mode_t, row_prebuilt_t*, ulint, ulint): Assertion `prebuilt->sql_stat_start || trx->state == TRX_STATE_ACTIVE || (prebuilt->table->no_rollback() && trx->state == TRX_STATE_NOT_STARTED)' failed.

in debug mode.

This is an incompatible change for ERP5 instances which might have
already been running mariadb 10.4, because their database would have
been updated to 10.4, but mariadb does not support "downgrading".
Hopefully we don't have such cases, but if that's the case one
solution seems to dump databases with 10.4 and load in 10.3 and
I guess in this process the system databases such as "mysql" should
be excluded from this process.